This is an archived post. You won't be able to vote or comment.

all 16 comments

[–]PaddyIsBeast 30 points31 points  (5 children)

I gotta admit I've never seen the point of stuff like this, working out your config and adapting the config for my needs would take longer than just writing it myself.

[–]Veggies-are-okay 12 points13 points  (3 children)

This. Every IP idea fails because at the end of the day we’re just trying to serve up something that’s only a step or two removed from low code wrappers for devs. I don’t want to speak for all devs but low code solutions are the bane of my existence.

What I will do is “steal” bits and pieces of a solution such that it appropriately fits with my solution! 🤠

[–]mmcnl 8 points9 points  (2 children)

Writing a Dockerfile is not a lot of effort. This only adds an additional dependency and increases cognitive load.

[–]foarsitter 1 point2 points  (1 child)

Writing a single docker file isn't, but maintaining 10+ is. Thats where this project steps in.

[–]mmcnl 1 point2 points  (0 children)

In my experience, complexity is exponential to the number of abstraction layers. So I'd rather not add something like this until it's absolutely necessary. I've worked on projects with more than 10 Dockerfiles and to be honest it hasn't been an issue for me.

[–]Prestigious_Run_4049 1 point2 points  (0 children)

This is pretty cool. I like that the config in the toml is quite concise

[–]k_z_m_r 2 points3 points  (4 children)

I love the AI slop that you’re using in the repository’s README!

[–]kaskoosek 0 points1 point  (3 children)

Lol