Set up development environment system [#849932]

We will provide good development environments for working on Drupal.org using AWS instance(s). Themers and developers should have real development environments with SSH access. No committing to deploy. A development environment is basically a db copy and bzr checkout, we can automate this on AWS.

1. Have wildcard DNS pointing *.drupalorgdev.org or something to the instance. A different top-level domain name will prevent session cookies being sent to development sites. Wildcard DNS means we don't have to touch DNS again.

2. Once a day redesign.drupal.org will get a fresh database and updates for the redesign. The database dump of that can be used for development environments. That Husdon job should be in decent shape later today.
(Right now http://twitter.com/hudsondrupal tweets that, SUCCESS:drupal_snapshot_to_redesign_cleanup.)

3. A Hudson job with a parameter should be able to automate a full staging site buildout:
- Set up a vhost
- Do a BZR checkout
- Make a DB or maybe they use a shared DB
- Make sure permissions and such give access to the developer

4. We should also have Hudson jobs for
- Delete a development site
- Bring in a fresh copy of the database
- Automate other site development environments, like security.drupal.org

Comments

Comment #1

basic CreditAttribution: basic commented 22 July 2010 at 22:09

We worked through the redesign development environment system at the redesign sprint. There are now two hudson jobs and two helper scripts that create and destroy development environments. The documentation for these is available at https://infrastructure.drupal.org/node/144

The next step is to complete the new wildcard dns and update the templates to match that, and then start expanding the hudson jobs/scripts to support build outs for more than just redesign.d.o

-Rudy