marionette
semver
marionette | semver | |
---|---|---|
2 | 727 | |
86 | 7,063 | |
- | 0.5% | |
3.0 | 0.6 | |
about 1 year ago | about 1 month ago | |
Go | ||
GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
marionette
-
Why are there no descent Go or Rust alternatived to Ansible?
I wrote a simple tool, which is modeled after puppet in terms of syntax. It was mostly an experiment to see what minimum required features are enough to provide something useful - and I settled on a few primitives such as creating files, installing packages, and running commands.
Despite the minimalism it turned out to be more useful than expected:
https://github.com/skx/marionette/
I added extra things, such as the ability to pull docker containers, and clone git repositories, and despite being single-host I'm using it to setup several virtual machines.
-
Ansible 4.0.0 final has been released
I wrote a proof-of-concept tool, inspired by puppet more than anything, but since it runs locally it is perhaps comparable to ansible too:
https://github.com/skx/marionette/
It turns out that three operations suffice for almost 90% of my needs:
* Populate a file, from a template with variable expansion.
* Run a shell-command.
* Install a package.
I added support for pulling a docker container too, just for fun. Although I never made the effort to pimp/promote it, the tool is stable and useful as-is.
semver
-
The right development flow: Better than Agile
We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-releaseβ¦
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
What are some alternatives?
puppet-summary - The Puppet Summary is a web interface providing reporting features for Puppet, it replaces the Puppet Dashboard project
react-native - A framework for building native applications using React
habitat - Modern applications with built-in automation
semantic-release - :package::rocket: Fully automated version management and package publishing
community.kubernetes - Kubernetes Collection for Ansible
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
helmfile - Deploy Kubernetes Helm Charts
Poetry - Python packaging and dependency management made easy
TermuxBlack - Termux repository for hacking tools and packages
fswatch - A cross-platform file change monitor with multiple backends: Apple OS X File System Events, *BSD kqueue, Solaris/Illumos File Events Notification, Linux inotify, Microsoft Windows and a stat()-based backend.
keep-a-changelog - If you build software, keep a changelog.