Monorepo / MagicApp: solving per-instance configuration #3

Closed
opened 2020-09-05 00:07:12 +00:00 by 3wordchant · 5 comments
Owner

As @decentral1se said over in #2:

Another thought on https://git.autonomic.zone/autonomic-cooperative/?q=.zone&sort=recentupdate&tab= is that it is really specific to having Drone CI running for all the deployments (you need that extra infra) and separating it into its own repository for each app is a little bit of overkill (or feels like). So, wonder how it could become a monorepo and still have this "if you push a commit, it auto-deploys" mode of operating...

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.

As @decentral1se said over in #2: > Another thought on https://git.autonomic.zone/autonomic-cooperative/?q=.zone&sort=recentupdate&tab= is that it is really specific to having Drone CI running for all the deployments (you need that extra infra) and separating it into its own repository for each app is a little bit of overkill (or feels like). So, wonder how it could become a monorepo and still have this "if you push a commit, it auto-deploys" mode of operating... 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.
Owner
A New Hope: https://git.autonomic.zone/autonomic-cooperative/abra
3wordchant added this to the Public mini-launch milestone 2020-09-21 18:51:18 +00:00
Author
Owner

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.

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](https://git.autonomic.zone/compose-stacks/planning/milestone/4). 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.
Owner

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 https://git.autonomic.zone/autonomic-cooperative/abra/issues/1) that can support the monorepo setup? So, making the .envrc explicit in a YAML formatted file.

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 https://git.autonomic.zone/autonomic-cooperative/abra/issues/1) that can support the monorepo setup? So, making the `.envrc` explicit in a YAML formatted file.
Author
Owner

Lots of progress towards monorepo over in autonomic-cooperative/abra@monorepo

Lots of progress towards monorepo over in [`autonomic-cooperative/abra@monorepo`](https://git.autonomic.zone/autonomic-cooperative/abra/src/branch/monorepo)
Author
Owner
First stab: https://git.autonomic.zone/autonomic-cooperative/coop-cloud-apps/ Closing for now.
Sign in to join this conversation.
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#3
No description provided.