I appreciate the spirit, but to shine some more light around the negativity you’re seeing in the comments, it’s a lot to ask for others to run your code on their machines. If you want folks to be running in docker, that’s oftentimes basically giving root access.

If I’m giving root access, I’d at least want for the person who wrote the code to have a thorough understanding of what the code, which once again is running as root on my home network, is doing.

The LastPass hack a few years back was enabled by a self-hoster running an outdated version of Plex on their personal machine. There is weight in choosing what software to run and support in your personal setup. The negativity you’re seeing is due to the belief that vibe coding, while able to produce something functional, is not reflective of solid, sustainable, and secure software development practices, and simply does not meet the bar for code to give root access to. It’s (probably) not personal.

virtually all home server setups run docker compose. no one is complaining about Docker, they’re complaaining about AI. The code is immaculate. Its fully tested as well. No one as looked at the code.

Also idk where you heard Docker is like giving root, thats just not correct on multiple levels. If it were a privledged container, which is unnecessary, then we could have a discussion. If you want a daemonless service, use podman. Use anythign you want, the source is there. Docker is not a requirement but is certainly not an issue in any way.

Hokay. So docker does run as root. Podman can run rootless, but docker does run as root.

So if you have any vulnerabilities in your code, like say remote code execution, than your app already has access to root.

Also, don’t pretend like your shit don’t stink. My code has bugs. And I’ve been at this a a decade. Your vibe coded thing isnt going to be secure because you probably don’t even know how to make it secure if you don’t know docker runs as root.

Here’s where I interject my opnion

Its fine to do this for yourself. If you wanted to hear how great your AI produced slop go to LinkedIn.

When you share things to be used by others, you have a responsibility yourself. How will you monitor and package up security updates? What kind of depenecinies do you have? Are they up to date? Do they have any CVEs?

There’s so much more to publishing than good intentions. Its fine to do something like this for yourself. But to publish and then absolve yourself of any responsibility is not a way to get taken seriously.

No to be clear, open source code owes you absolutely nothing at all and has zero responsibilities. It’s important that you know that.

Personally, whether or not this will be maintained in the future is the biggest reason why I’m unlikely to try this. If the main developer vibe-coded it up, then in my book there’s a lower chance that the codebase will be maintained in the future.

If your response to “How will you maintain this?” is “nothing is owed”, it really cements the idea that this will not be maintained.

If an application is unlikely to be maintained in the future, then the risk-reward ratio will rarely justify me incorporating it into my workflow.