PgHero VS Capistrano

I am using https://github.com/ankane/pghero/ and this is one of its features with GUI

I use either PgHero or Rails PG Extras on every project

There are tools available which can look at your Postgres logs and tell you if you need to add indexes, I've used https://github.com/ankane/pghero before and it seems decent.

https://github.com/ankane/pghero (open source equivalent to pganalyze)

- [pghero](https://github.com/ankane/pghero)

pghero

If you are using PostgreSQL you can enable logging of slow queries and connect to the server with pghero (https://github.com/ankane/pghero) and check top queries by the number of requests and total usage time. Also, you can just enable logging of queries in Django, and on each request, you will have a list of queries on development, sometimes it's just a missing select_related of prefetch_related to increase performance, or you need to create a complex index.

If you are using rails, pghero is a great gem to get better visibility on your Postgres performance

https://github.com/ankane/pghero

I know others can answer this better but we use a combination of PgHero and logging of slow queries trough jOOQ.

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.