Naming convention on images in the compose config #4

Closed
opened 2021-12-04 15:49:57 +00:00 by decentral1se · 1 comment
Owner

E.g. we're using stuff like snikket_server instead of app (or idk if that is the main image?) which I think abra can handle but there are probably a bunch of bugs waiting for not following this naming convention. Would changing them mess up the config? Seems like it might.

E.g. we're using stuff like `snikket_server` instead of `app` (or idk if that is the main image?) which I think `abra` can handle but there are probably a bunch of bugs waiting for not following this naming convention. Would changing them mess up the config? Seems like it might.
Owner

I wasn't sure if changing either snikket_proxy or snikket_server to app would break things, or which one to do, but now I'm semi confident that it should be snikket_proxy, and that it should be fine to change it if enough SNIKKET_INTERNAL vars are updated.

I wasn't sure if changing either `snikket_proxy` or `snikket_server` to `app` would break things, or which one to do, but now I'm semi confident that it should be `snikket_proxy`, and that it should be fine to change it if enough `SNIKKET_INTERNAL` vars are updated.
decentral1se referenced this issue from a commit 2021-12-04 23:49:17 +00:00
Sign in to join this conversation.
No Label
No Milestone
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/snikket#4
No description provided.