Answers: <ol>
  <li>Ensure everyone, regardless of OS, uses Bash and Linux-friendly file paths and naming conventions.</li>
  <li>Windows users should <a href="https://learn.microsoft.com/en-us/windows/wsl/install" rel="nofollow noreferrer">install WSL</a></li>
  <li>Ensure everyone knows how to work with <code>docker</code> and <code>docker-compose</code> at the command line.</li>
  <li><em>local set up does not currently use containers</em> --everyone should have a local set up that uses containers!</li>
  <li>Create a private Docker registry to make it easier to share Docker images with your team.</li>
  </ol>
  
Answers: CC BY-SA 4.0
Answers: 2024-09-27T14:21:40.553Z
Answers: 2024-09-27T14:21:40.553Z
Answers: mikequentel
Answers: <p>To standardize your development environment across Mac, Linux, and Windows, consider using Docker for local development, mirroring your production setup. This ensures consistency across operating systems and simplifies onboarding. Docker Compose can manage multi-container setups, making it easier to handle microservices. For logging, debugging, and hot reloading, tools like <code>docker logs</code>, IDE integrations (e.g., Visual Studio Code with Docker extensions), and bind mounts for live code updates are effective.</p>
  
Answers: CC BY-SA 4.0
Answers: 2024-08-27T12:15:35.323Z
Answers: 2024-08-27T12:15:35.323Z
Answers: lostmarien
Body: <p>I am working with a set of microservices and a database that are currently being set up by developers on Mac, Linux, and Windows workstations each with their own idiosyncrasies. The production application is containerized using Docker and deployed on AWS ECS, but the local set up does not currently use containers.</p>
  <p>What are my current tooling options to research with the goal of creating a more standardized development environment across operating systems and reduce the onboarding time for new developers? How might choices affect developer ease in things like logging, debugging, and hot reloading?</p>
  
Comments: CC BY-SA 4.0
Comments: 2024-08-02T03:56:44.287Z
Comments: Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer.
Comments: Community
Tags: <docker><docker-compose><amazon-ecs>
Title: Advice on tooling for development environment
UserDisplayName: rbz732
ThreadText: # Advice on tooling for development environment
  
  (Asked by: username_0 on 2024-07-31)
  
  I am working with a set of microservices and a database that are currently being set up by developers on Mac, Linux, and Windows workstations each with their own idiosyncrasies. The production application is containerized using Docker and deployed on AWS ECS, but the local set up does not currently use containers.
  
  What are my current tooling options to research with the goal of creating a more standardized development environment across operating systems and reduce the onboarding time for new developers? How might choices affect developer ease in things like logging, debugging, and hot reloading?
  
  **Tags:** docker, docker-compose, amazon-ecs
  
  > **Comments:**
  > **username_1**: Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2024-08-27. Score: 1
  
  To standardize your development environment across Mac, Linux, and Windows, consider using Docker for local development, mirroring your production setup. This ensures consistency across operating systems and simplifies onboarding. Docker Compose can manage multi-container setups, making it easier to handle microservices. For logging, debugging, and hot reloading, tools like `docker logs`, IDE integrations (e.g., Visual Studio Code with Docker extensions), and bind mounts for live code updates are effective.
  
  
  ---
  
  ### Answer by username_2 on 2024-09-27. Score: 0
  
  1. Ensure everyone, regardless of OS, uses Bash and Linux-friendly file paths and naming conventions.
  2. Windows users should [install WSL](https://learn.microsoft.com/en-us/windows/wsl/install)
  3. Ensure everyone knows how to work with `docker` and `docker-compose` at the command line.
  4. *local set up does not currently use containers* --everyone should have a local set up that uses containers!
  5. Create a private Docker registry to make it easier to share Docker images with your team.
  
  
  ---
  
  