Custom CSS in volume #9

Merged
3wordchant merged 4 commits from custom-css-volume into main 2025-01-07 15:16:21 +00:00
Owner

This PR adds an optional compose file, compose.css-volume.yml, which allows hosters to store a complete custom.css file.

This PR adds an optional compose file, `compose.css-volume.yml`, which allows hosters to store a complete `custom.css` file.
moritz was assigned by 3wordchant 2024-12-24 18:31:18 +00:00
3wordchant added 3 commits 2024-12-24 18:31:19 +00:00
decentral1se reviewed 2024-12-25 09:09:50 +00:00
decentral1se left a comment
Owner

💫

💫
.env.sample Outdated
@ -50,3 +50,1 @@
COPY_ASSETS="flow_background.jpg|app:/web/dist/assets/images/"
COPY_ASSETS="$COPY_ASSETS icon_left_brand.svg|app:/web/dist/assets/icons/"
COPY_ASSETS="$COPY_ASSETS icon.png|app:/web/dist/assets/icons/"
## custom css and assets
Owner

Requires some release notes for this change in behaviour?

Requires some release notes for this change in behaviour?
Author
Owner

I cannot remember why these were commented out, again I don't think it will affect existing deployments but unless @knoflook remembers more context I say we just revert the commenting-out change.

I cannot remember why these were commented out, again I don't think it will affect existing deployments but unless @knoflook remembers more context I say we just revert the commenting-out change.
decentral1se marked this conversation as resolved
@ -0,0 +3,4 @@
services:
app:
user: root
Owner

Not sure if this changes the attack surface but in case it does, might be worth signalling in release notes and/or docs that a user: root is introduced into the stack deployment? Might be a consideration point since it's usually a central point of infra.

Not sure if this changes the attack surface but in case it does, might be worth signalling in release notes and/or docs that a `user: root` is introduced into the stack deployment? Might be a consideration point since it's usually a central point of infra.
Author
Owner

I don't think it changes anything about existing deployments, unless someone opts-in to the extra .yml file.

It's hard for me to imagine how there could be a security hole in either cp, or su, but I don't claim to be an expert.

Happy to add a comment in .env.sample to warn about this, either way.

I don't think it changes anything about existing deployments, unless someone opts-in to the extra `.yml` file. It's hard for me to imagine how there could be a security hole in either `cp`, or `su`, but I don't claim to be an expert. Happy to add a comment in `.env.sample` to warn about this, either way.
decentral1se marked this conversation as resolved
Author
Owner

Tysm for the review @decentral1se !

Tysm for the review @decentral1se !
3wordchant added 1 commit 2025-01-07 15:16:06 +00:00
3wordchant merged commit 344db235b0 into main 2025-01-07 15:16:21 +00:00
3wordchant deleted branch custom-css-volume 2025-01-07 15:16:21 +00:00
Sign in to join this conversation.
No description provided.