Description
Ariadne is a standardized virtual machine (VM) development environment for easily developing Drupal sites in a local sandbox that is essentially identical to a fully-configured hosted solution. It attempts to emulate a dedicated Acquia/Pantheon server as closely as possible, with added development tools. Once several simple system requirements have been met, it can be set up using only a few commands from your computer's terminal.
The current iteration aims to create a local Vagrant environment that mimics Acquia's infrastructure as closely as possible, using cookbooks and roles that can easily be used to deploy an actual cluster.
Similar Projects
Quickstart and DrupalPro provide a large "golden image" of a GUI development environment, whereas Ariadne is just flat files with instructions on configuring a fully configured system from a stripped-down, bare essential "base box" image hosted elsewhere (base box is not specific to Drupal). I've been in touch with Mike Stewart about collaborating further, but it will be a long and significant effort, and it's not clear to me which will most sensibly spawn the spiritual successor.
The Vagrant project on Drupal.org uses Chef to provision, but is modeled after the php quickstart repository created by chef's parent company. Like that project, it basically aims to locally simulate the same clustered LAMP setup locally, but running Drupal. I don't believe it is intended for day-to-day development.
Aegir-Up uses Aegir as a centerpiece of the VM, and has it's own templating language to help it work with Drush. Many of our architectural and aesthetic approaches differ. Most notable, it used Puppet for system provisioning, which isn't my chosen tool.
Drupal-Up is a project I just found right now. It seems to have a subset of Aegir-Up functionality, but without the Aegir focus. It still uses Pupper, which prevents me from contributing.
Drupal.org project page
http://drupal.org/sandbox/patcon/1783838
GitHub project page
https://github.com/myplanetdigital/ariadne#readme (much more detail)
To clone (master branch isn't default, but has stable releases -- currently tag "1.2.0")
git clone git.drupal.org:sandbox/patcon/1783838.git --branch master
Drupal version agnostic.
Comments
Comment #1
sdboyer commentedso, being that this is not at all drupal code, most of the folks who typically do project reviews will be out of their wheelhouse to comment on it. i've been through it with this project several times, and while it's still got some pain points, in my opinion it's well over the line into readiness for a presence on d.o.
patcon already knows most/all of us who do devops in drupaldom, and has been discussing ariadne with us for months.
unless someone raises an objection in the next few days, i'll paste in the text from the reviews templates and make him vetted.
Comment #2
sdboyer commentedComment #3
klausiNo objection here, just a tip: We are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and I'll take a look at your project right away :-)
Comment #4
patcon commentedThanks klausi! Have never checked out those queues -- some of the projects looks really interesting, so I'll try to come back and review a few for kicks :)
Comment #5
anwar_maxHi Patcon,
Please find my comments below..
Autoamated Review
It appears you are working in the "develop" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.There is still a master branch, make sure to set the correct default branch: http://drupal.org/node/1659588 . Then remove the master branch, see also step 6 and 7 in http://drupal.org/node/1127732 Review of the develop branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
Source: http://ventral.org/pareview - PAReview.sh online service
Comment #6
sdboyer commentedour branch naming conventions are not really applicable to a project like this.
i'd forgotten about this, but that response resurfaced it for me. per my original comment, i'm promoting this now. here're some helpful links wrt maintainership:
Comment #7
patcon commentedthanks boyer and anwar_max :)
Comment #8.0
(not verified) commentedCleaner formatting
Comment #9
avpaderno