What's your DevOps setup?

Github for code
Github actions for CI/CD
Deployed to AWS Beanstalk (Docker for everything)
Trello for project management

BitBucket for code
No CI/CD as it's overkill at the moment - will use Azure when/if needed
Clubhouse for project management and issue tracking (issue tracking (bugs/errors from codebase is automatically created using the Clubhouse API). Critical bugs I also send myself a Telegram message

Hosted Kubernetes on Digital Ocean
Selfhosted Gitlab for CI/CD, issues
Project management: Basecamp
Everything (Go& Rails applications) running in containers in the cluster behind a Digital Ocean load balancer.

Hosting provider: Digital Ocean
Code hosting: Gitlab
CI/CD: Gitlab
Orchestrator: Nomad / Consul
Frontend proxy: Traefik

Everything run in docker container :)

My code is hosted on Gitlab, I'm also using their CI/CD pipelines for automated testing & deployments to AWS. For everything else I'm using Notion.

I'm sure I'll be the odd one out for saying this as it's not particularly hipster cool, but I use the Microsoft Azure Devops tools (https://azure.microsoft.com/en-gb/services/devops/).

It's free, they provide private git repositories, and pretty good CI and CD pipelines that integrate well with their Azure offering. You can also hook it up to pretty much any service (I've set-up CI/CD pipelines for AWS, Siteground, and Netlify recently). You also have the choice to role your own build/deploy agent if you don't want to use theirs or you're doing some on-prem stuff.

Check out Buddy for CI/CD - highly recommend: https://buddy.works

We use Atlassian tools for the rest: BitBucket, Trello, JIRA.

bitbucket for code
build docker containers for prod/stage/dev
push them to rancher controlled k8s cluster
have my own build solution for nginx proxy with letsencrypt ssl termination

Github, no CI/CD, issues and todos in Notion.

I'm trying to keep it as simple as possible and to only add more CI/CD when it would save me time.
There are currently too many other items on my (mental) backlog, that provide way more value than spending too much time on a sophisticated DevOps setup.

Therefore my current setup:

1. A git push hook that runs my test suite locally.
2. A github action that builds and deploys the frontend on a push to master.
3. A hook on docker hub that builds the docker image for the backend on a push to master.
4. A hook on the servers that updates the docker containers with the new image when a new image is available.

All done in the simplest manner possible.

GitHub for code.

No DevOps, no CI/CD or issue tracking - just keep it simple. All those "toys" and big words are mostly a distraction for an indie hacker and was originally back-propagated from the big players like Google and Amazon. They solve a different kind of problems there with these tools.

I like an example of Pieter Levels from NomadList - he serves millions of page views per month and all he has is a freaking plain PHP files and a single server to do so.

Everything in Gitlab.