self-contained-runnable-python-package-template VS awesome-devops

The approach I prefer is to not mess with setuptools etc at all in the first place, and simply make a nice executable package.

e.g. https://github.com/tpapastylianou/self-contained-runnable-py...

The title should be: How to create a "Python DISTRIBUTION package".

The term "python package" means something entirely different (or at the very least is ambiguous in a pypi/distribution context).

To add to the confusion, creating a totally normal, runnable python package in a manner that makes it completely self-contained such that it can be "distributed" in a standalone manner, while still being a totally normal boring python package, is also totally possible (if not preferred, in my view).

Shameless plug: https://github.com/tpapastylianou/self-contained-runnable-py...

Shameless plug: I use my own template, which organises things as runnable projects.

https://github.com/tpapastylianou/self-contained-runnable-py...

It serves my purposes very well (which is creating projects that represent standalone experiments).

Sharing in case someone else here finds it useful.

More recently I've modified this a bit to also generate nice html reports straight from the __main__.py file, independently of the underlying python code, and use this as lab books (where each lab book contains a single analysis and its report). I'll upload this template separately when I find the time.

I would start with awesome devops and drill down there to which tools and projects are open source and in go. I know that Terraform is in go, Docker itself is in go, some projects that I use like Telegraf are in go too, but a comprehensive list of all tools that can be used by devops, that are open source and in go may be huge. Is better to get a very partial list and pick from there the ones you find more interesting, both in mission and in code.

github.com/wmariuss/awesome-devops

Not necessarily, it just depends on how invested you are in the CI/CD pipeline for any given project, your preferences regarding self-hosting vs. cloud, and the amount of time you have to dedicate to the subject.

Strictly speaking, any tool or set of tools that allow you to trigger building & deploying/publishing artifacts in response to source control commits can be used to build a CI/CD pipeline. One could write bash scripts linked to a cron job that pulls a remote repository every n minutes and then performs some scripted actions to integrate changes between branches before building & publishing the artifact to a local SFTP server.

If you prefer a more mature solution with better documentation however, there is a (non-exhaustive) list of CI/CD tools on this awesome-devops list:

https://github.com/wmariuss/awesome-devops#continuous-integr...