Agaric internal: Steps to quickly create and deploy a site

Full steps to take a new site live:

Create a project in git: https://agariclabs.net/gitweb?p=agaric/scripts.git;a=blob;f=agc.sh;hb=HEAD

Start a MayFirst project.

MayFirst login: https://members.mayfirst.org/cp/
Member area: https://members.mayfirst.org/cp/index.php?area=member
Add a new member: https://members.mayfirst.org/cp/index.php?area=member&member_id=458&action=new

primary server: sojourner

Next, create a database for this hosting order. We customarily use the project name, e.g. example.

Then create a database user and give it full access to the database above. Again, we customarily use the project name, e.g., example. Save the password you create for this database user.

Make sure you have an etc/live.settings.php; you can copy etc/test.settings.php or web/sites/default/default.settings.php or run drake build_live to create one. Copying the test settings is easiest, then edit it:

Edit the database user that is automatically created so that you can create a new randomly generated password, and commit it to your etc/live.settings.php so the database definition part looks something like this:

Don't forget to git add etc/live.settings.php and git commit it.

Now we're ready to follow Deploying the Agaric Way:

Warning: This is done only the first time, but presuming you've got some content you want on the test site, move the test database to the live server with the drake db_sync_test_to_live command and move the files from the test server to the live server with the drake file_sync_test_to_live command. Again, don't use these commands after the initial launch.

Once you've checked out the site at its temporary URL, e.g. example.mayfirst.org, and everything looks OK...

Configure its domain to point to a.ns.mayfirst.org and b.ns.mayfirst.org nameservers.