core VS upspin

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.

Super intriguing. Thanks for sharing!

It reminds me a bit of an early Go project called Upspin [1]. And also a bit of Solid [2]. Did you get any inspiration from them?

What excites me about your project is that you're addressing the elephant in the room when it comes to data sovereignty (~nobody wants to self-host a personal database but their personal devices aren't publicly accessible) in an elegant way.

By storing the data on my personal device and (presumably?) paying for a managed relay (and maybe an encrypted backup), I can keep my data in my physical possession, but I won't have to host anything on my own. Is that the idea?

https://upspin.io/

There are a few Go projects meant to be learned from:

- https://github.com/pion/opus for to learn audio

- https://github.com/benbjohnson/wtf for overall production quality

- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors

You could also take a look at some real-world open-source projects. I like upspin for its idiomatic approach.

For example, Rob Pike's upspin places all its validations in the separate package. Do you agree with that approach? Which yet proven options there are?

Just a few projects that could perhaps interest you in terms of design of your own solution :

Upspin: https://upspin.io/

The early error wrapping work which emerged out of the Upspin project, that eventually made its way into the errors package, included stack traces in the wrap error. This would provide exactly what it appears you seek.