myapp VS upspin

I would love to suggest https://github.com/learning-cloud-native-go/myapp and https://learning-cloud-native-go.github.io/ some open source side projects I am working on.

https://github.com/learning-cloud-native-go/myapp shows how to build a Dockerized RESTful API application using Go. It includes a sample RESTful APIs/ CRUD build using Go net/http with Chi router, Postgres, DB migrations, Configs via env variables, Zerolog structural logs, Validator v10, Gorm.

You need to set these env variables/ configs. https://github.com/learning-cloud-native-go/myapp/blob/main/.env

Some open source projects I am currently working on, - https://learning-cloud-native-go.github.io/ - https://github.com/learning-cloud-native-go/myapp

Checkhttps://github.com/learning-cloud-native-go/myapp

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.