core VS Buildkite

As a recap, StaticBackend is a simple backend server API easy to self-host or importable in Go program without hosting a separate server.

StaticBackend is a simple backend server API you may use to build complex web applications. Fully open source and easy to self-host. It handles lot of backend building blocks.

I want to put StaticBackend on your radar. It's an open-source backend API I've worked on for more than 3.5+ years.

I'd like to put StaticBackend - GitHub in your radar. It's a simple backend server API that tries to handle most of the common functiionalities found in web applications. It's open-source and very easy to self-host.

Since people often ask where they could contribute to a Go project, I thought I'd jump in as I took some times to create some good first contribution issues for StaticBackend.

It's not always present in issues what has to be done in a project. On that note, I'd shamelessly suggest to look at StaticBackend which is a backend API to help expedite v1 (MVP) launch time.

I can tell you what I like and don't like about my open source backend API (self-hosted Firebase) https://github.com/staticbackendhq/core

Hey, if you're interested in web backend I started StaticBackend - GitHub repo in 2019. It's a REST backend server which aim to provide most of the common building blocks like user authentication, database, file storage, websocket, schedule tasks, server-side function.

buildkite.com you can run agents where ever you want.

Give https://buildkite.com/ for CI/CD a try, you'll love it!

Even that niche has better competitors, I think. I haven't used on-prem CCI, but I used hosted CCI for several years and when my team switched to https://buildkite.com/ it was a huge breath of fresh air. I think BuildKite is the only CI system I've used I thought was actually worth paying for, and I bet it works out cheaper than self-hosted CCI in most cases as well.

Buildkite: a startup that offers a CI/CD platform that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI.

At Redpanda, we want to always provide an experience that is fast, simple, and productive for developers. That applies to our own team of engineers, too. When considering how we could achieve a more stable continuous integration (CI) pipeline, we wanted that same experience: fast, simple, productive. By running multiple instances of our pipeline steps in parallel on our CI platform, Buildkite, we can now run multiple repetitions of the same Buildkite step and use only the amount of time needed for a single step.

> You can also get comparable performance out of https://buildkite.com/ which lets you self-host runners on AWS

you can self-host github runners as well, with a few caveats, the most serious one being that then you are responsible for cleaning up the state of your self-hosted runner between runs

https://docs.github.com/en/actions/hosting-your-own-runners/...

structural isolation guarantees of the form (build execution during run N cannot possibly impact build execution of run N+1) are tremendously helpful, if you cannot offer similar guarantees when self hosting then it may not be wise to self host.

A better option, if you want to run the builds on your own hardware is to look at something like Buildkite or GitLab CI.

One of the integrations that sends Change Events to PagerDuty is Buildkite. Buildkite is a continuous integration pipeline that allows you to notify PagerDuty with just the information you want to know. Conditional rules allow you to send only what matters.