Should the assets folder be a named volume? #8

Closed
opened 5 months ago by decentral1se · 3 comments
Owner

When an upgrade is ran, they are not updated but they should be?

https://github.com/Chocobozzz/PeerTube/issues/3546

I had to manually remove the existing volume and redeploy for the ruangrupa instance.

When an upgrade is ran, they are not updated but they should be? > https://github.com/Chocobozzz/PeerTube/issues/3546 I had to manually remove the existing volume and redeploy for the ruangrupa instance.
Collaborator

Those files are served directly by nginx so they need to be in a named volume in order to be reachable.

What we could do instead as a workaround is use the nginx proxy-cache and forward the misses to the nodejs container... It would be much better to have the peertube container copy them over during startup though. Maybe the way to go is to do that ourselves in the entrypoint script (which we are already overriding)

Those files are served directly by nginx so they need to be in a named volume in order to be reachable. What we could do instead as a workaround is use the nginx proxy-cache and forward the misses to the nodejs container... It would be much better to have the peertube container copy them over during startup though. Maybe the way to go is to do that ourselves in the entrypoint script (which we are already overriding)
Poster
Owner

Nice! Thanks for explaining that. Yes, the entrypoint hook to copy stuff would be great.

Nice! Thanks for explaining that. Yes, the entrypoint hook to copy stuff would be great.
Collaborator

@decentral1se should be good to go :)

@decentral1se should be good to go :)
decentral1se closed this issue 5 months ago
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.