host org-y on amplify-edge, and then host real data demo on gcn.org #55
Description
We should host the current org-y demo in our data center. The current random test data is fine.
Then get the CI doing a release on each successful build to the CI "tag"
deployment_mapping.json:
We sort of discussed an idea of git holding a "deployment_mapping.json" file in the master branch.
For example: V1.1.1 = production, V1.1.2=staging, v1.1.3=ci.
In the data center, booty would be polling for that "deployment_mapping.json", and then know what git release it should be looking for based on booty being configured for an environment like "ci, staging, production".
With this setup, when a developer wants to tag a release its independent of the deployed booty's in the data center.
They can play with a CI environment and if happy promote it using the "deployment_mapping.json" file. They woudl just pull master, edit it, and push it. All the deployed booty's would then see it as they polled in. Could do web hooks, but pollings is simpler for now. And allows a move to s3 or other later to be easy.
Let me know your thoughts on this approach.. @alexadhy
I know its pointless in some ways until we have migrations, but its i think a nice way forward...
Once the above works, then we can get GCN using it:
GCN is not capable of running their own repo and code.
So we gotta do it for them for now. We can setup a github user and repo for them called "main", with bootstrap data that represents a single Org/Project to keep things simple, as thats is all they need.
User can be "ops@getcouragenow.org" and same github user name.
Then we can have a folder for each Org with their own bootstrap data.
Example: deploy/org-demo/, deploy/org-a/, deploy/org-b/, etc, etc
This will be where rosie can edit the bootstrap for each of the orgs they want to facilitate, and then tell them the Iframe URL to use.
We will run this on Server with caddy running each of them under the GCN domain, and a subdomain for each Org.