dagu VS core

I am developing an OSS workflow scheduler called Dagu with the goal of developing a simpler workflow scheduler to replace Airflow.

DAGU is in the early stage and aimed to be a good alternative workflow engine for smaller use-cases or existing codebases that need to be organized without hassle or high learning curve.

Hi, let me share my open source project, Dagu. It is a No-code workflow (DAG) executor. With Dagu, you can define workflow in declarative YAML format. It is self-contained and suitable for smaller projects with fewer people. Please try it! :) https://github.com/yohamta/dagu

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.