Programming

17407 readers

116 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

(How) do you automate setting up your local development environment? (lemmy.ml)

submitted 1 year ago by [email protected] to c/programming

23 comments fedilink hide all child comments

In a lot of projects, this is usually done via README. It tells you what running dependencies to install and how to run certain commands.

This can get harder to maintain as things change, the project grows, and complexity increases.

I see two parts to automate here: actually setting up the environment, and running the application or orchestrating multiple apps.

How do you address this?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 16 points 1 year ago* (last edited 1 year ago) (2 children)

My life changed once I discovered dev containers in VS Code. Basically developing within a bootstrapped Docker container.

[–] fuckspez 4 points 1 year ago (1 children)

We're following the same. It's been a life changer for us.

[–] __init__ 5 points 1 year ago

Dev containers are the shit. We did the readme instructions style at my last job and it took new hires like a full day to set up, propagating changes was a nightmare and shit was always going wrong. We use dev containers now. Everyone gets the exact same version of everything with almost zero opportunity to screw it up. If anything gets messed up, it’s fixed by a rebuild almost every time.

[–] [email protected] 2 points 1 year ago (2 children)

How's the filesystem performance? Whenever I've mounted something into a Docker Container, the performance has suffered. For example, things like NPM/MVN suddenly take way longer.

[–] [email protected] 1 points 1 year ago

In my experience it's greatly dependent on how much memory you dedicate to Docker. I've never ran any performance benchmarks, this is just anecdotal.

[–] __init__ 1 points 1 year ago

It depends on how you set it up. You’re going to take a performance hit using a bind mount. The docs recommend putting your workspace into an actual docker volume for better performance, but I haven’t tried that myself cause so far the bind mount has performed “good enough” for me.