Migration instructions need to include `config/` handling
Open
Nobody has claimed this yet.
bug
docs
feature: auto config (environment variables)
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
Otherwise none of the image's config/ files will ever get deployed into migrated environments (though fortunately #2120 at least will warn them now).
The migrations instructions already are overdue to be reviewed based on the report contained in #1155
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
Locate the migration instructions in the repository and review report #1155 first, then compare the documented process with the warning from #2120. Update the instructions to cover deployment of the image's config/ files, and incorporate the relevant migration findings from the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100