Organisational "buildpack" shower thoughts #59

New Issue

decentral1se · 2021-04-11T16:39:28Z

decentral1se commented

2021-04-11 16:39:28 +00:00

you know we have these apps now but we also have this kind of big-picture organisational strategy stuff too. So, like, imagine we say, Autonomic uses 6 apps to run the co-op. We could distill that down into docs as a sort of "co-op buildpack" or something, no? As an abstraction layer beyond categorising apps (useful but more is needed). If your org needs x,y,z then choose buildpack C (which is just a curated list of 6 apps)
then you abra buildpack create coop and it wires it all up (this is maybe a dream level of automation)

> you know we have these apps now but we also have this kind of big-picture organisational strategy stuff too. So, like, imagine we say, Autonomic uses 6 apps to run the co-op. We could distill that down into docs as a sort of "co-op buildpack" or something, no? As an abstraction layer beyond categorising apps (useful but more is needed). If your org needs x,y,z then choose buildpack C (which is just a curated list of 6 apps) > then you abra buildpack create coop and it wires it all up (this is maybe a dream level of automation)

decentral1se added the

design

label 2021-04-11 16:39:28 +00:00

decentral1se commented

2021-04-11 16:41:03 +00:00

yeah this kind of thing has been kicking around in my mind.
step zero: firm up our tech choices, maybe make a blog post about our stack
easy first step: lists of recommended package combos in the co-op cloud docs
step 2: maybe adding some options to the installer?
curl ... | bash -s -- --set-us-up-the-bomb=co-op
step 3: meta-recipes ("meal plans"? 🙃) in abra itelf?
abra mealplan co-op

> yeah this kind of thing has been kicking around in my mind. > step zero: firm up our tech choices, maybe make a blog post about our stack > easy first step: lists of recommended package combos in the co-op cloud docs > step 2: maybe adding some options to the installer? > curl ... | bash -s -- --set-us-up-the-bomb=co-op > step 3: meta-recipes ("meal plans"? 🙃) in abra itelf? > abra mealplan co-op

decentral1se added this to the (deleted) project 2021-04-30 07:31:47 +00:00

decentral1se commented

2021-09-08 13:01:32 +00:00

For Another Day.

decentral1se closed this issue

2021-09-08 13:01:32 +00:00

decentral1se commented

2023-03-06 14:00:02 +00:00

Thought about this again after chatting with @moritz! Some way to specify an entire deployment via YAML or some other thing. And we talked about some extra glue layer which might query the API to create SSO clients and insert them into the relevant apps. This would be a higher level of automation. A sketch:

apps:
  - recipe: nextcloud
  - recipe: authentik
client:
  - <spec authentik/nextcloud client>

And you could abra apply autonomic.yml and it would "apply" the configuration to a server. This would be a "terraform-like" style implementation which would operate on the config commons instead of the system level.

Galaxy brain, indulge me.

/cc @moritz

Thought about this again after chatting with @moritz! Some way to specify an entire deployment via YAML or some other thing. And we talked about some extra glue layer which might query the API to create SSO clients and insert them into the relevant apps. This would be a higher level of automation. A sketch: ```yaml apps: - recipe: nextcloud - recipe: authentik client: - <spec authentik/nextcloud client> ``` And you could `abra apply autonomic.yml` and it would "apply" the configuration to a server. This would be a "terraform-like" style implementation which would operate on the config commons instead of the system level. Galaxy brain, indulge me. /cc @moritz

🚀 1

decentral1se reopened this issue

2023-03-06 14:00:03 +00:00

decentral1se added this to the Medium/large enhancements project 2023-06-08 09:32:58 +00:00

3wordchant referenced this issue from coop-cloud/outline

2023-06-25 19:56:57 +00:00

add integrated minio #14

Sign in to join this conversation.