Agaric web development cooperative's main web site: https://agaric.coop
Find a file
2018-12-02 19:27:09 -05:00
box Create single method to provide all overridden values 2018-08-23 22:56:43 -04:00
config/sync Switch to non-display suite, normal node templates 2018-12-02 19:27:09 -05:00
drush Correct Drush alias tag 2018-11-05 17:37:42 -05:00
provisioning Add redirects in a text file (to be reformatted) 2018-11-19 17:34:43 -05:00
web Update pattern library 2018-12-02 11:09:32 -05:00
.gitignore Ignore folder for SQL dumps 2018-09-06 16:07:12 -04:00
.gitmodules Specify branch for pattern library submodule to prevent detached head 2018-09-05 16:11:36 -04:00
composer.json Add my patch to fix Google Docs ironic insertion of bad MSDOS carriage returns 2018-11-18 22:08:16 -05:00
composer.lock Update composer lock file 2018-11-20 13:19:30 -05:00
phpunit.xml Add the proper configuration to run the tests 2018-08-24 15:46:37 -04:00
README.md Add note to readme about forcing config update on deploy 2018-11-12 23:52:52 -05:00
Vagrantfile Add all files needed to bring up VM and run agaric.com locally 2018-08-20 10:45:20 -04:00

Get submodules

This project includes the Agaric styleguide as a git submodule.

When cloning

git clone --recurse-submodules git@gitlab.com:agaric/sites/agaric-com.git

If you cloned without --recurse-submodules

If in your initial clone you didn't do as above, you can get the styleguide with:

git submodule init
git submodule update

Get started

To be able to import the configuration, you need to get the initializing database (where we will also be collaborating on content) from the test site pending resolution of drutopia#216.

vagrant ssh
composer install
drush -y sql-dump > /tmp/paranoia.sql && drush sql-drop && drush -y sql-sync @test @self && drush -y updb

Get updates

git submodule update --recursive --remote

Theming

See web/themes/custom/agarica/README.md and web/themes/custom/agarica/patternlibrary/README.md

Deployment

Agaric is currently using a Platform as a Service version of Drutopia with additional modules.

Set up drutopia_host and hosting_private, as documented in hosting private.

Then use ahoy, from within the hosting_private directory.

If Agaric's Drutopia PaaS base has changed (the composer.lock in this directory), produce and push a new build:

ahoy deploy-build agaric

To deploy everything else (config, templates, styles):

ahoy deploy-site agaric_live

If you need to overwrite live configuration (only after confirming you've committed any parts you want to keep) you can use ahoy for that too with deploy-site-force.