glab VS upspin

I don't know if you know about the history of the cli. For years it was looking like a hobby project from ProfClems https://github.com/profclems/glab and then it was adopted by Gitlab as their official CLI.

it's not official, but I like https://github.com/profclems/glab

#1: GitLab offering free certification for a short time | 19 comments #2: renew-le-certs | 0 comments #3: GLab v1.13.0 released: glab is an open-source GitLab command-line tool bringing GitLab concepts to your terminal next to where you are already working with Git and your code | 6 comments

For GitLab users, there is a project trying to give the same UX and functionality: https://github.com/profclems/glab

glab is able to do this

If ${repo} starts with gitlab, then use glab to clone the repo

Take a look at https://github.com/profclems/glab.

The `glab auth login` flow now includes a step to authenticate git as well when "HTTPS" is selected as the default git protocol. This enables git operations like clone, push, etc to automatically work with GitLab on a spotless system after the user has authenticated to `glab`

Check out the new features available in [v1.17.0](https://github.com/profclems/glab/releases/tag/v1.17.0)

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.