parse-community / parse-community/docs
📙 Remove legacy feature from Docker example
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 507
- PR merge metrics
- No merged PRs in 30d
Description
Link to section:
https://github.com/parse-community/parse-server#inside-a-docker-container
What is the issue?
The example on how to set up Parse Server with Docker uses the --link argument. However, this argument is a legacy feature of Docker that will eventually be removed.
Can you propose a solution?
As the Docker docs say:
we recommend that you use user-defined networks to facilitate communication between two containers instead of using --link.
Is there anything we should change in our example to bring it up-to-date?
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
Open the linked “inside a Docker container” section and compare its --link example with Docker’s linked networking guidance. Update the example to use the recommended user-defined network approach, and consider the work done when the legacy --link argument is no longer documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100