Deployer VS cz-cli

Deployer offers PHP developers a streamlined, zero-downtime deployment process, supporting major PHP frameworks. It is the ideal choice for secure, interruption-free deployment, automating and simplifying deployment tasks in the PHP environment.

I use deploybot.com to handle like 10 different Drupal installs, on a shared hosting. See also https://deployer.org but you can have your "light" platform.sh on a reasonably cheap shared hosting.

Yes, in combination with PHP deployer: https://deployer.org/

Is there an equivalent for deployer in .NET world?

https://deployer.org/

We have recently moved from jenkins + deployer.org to envoyer.. Alot of value and ease of life considering the monthly fee....

I would also check out PHP Deployer (https://deployer.org/) as an open source/free alternative to some of those paid solutions mentioned in other comments.

setup blue/green deployments or go fancy with something like deployer

Deployer https://deployer.org/

I'm not looking for a hosting, i'm looking for the equivalent of deployer.org for node. A package that handles the process to git pull, install dependencies, rollback if necessary, etc... When i search for "how to deploy a node app" all i get is tutorials on how to deploy to Heroku, Vercel & other cloud providers :(

If you aren't then https://deployer.org/ is pretty easy for beginners

Adopt a convention like commitizen: https://github.com/commitizen/cz-cli

'typeofchange(scopeofchange): reason for change'

It sort helps force devs to type out more meaningful commit messages.

Commitizen Define a interface to write your commits and automatically and a prefix and a suffix to your message. (and others features not related)

Conventional commits are great, especially if you add in commit linting.

Being able to programmatically increment semantic versions and automatically generate relevant changelogs is awesome.

It’s also nice to implement Commitizen[0] for a little hand holding until folks get used to the linting.

I used to care a lot about doing things the way that felt right to me, but now I just want some common standard that is easy for everyone to follow, easy to automate, and easy to verify programmatically.

Things like conventional commits and semantic versioning aren’t perfect, but they are quite good and apply broadly to many use cases with common tooling and conventions.

--

[0]: http://commitizen.github.io/cz-cli/

In the world of software development, maintaining consistent code quality and ensuring that the codebase adheres to predefined patterns and guidelines is crucial. However, manually enforcing these standards can be time-consuming and error-prone. This is where automation tools like Husky, Lint-Staged, Commitlint, and Commitizen come to the rescue. In this post, we will explore how these tools can be combined to streamline your development workflow.

Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.

When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.

I use Commitizen to enforce a strict commit message. It's not required - but it makes my life easier. It adheres to a standard - but it's certainly not "the" standard.

When I googled, I found cz-cli project first: https://github.com/commitizen/cz-cli

Same thing with git commits. Something like commitizen. It forces a specific format of your commits. And if you're using an associated issue/bug tracker that can automatically link to commits you can set up to format like that.

That may also serve as a good entry point for nodeJS via the tools: commitizen, commitLint. That is you implement them within your project, and then also think about how to implement via CI/CD remotely.