[FEATURE] Improve Docker Compose file
See original GitHub issueDescription
Make the Docker Compose more standard and complete according to the project by including the LinkFree image (service) building on the fly. Currently, we are only using the Mongo image just to get for DB connection which is not good. Changes will connect the App and DB internally.
Also after this, a contributor doesn’t need to step into the environment locally, everything will run inside containers. After this, the whole project setup will need just two-step
- Clone the repo
- Then
docker compose up
Issue Analytics
- State:
- Created 9 months ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Overview | Docker Documentation
Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application's services....
Read more >3 Docker Compose features for improving team development ...
Using advanced Docker Compose features to solve problems in larger projects and teams.
Read more >A Better, Flexible Docker Compose File - Servers for Hackers
We add features to our `docker-compose.yml` file to help our developers.
Read more >What is Docker Compose {Definition, Use Cases, Benefits ...
You can customize containers for different environments or users by adding environment variables in the docker-compose file. That gives you more ...
Read more >Docker Compose Tutorial - Process, Feature, and Use Cases
Features of Docker Compose · Multiple isolated environments on a single host · Preserve volume data when containers are created · Only recreate...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great idea 👍 we can include this in the new docs too
if I understand the concern correctly, I do not think it is an issue because where the dependencies are installed is where the app will run - yes people people try to do both, run the container and run it outside there will be an issue, but I think they need to select one of the options to run the project not both. Hope I understood correctly?