Better way to make /storage accessible without persistent volumes
Nobody has claimed this yet.
- Dominant language
- Less
- Stars
- 28
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently laravel is being shared inbetween two containers, so when it wants to write logs to /storage - it fails to do so. The ideal solution would make this hack obsolete: https://github.com/Miosame/flatline/blob/655d8746f087e01b24293ff69ae697178558fa66/install.sh#L18 and maintain host volume mounts, instead of persistent data volumes, due to those not being easy to backup for the end-user.
Contributor guide
No contributing guide indexed for this repository
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
Start by inspecting install.sh at line 18 and trace how the two containers share Laravel's /storage path. Determine how host volume mounts are configured and define completion as Laravel being able to write logs without the current hack, while keeping data accessible for user backups instead of using persistent data volumes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100