291–300 of 328 posts
I run a solo SaaS product with 15,000+ users. I use the "arcane/wizardry" techniques still. I simply run "make deploy" and a new production build is made and rsync'd to production. Then the script executes a "deploy.sh" on the production server which reloads the system process to pick up the new binary. Poof.
A cron job which saves a copy of the DB to S3.
That’s it.
If you’re focused on anything more with no employees you’re probably wasting your time.
This seems to (strangely) be an unpopular answer here, but I've spent a weekend to terraform everything. I run a couple of different projects which are yet to pick-up traction, so prototyping quickly is essential. What I have now is terraform on Github which handles Networking (VPC, subnets), ECS/ECR, ALB for my backend and S3/CloudFront for frontend. Everything is on AWS because I'm familiar with it, so it's faster.…
Later, I realized that Heroku + Netlify are good enough. Switching was easy. The hardest part was admitting to myself that I had wasted so much time on AWS. I felt relieved after I deleted the Terraform and Packer code.
No k8s for sure.
At the start of this year I joined hands with Chris on https://hatchbox.io to work on cost effective deployment service. We are putting together all the deployment best practices we've learned over the years into this product in a cost effective way.
Earlier quoted context omitted.
My experience says to backup to a different vendor.
This is part of my threat model. Is there an easy way to do this with e.g. hosted RDS or block storage device snapshots?
Because everyone here is hell bent on "spooky arcane oldhat sysadmin deploy techniques", I'll share my setup using k8s. - CI on github actions - Project management on post-its (short) and READMEs (long term) - deployment is done by a github action trigger on the `main` branch - Hosting is using AKS, GKE, or on-prem k3s on a raspberry pi. Want to restart a service ? just kill the pods. - Devops took about 2 days of wo…
> Note: this is highly effective because I already had significant K8s experience, so, if you're still learning about what Ingress-Controller to choose for your OIDC proxy, then don't go that route. What would you recommend instead ?
You have a lot of freelance work and devops positions that will give you that experience. You shouldn't try to do this alone, you need guidance to understand how this ecosystem works.
In my case, I have tried MetaCall: https://metacall.io
Because everyone here is hell bent on "spooky arcane oldhat sysadmin deploy techniques", I'll share my setup using k8s. - CI on github actions - Project management on post-its (short) and READMEs (long term) - deployment is done by a github action trigger on the `main` branch - Hosting is using AKS, GKE, or on-prem k3s on a raspberry pi. Want to restart a service ? just kill the pods. - Devops took about 2 days of wo…
>> Job scheduling is built-in (and -fuck- logs are much more accessible on a failed job container than in a custom cron + sh solution)
Can you expand on this? How do you handle logs?