coop-cloud/karrot
coop-cloud
/
karrot
0
0
Fork 0
Code Issues 4 Pull Requests Packages Projects Releases Wiki Activity

Use updated docker images #10

Merged
nicksellen merged 5 commits from change/use-new-docker-images into main 2024-03-25 18:48:20 +00:00
Conversation 1 Commits 5 Files Changed 4 +54 -42
nicksellen commented 2024-03-25 18:36:28 +00:00
Member
Copy Link

We have a reworked Karrot release process now ( https://docs.karrot.world/dev/deployment/releases) which results in new releases being publlished over at https://codeberg.org/karrot/karrot/releases.

It builds the docker images, so we can use the same docker images in many contexts. Frontend and backend repos now have unified version numbers.

It's a big change for the images, but should be no user facing changes.

It also moves the geoip out to a separate compose file and container (we can reuse the upstream maxmind one, which can handle all the updating itself).

The new frontend docker image uses the nginx image templating, so we don't need the docker config any more.

The new backend docker image has an entrypoint that directly calls the karrot.cli python module.

Breaking change: now the backend runs as a non-root user, the files have the wrong ownership. This needs a manual step to chown them:

abra app run <domain> app -u root chown -R karrot:karrot /app/uploads/
We have a reworked Karrot release process now ( https://docs.karrot.world/dev/deployment/releases) which results in new releases being publlished over at https://codeberg.org/karrot/karrot/releases. It builds the docker images, so we can use the same docker images in many contexts. Frontend and backend repos now have unified version numbers. It's a big change for the images, but should be no user facing changes. It also moves the geoip out to a separate compose file and container (we can reuse the upstream maxmind one, which can handle all the updating itself). The new frontend docker image uses the nginx image templating, so we don't need the docker config any more. The new backend docker image has an entrypoint that directly calls the karrot.cli python module. **Breaking change**: now the backend runs as a non-root user, the files have the wrong ownership. This needs a manual step to chown them: ``` abra app run <domain> app -u root chown -R karrot:karrot /app/uploads/ ```
nicksellen added 5 commits 2024-03-25 18:36:29 +00:00
a707991df9
Add initial compose file declaration 
Other ones don't seem to have it, but it wouldn't work on mine
without it :/
nicksellen commented 2024-03-25 18:48:15 +00:00
Author
Member
Copy Link

Going to merge right away, as I can't properly try it out until it's on main branch it seems.

Going to merge right away, as I can't properly try it out until it's on main branch it seems.
nicksellen merged commit 83e1c78b6a into main 2024-03-25 18:48:20 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 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/karrot#10
No description provided.
Delete Branch "change/use-new-docker-images"

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?