Runtime created files stored in /app
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, html
- Domain
- backend
Research direction
Start by locating the city_light initialization path mentioned in the issue and tracing where runtime paths are constructed. Search the application for files written beneath /app, including uploads, caches, temporary files, reports, databases, and logs; the issue names no specific files or tests. Done means runtime-generated files use the configurable /var/chaotica base path rather than /app.
Written by the indexing model from the issue text.
Description
Overview
At the moment, Chaotica creates and stores runtime-generated files inside /app/. Since /app/ should ideally contain only source code and static assets, it would be cleaner (and more container-friendly) to store all runtime data under /var/chaotica.
Problem:
Runtime files are currently written into /app/, which mixes application code with mutable data.
This makes it harder to run the app with /app mounted read-only (a common best practice for containers).
Proposed Change
Standardize runtime storage under:
/var/chaotica
Update the application so any files created at runtime (uploads, caches, temp files, generated reports, sqlite/db files, logs, etc.) are written beneath /var/chaotica instead of /app.
Suggested Implementation Notes
- use the single configurable base path based on the one i used for city_light initialisation (/var/chaotica/cities_light) and use it everywhere runtime paths are constructed.
Why
Separating immutable app code (/app) from mutable runtime data (/var/chaotica) improves cleanliness, and deployment ergonomics—especially for Docker-based workflows. The hope being the dev lifecycle can be locally based on the docker container and allow for hot patching while doing so.
- Dominant language
- HTML
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from brainthee/CHAOTICA
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
[Minor UI Bug] Client page shows account manager photos as squares overlapping the round borderOpen
Difficulty 1/5 Under an hour Newbie friendliness 94/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
All issues in brainthee/CHAOTICA
Similar issues
-
dropIndexes by key pattern panics on a shorter pattern and drops the wrong index on a longer oneOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mega-yfue/ha-eufy-sdk-bridge#198 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
qte77/agentic-job-offer-to-application-kit#487 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
btclib-org/btclib-wallet#801 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days