Monorepo / MagicApp: solving per-instance configuration #3
Labels
No Label
automation
bug
community organising
democracy
design
documentation
duplicate
enhancement
finance
funding
help wanted
invalid
publishing
question
security
wontfix
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As @decentral1se said over in #2:
Since then, we've been wondering about MagicApp as a potential alternative solution, to get closer to a Cloudron-esque pointy-clicky-app-deployment UI, but backed off wondering if it wasn't the "just one more neat abstraction layer" that might completely disconnect us from reality.
A New Hope: https://git.autonomic.zone/autonomic-cooperative/abra
As we saw recently with the Wordpress backup collab, it'd be nice to have even a start at a solution to this for our public mini-launch.
A monorepo seems simpler; I guess we'd need to decide a recommended repo / config layout and then add options to
abra
to specify which env vars go with which stacks.Yeah, I think monorepo would be nice. It would also be less overhead for our our upgrade bot config and general day-to-day maintenance. Is there anything to be said for trying to come up with a
abra.yml
format (some references made in autonomic-cooperative/abra#1) that can support the monorepo setup? So, making the.envrc
explicit in a YAML formatted file.Lots of progress towards monorepo over in
autonomic-cooperative/abra@monorepo
First stab: https://git.autonomic.zone/autonomic-cooperative/coop-cloud-apps/
Closing for now.