Lita VS Capistrano

Location: Oakland, CA

Remote: Exclusively

Willing to relocate: No

Technologies: Rust, Axum, Ruby, Ruby on Rails, TypeScript/JavaScript, Node.js, PostgreSQL, Python, Flask, AWS, Docker, Kubernetes

Résumé: https://www.jimmycuadra.com/jimmy_cuadra_resume.pdf

Email: jimmy@jimmycuadra.com

I was laid off by Cisco Meraki last summer, where I spent four years as a technical lead for the cloud side of the wireless products. I have experience in both web development and cloud infrastructure roles.

I have worked for years in open source software development. I created and ran two notable open source projects: Lita, a ChatOps framework for Ruby (https://github.com/litaio/lita) which is used by many companies for automating internal operations and workflows, and Ruma, an implementation of the Matrix protocol in Rust (https://ruma.dev/) which went on to become the basis for the official Rust SDK for Matrix.

My ideal role would be building software targeting other developers, either as a member of a developer tools team, or for a company whose products are made for developers. I'm also drawn to companies building "neutral" utilities whose value is fairly self-evident: Things like PagerDuty and Stripe which are generally useful and provide the infrastructure needed for other things to work.

I would love to use Rust professionally, but I'm fine with other languages, too. I'd also be very happy to work on a product with an amount of open source code, given my background working on OSS projects.

Email: jimmy@jimmycuadra.com

I was laid off by Cisco Meraki last summer, where I spent four years as a technical lead for the cloud side of the wireless products.

I have worked for years in open source software development. I created and ran two notable open source projects: Lita, a ChatOps framework for Ruby (https://github.com/litaio/lita) which is used by many companies for automating internal operations and workflows, and Ruma, an implementation of the Matrix protocol in Rust (https://ruma.dev/) which went on to become the basis for the official Rust SDK for Matrix.

The previous deployment was using capistrano v2, and the client wants to stay with the same deployment method. So I just upgraded the code to use capistrano v3.

Yes, we can! Rolling out new code updates, features and hotfixes is what we do constantly. At context of our web projects written with Ruby on Rails, it’s a question of a single command to start deploy. For this purpose we use capistrano https://github.com/capistrano/capistrano

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.