> curl -v godocs.io
* Trying 173.195.146.154:80...
* connect to 173.195.146.154 port 80 failed: Timed out
* Failed to connect to godocs.io port 80 after 21009 ms: Timed out
* Closing connection 0
curl: (28) Failed to connect to godocs.io port 80 after 21009 ms: Timed out

between this and the standard library being broken for two weeks:

https://lists.sr.ht/~sircmpwn/godocs.io/%3CCAP8dQmuDD_DHaA4TDf9VB-Cr5rKbfBaFtBQ%3Dqcoc7tbvpCDnxw%40mail.gmail.com%3E

I am sick and tired of the issues. since I am also not a fan of
https://pkg.go.dev. I found an open source tool that generates Go docs. It
doesn't currently support versioned docs, so I added that feature myself:

https://github.com/3052/doc2go

You need to be more respectful in your communication. If you're ready to
move on then do it, no need to be spiteful on your way out.

Sorry for the issues. godocs.io is maintained in my free time, so I'm not able
to address issues right away.

The site needed to be migrated to a new server. It should be working now. If you
have any issues, let me know.

The standard library is still broken, but I hope to address that soon. In the
meantime, you can choose the latest version from the versions page.

If you still want to self-host your own docs, you may be interested in this
tool: <https://code.pfad.fr/vanitydoc/>. It's based on the templates used by
godocs.io.

On Fri, Jan 19, 2024 at 3:52 PM Adnan Maolood wrote:
> The site needed to be migrated to a new server. It should be working now.

Before the outage, I used https://godocs.io daily, as my main source
for Go documentation. I did so because honestly https://pkg.go.dev is
a hot pile of garbage. it just reeks of over engineering shit that
permeates web development these days. so I really do appreciate GoDocs
and you as well. GoDocs is great because it's a simple style, like
http://godoc.org before it.

However, GoDocs being down for two weeks, or defaulting to 7 year old
packages, is not something I can put up with. Again, I appreciate all
you have done, but with the repeated issues I have posted over the
months, I am just mentally done dealing with http://godocs.io. I need
something that more or less works consistently and without headaches,
and GoDocs has never been that. I guess this outage is good, because
it forced me to confront that fact, and find another solution.

> If you still want to self-host your own docs, you may be interested in this tool: <https://code.pfad.fr/vanitydoc/>.

I checked it out. I love the code because they managed to avoid any
third party imports, which you rarely see these days. but it seems the
code is not robust currently, and is severely lacking documentation:

https://codeberg.org/pfad.fr/vanitydoc/issues/1

however my pull request was accepted, so I think I have a tool I can use now:

https://github.com/abhinav/doc2go/pull/175