Thanks for the comment! Yes this is meant more for your personal projects than for using in existing projects

The idea behind needing a password to get a password, totally understand, my main goal was to have local encrypted storage, the nice thing about this implementation is that you can have all your env files saved and shared in your git repo for all devs to have access to, but only can decrypt it if given the master password shared elsewhere (keeper, vault etc) so you don’t have to load all values from a vault, just the master

100% though this doesn’t cover a large range of usage, hence the name “simple” haha, wouldn’t be opposed to expanding but I think it covers my proposed use cases as-is

You could definitely do clever things to obfuscate what you’re doing, but it’s much easier to replicate building the image as there are no external dependencies, if you have docker installed then you can build any docker image

When you make a docker image and push it to dockerhub all of the instructions it took appear there so it’s very transparent, also super easy for any person to build it themselves unlike executables, just download the Dockerfile and run a single command

Besides the obvious of telling your users to build the exe, have you considered alternative distribution methods like docker?

I have the snap installed, for what it’s worth it’s pretty painless AS LONG AS YOU DON’T WANT TO DO ANYTHING SILLY

I’ve found it nearly impossible to alter the base behaviour and have it not entirely break, so if nextcloud out of the box does exactly what you want, go ahead and install it via snap…

I predict that on docker you’re going to have a bad time if you can’t give it host network mode and try to just forward ports

That said, docker >>>> VM in my books