8 Comments
User's avatar
Jelena Cupac's avatar

Is it easy for developers who've never used Docker to get used to it?

Expand full comment
Vinny's avatar

I think so. It's easier than config all app by hand.

Expand full comment
Valentina Jemuović's avatar

Yes, indeed. Sure, there is a learning curve when using Docker the first time, but afterwards it’s easy.

Expand full comment
Jesús Leganés-Combarro's avatar

IMHO, projects should work with default config at least of basic functionality, or crash at start time with a nice error message telling what's missing to add or configure. Docker should not be needed for development environments, at most docker-compose when there are several interrelated components, and always accessing the actual source code from a volume, so it's only used to spin servers up.

Expand full comment
Valentina Jemuović's avatar

“projects should work with default config at least of basic functionality“

Yes.

“Docker should not be needed for development environments“

VJ: But how would you hand the case where the app needs a DB, yet there’s no Docker?

Expand full comment
Jesús Leganés-Combarro's avatar

Allow to install the database globally, include a local mock server, or use docker-compose. Docker-compose is nice for these use cases, Docker isn't.

Expand full comment
Per Lundholm's avatar

I'd prefer something like Flyway to keep database schema and code in sync. But Docker for sure avoids the hazzle of installing and updating database and middleware. Your build system should pick the correct version of the compiler.

The should be no procedure other than getting the software from the repository , almost.

Documents get outdated. Period.

Expand full comment
Jesús Leganés-Combarro's avatar

I miss a plot twist, like "...until a new teammate joined, and found Docker was either the solution", and later a long post explaining the importance of document everything and have documentation updated and how to test all the onboarding process is updated automatically :-)

Expand full comment