Deployer VS Capistrano

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

If you don't want to go down the NFS share route then Capistrano is a useful tool if you're willing to write a little bit of ruby. It comes with some built in goodies like rollbacks. It's an oldie (pre-dockerize everything), but still useful.

https://github.com/capistrano/capistrano

You can start by deploying from your machine to simultaneously get it deploying across all your servers, then I'd consider having a CI/CD pipeline take over and run Capistrano for you.

- Integrate automation deployment: [capistrano](https://github.com/capistrano/capistrano)

Integrate automation deployment: capistrano

The deployment process generally includes making the new version available, directing traffic from the old to the new version, and stopping the old versions. Capistrano has been doing this since 2006. However, what makes Kubernetes deployments better is the minimum number of pods required, and its rollout strategy minimizes or eliminates downtime. For example, a rolling update strategy can ensure new pods gradually replace old pods with configs like maxSurge and maxUnavailable. Because this is done in a declarative way, as a user or operator, you only need to ask Kubernetes to apply a given deployment and Kubernetes does the rest. Next up is the Kubernetes config map.

[1] https://github.com/capistrano/capistrano

Capistrano

What I had considered was writing a deployment script where upon successful build in a separate folder, it'd swap out the deployed folder, similar to how Capistrano works. It has a "current" folder and it'll build in a temporary folder and then replace the symlink to a newer build.

capistrano with plugins for deployment

deployer is a deployment tool written in PHP. It comes with "Zero Downtime Deployments" out of the box and can be extended by writing simple PHP code. (capistrano would be the equivalent in the Ruby world).

Capistrano, if you like Ruby.