Feature: Read-only filesystem support
Open
Nobody has claimed this yet.
type: feature
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
Requested Feature
- Supporting read-only velocity.toml
- Optionally supporting disabling logging to disable all writes to the filesystem
Why is this needed?
To support a declarative, immutable system like nix, having a read-only configuration file is neccessary, i also think any project should not have write access to a its own config file at runtime.
Alternative Solutions
I have a workaround to this issue, but its not using the immutable system of nix, which removes reproducibility from my server. Skademaskinen/Server-Config#23
Additional Information
No response
Contributor guide
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.
Research direction
The issue names no files, tests, or entry points. Begin by tracing where velocity.toml is read and where configuration or logging writes occur; done should include read-only configuration support and an option that prevents filesystem writes, with behavior verified by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100