If it helps:

I build full stack, mostly polyglot applications (usually C and C#) frameworks w/web-apps and I just take my Linux bundles and package them inside a container as part of a CI. The requires user's users to build containers locally, but it does ensure that builds are consistent with bare-metal and containerized, plus it makes CI easy. I then give users a Taskfile.dev script for cross-platform bootstrapping. It's not a complete solution, but I think it's a good middle ground.

That being said, it now cost's me very little, aside from testing time, to target both containers and bare-metal.

Reply to this note

Please Login to reply.

Discussion

CI = continuous integration? I’m learning new words 😅

Lol, yessir! There are so many different things. Again personally, I built my own tools for CI because there are so many big tools that can get you stuck in their way of building things IMO, or stuck working inside docker containers making your repo all messy. I opted for using https://taskfile.dev and my custom orchestration tool.

Crazy example, but this is my Simple-Bookmark app. You can see the taskfile.yaml files that do all the build steps, including the container package.

https://github.com/VnUgE/Simple-Bookmark/tree/master/ci

And then magically, the output is put into my S3 server available for download on my site. lol

https://www.vaughnnugent.com/Resources/Software/Modules/Simple-Bookmark

Bookmarks! I know someone who loves bookmarks … nostr:npub12zqf55l7l9vsg5f6ssx5pq4f9dzu6hcmnepkm8ftj25fecy379jqkq99h8