Make a new Drupal site project in the Agaric system
Run from anywhere on the test or development server:
sudo /srv/scripts/agaric-newproject.sh 5 myagaric myagaric.com my.agaricdesign.com
You'll see a fair amount of output, and the last line you see should be:
Site myagaric installed; run /etc/init.d/apache2 reload to enable.
Run once as a test and once without sudo to look for problems (other than permission denied on the one run without sudo). Look for Syntax OK after running the first command, and permission denied on "make_sock: could not bind to address" is the first error for the one without sudo.
sudo /usr/sbin/apache2ctl -t
/etc/init.d/apache2 reload
sudo /etc/init.d/apache2 reload
Currently a separate step, we should roll it in: installing the database.
sudo /srv/scripts/agaric-createdatabase.sh myagaric
I will show all the output because I love it so:
Connected to database server.
User myagaric created.
Granted usage.
Database myagaric created.
Granted privileges of user myagaric to database myagaric
Copy and save this password for use on the Drupal install page, if needed:
A4KDWFcVikttQu1x
@TODO:
edit settings.php directly and protect it.
Create sites/default/files and make it writeable by the web user.
Make an installation profile that sets this directory, turns on clean URLs, etc.
Resolution
More like this
- Adding a new version of Drupal core to Agaric's Piston-enabled deployment system
- How to make patches that involve multiple files and adding new files
- Agaric move site from test to production (for first time) steps
- Git profile project in an SVN Drupal site
- Setting up the Agaric way (svn working copy checkouts) on a new server


Comments
Post new comment