You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our development environment relies on Docker and docker-compose, leading to permission issues on HOST while working on the project. To solve these kind of issues and ease developer on-boarding on the project, we wrote a bunch of shell scripts (bash) to build, run and test Fonzie.
Even if those scripts are relevant to improve the developer experience, they raise two kind of problems we need to address:
wrapping docker(-compose) commands can appear unnecessary for advanced users that prefer using docker raw commands,
hiding the underlying docker complexity will not incentive new users to learn it from the basis.
Proposal
We need to exhaustively document those scripts to explain what they are doing (by comparing them with docker(-compose) raw commands) and how they can ease the developer life.
The text was updated successfully, but these errors were encountered:
Purpose
Our development environment relies on
Docker
anddocker-compose
, leading to permission issues on HOST while working on the project. To solve these kind of issues and ease developer on-boarding on the project, we wrote a bunch of shell scripts (bash) to build, run and test Fonzie.Even if those scripts are relevant to improve the developer experience, they raise two kind of problems we need to address:
Proposal
We need to exhaustively document those scripts to explain what they are doing (by comparing them with docker(-compose) raw commands) and how they can ease the developer life.
The text was updated successfully, but these errors were encountered: