PrestaShop / PrestaShop/docker
[Documentation] Handling upgrades
Open
Nobody has claimed this yet.
question
- Dominant language
- Dockerfile
- Stars
- 281
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
I m' a bit confused by the "whole /var/www/html" volume :
- Usually volumes only contains user data not app "static" data
- How would one handled a 1.6-1.7 upgrade with the whole volume ?
- When he would compose pull/rm/up with 1.7 , he will need to manually start an upgrade using the web GUI ?
- That sounds against docker usage.
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
The issue does not name a file or test; start by reviewing the Docker volume configuration and the 1.6-to-1.7 upgrade flow described in the issue. Done means documenting whether the full /var/www/html volume is intentional and giving reproducible compose and web-GUI upgrade steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100