Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

separate run, data and static assets #2768

Open
s-u opened this issue Nov 30, 2024 · 0 comments
Open

separate run, data and static assets #2768

s-u opened this issue Nov 30, 2024 · 0 comments

Comments

@s-u
Copy link
Collaborator

s-u commented Nov 30, 2024

With the new build system we have a nice separation of deployment and run-time. The docker compose setup shows that what we need are are three fundamental volumes: run for run-time sockets, pid files etc, data for persistent storage (rcs, sks, users data, ...) and static RCloud assets (in the images). Currently we only have ROOT but as #2749 points out we have to separate the static assets from run-time and data. So we need more locations that can be used in config files such, e.g. RCLOUD_ROOT, RCLOUD_RUN, RCLOUD_DATA - they could default to $ROOT, $ROOT/run and $ROOT/data respectively, but should be able to live outside of the $ROOT tree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant