Golang

2230 readers

1 users here now

This is a community dedicated to the go programming language.

Useful Links:

Rules:

Posts must be relevant to Go
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 2 years ago

MODERATORS

Ategon

RandomDevOpsDude

austin

GoHome: A simple app to host your Go modules with vanity URLs (deddit.petersanchez.com)

submitted 11 months ago by [email protected] to c/golang

2 comments fedilink hide all child comments

Repo: https://git.code.netlandish.com/~petersanchez/gohome

I wrote a simple application to easily manage your Go modules that you host on your own domains, backed by sqlite3.

I know there are quite a few ways to do this (nginx hacks, static pages, other server apps) but none of them scratched my itch. I wanted a simple utility that I can add/edit via my web browser and be done with it. No config file changes, no server reloads, etc.

Happy to hear all feedback.

Blog post (if you care): https://petersanchez.com/easily-host-go-modules-on-your-domain/

you are viewing a single comment's thread
view the rest of the comments

[–] atheken 1 points 11 months ago* (last edited 11 months ago) (1 children)

Considering the implications of relying on an external company as the registry, I don’t think custom domains are really “vanity” as much as reserving agency to move the code if it becomes necessary. I’m perfectly happy with GitHub, but would rather my modules didn’t break if they implement a policy change at some future date. I also don’t like the implication that “GitHub owns” my repo due to the import path stuff.

That being said, I wonder if this same thing could be achieved with a simple reverse proxy/CDN with a few rewrite rules? Ideally, the only cost to a typical maintainer would be the domain name, and the rest could be hosted on free infrastructure (cloudflare would seem like a reasonable choice).

[–] [email protected] 1 points 10 months ago

Yea, that's my main thing. I don't want to be "stuck" on a forge I no longer want to continue using.

I'm sure you can wire up many ways to do it with a simple CDN, etc. Previously I was using nginx rules to serve it. I know others who use simple static html pages. There are many ways to get it done. My module is just one way that works for me.