Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Having 4 different Docker images with different ways of being configured is repetitive and confusing #12847

@reivilibre

Description

@reivilibre

We have:

  • 'the image' as published on Docker Hub (this one is user-facing and we don't want to break the interface)
  • a workers variant (I don't know who uses this other than Complement..?)
  • a Complement variant (SQLite only!)
  • a Complement + Postgres + workers variant

They don't even configure themselves in the same way. For example, one of them uses ugly sed incantations to configure appservices, the other two use slightly different Jinja2 (though they also have good reason for being slightly different, it still seems like they could be unified).

It seems like, as a first step to restore some sanity, we could for example remove the Complement+SQLite image and make it a special case of the workers one?
This would also open up the doors to having Complement+Postgres (without workers).

I will have a look at this to try and see about unifying them. I will probably leave the user-facing image alone.

New idea?:

  • 'the image'
  • Workers + Postgres
    • Complement + Workers + Postgres
      • Complement + monolith + Postgres (or can use SQLite via env var?); special case of 'no workers'

Metadata

Metadata

Assignees

Labels

T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions