Implement automation triggers.
Opened this issue · 4 comments
daniel-vc commented
Purpose of this issue is to cover a few scenarios where we might want automation to occur from places like master, develop or feature branches.
Some ideas (feel free to add your own).
- Master: Github triggers new actions to Server CI
- Master: Circle CI master triggers new builds, then publishes to a hosting platform (Netlify?)
- From feature branch, publish to new staging url (Netlify)
daniel-vc commented
Will create a CircleCI work account and give you all access to it.
daniel-vc commented
Update:
- CraftCMS is now being run from: https://github.com/daniel-vc/project-loop
- Gatsby front-end is being run from: https://github.com/daniel-vc/project-loop-gatsby
- Craft CMS Admin URL is: http://loop.test.circulareconomy.space/admin
-
Both repositories are now being watched on CircleCI for updates and watches for any changes on any branches.
-
Gatsby is now being watched for changes in Gatsby Cloud
daniel-vc commented
Gatsby now re-builds (via Gatsby cloud) after content update trigger from Craft CMS.
daniel-vc commented
🔥Gatsby Cloud now building to Amazon S3
Endpoint URL: http://emf-project-loop.s3-website.eu-west-2.amazonaws.com/