agaric/agaric-coop
10
1
Fork 0
Code Issues 102 Pull requests Projects Releases Packages Wiki Activity
Agaric web development cooperative's main web site: https://agaric.coop
656 commits 5 branches 0 tags 10 MiB
Jinja 52.3%
PHP 24.3%
Shell 15%
Ruby 6.1%
Makefile 1%
Other 1.3%
Find a file
Clayton Dewey 3364db12b4 Fix formatting in User Story template
2019-01-25 12:18:46 -07:00
.gitlab/issue_templates Fix formatting in User Story template 2019-01-25 12:18:46 -07:00
box Create single method to provide all overridden values 2018-08-23 22:56:43 -04:00
config/sync Language switcher footer 2019-01-21 23:48:06 -06:00
drush Update live site URI 2019-01-02 18:30:31 -05:00
provisioning Redirect project we resurected 2019-01-02 01:15:30 -05:00
web Typo 2019-01-22 12:27:57 -06: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 Language switcher footer 2019-01-21 23:48:06 -06:00
composer.lock Composer lock file with the language dropdown module 2019-01-21 23:48:25 -06:00
Makefile Correct sync location and split up steps 2019-01-24 13:46:35 -05:00
phpunit.xml Add the proper configuration to run the tests 2018-08-24 15:46:37 -04:00
README.md Tweak README for deployments 2019-01-24 14:00:03 -05:00
redirects.txt Add redirects.txt as expected per drutopia_host 2018-12-07 02:00:24 -05:00
SERVICES.md Add services file with Drupal Planet info 2019-01-04 07:36:42 -05:00
Vagrantfile Add all files needed to bring up VM and run agaric.com locally 2018-08-20 10:45:20 -04:00

README.md

Agaric's Flagship Site

See also SERVICES.md

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 @live @self && drush -y updb
drush -y rsync @live:%files @self:%files

Get updates

git pull
git submodule update --recursive --remote
vagrant ssh
composer install
drush -y sql-dump > /tmp/paranoia.sql && drush sql-drop && drush -y sql-sync @live @self && drush -y updb
drush cim -y

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.

Ensure all three related repositories are up-to-date with:

ahoy git-pull-all

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

Then record the deployment. This applies to both deploy-site and deploy-build record keeping: Navigate to /drutopia_host/build/artifacts Add all new files generated with git add . Commit the files with a message on what you deployed with 'git commit -m ' Push the changes to the repo with git push

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.