10 Comments

  1. Scott Hartley

    Why not just use something like Bitnami?

    https://bitnami.com/stack/wordpress/installer

    Report

    • timothybjacobs

      Bitnami runs on your own machine. VVV and the likes use virtual machines which don’t have a risk of corrupting your system, allow you to test against multiple server configurations, and allow for a team to have the same server configuration – hopefully reducing the “it works for me” syndrome.

      Report

      • ezekg

        Correct. Vagrant (and virtual machines in general) allows for rapid development. In addition to being able to easily share/distribute VMs, you can also destroy and rebuild a VM at any time, giving you complete freedom to test inside of a sandboxed environment. Vagrant also allows you to perfectly mirror your production environments (though we don’t often do this); as far as I can tell, Bitnami does not allow such freedoms.

        Report

  2. Aakash

    Is VVV available on azure ??

    Report

  3. Theron S (@therons)

    https://github.com/bradp/vv has been around for some time and ia great for origonal vvv box.

    Report

    • ezekg

      Both projects were actually created around the same time (Oct/Nov last year), but ours was in private development. Variable VV is a really great project. I continued to develop ours to allow more flexibility and to make sure that it is well tested, since it’s written in Ruby. Also, a nice side effect of building it in Ruby is that it supports Windows, which as far as I know, no other site generator does (since they’re all written in Bash).

      Report

      • Theron S (@therons)

        Neat. I’d be interested in knowing what use cases it might be wise to choose theme juice for over variable vvv? Apache is an obvious. Any others you can think of?

        Report

        • ezekg

          It really depends on you and your team. Theme Juice isn’t simply a site generator, it’s also a site manager. It helps you manage and organize your build tools, it sets you up to test on other devices via xip.io, and hypothetically, it could even manage multiple Vagrant installations e.g Nginx VVV, HHVM VVV, and Apache VVV.

          Another thing to note is that you can have your projects live anywhere on your file system, (as opposed to having them directly inside the VM’s www/ directory), since everything is shared with the VM (think: symlinks). These points alone show the flexibility of our CLI. Hopefully within the next month we’ll have deployments/migration handled as well!

          Report

  4. Hans-Helge

    Interesting project. I use VVV on daily basis and with vv it works really great. But the ability to access the sites on your mobile devices, like theme juice promises it, would be great. :) Will definitely take a look at it.

    Report

Comments are closed.

%d bloggers like this: