
I suggest continuing this discussion/effort on the Haskell Discourse at https://discourse.haskell.org/t/documentation-of-haskell-websites-servers-an... . Howard On Fri, 2021-03-19 at 14:21 -0400, Gershom B wrote:
Cc: admin@haskell.org which remains (since it was set up over five? years ago) the contact address for haskell infra admin stuff. There's also, as there has always been, the #haskell-infrastructure irc channel.
This all _used_ to be on phabricator (and was on the haskell wiki before that) but it wasn't really suited to port over nicely to gitlab. At the request of the still-forming working group for HF, a repo was created on github with key information and policy, and sent to the HF, which should have this documented somewhere already: https://github.com/haskell-infra/haskell-admins
I'll go back and try to read earlier in the thread, if I was cc'd, because I'm just now looped in?
I.e. I see from the message "gitlab is down" but other than that I'm not sure exactly what is at issue?
-g
---
Here's the info I sent the committee last time it asked:
here's the full list of servers. benley (Benjamin Staffin) has been using the two boxes as his tests for mailman migration. the various servers tagged bgamari are all the ghc specific ones. the three hackage servers are matrix, docbuilder, and hackage proper. the two consolidated servers are misc-services-origin and www-combo-origin.
here's info on packet's elastic block storage: https://www.packet.com/developers/docs/storage/ebs/
its a bit fiddly, but we have it working at this point.
Davean, Herbert, Ben and me are the ones who have keys on almost every box, I think. Alp and Austin are both officially team members but I haven't interacted with them much (austin is legacy, and alp may only work with Ben on ghc stuff, idk).
Davean manages backups.
some significant subdomains hosted: archives.haskell.org, hoogle.haskell.org, downloads.haskell.org, wiki.haskell.org
there are some other smaller subdomains such as summer.haskell.org, pvp.haskell.org, etc.
here are the main static subsites of haskell.org, most of which have existed at those urls well prior to the existence of a haskell.org website beyond the wiki
alex communities ghc- perf happy hoogle onlinereport
arrows definition ghcup haskell-symposium hugs platform
cabal ghc haddock haskell-workshop nhc98 tutorial
Sadly, joachim didn't keep up ghc-perf which was nice while it was working.
On Fri, Mar 19, 2021 at 2:13 PM
wrote: Hi Richard, Gershom and Ben,
I have access to the server that runs the Haskell wiki. There are other websites on that server as well. I can document them as well. I know that Gershom B. has done most (all?) of the work on that server. I ask him and the haskell.org committee to send me or point me at whatever documentation they have already.
I ask Ben and others with any documentation of gitlab.haskell.org to send me or point me at whatever they have already.
I don't want to do this alone. Other volunteers are welcome! I also will abide by the Haskell Foundation and the haskell.org committee in arranging this documentation according to their needs and preferences.
Howard
On Fri, 2021-03-19 at 17:32 +0000, Richard Eisenberg wrote:
On Mar 19, 2021, at 12:44 PM, howard.b.golden@gmail.com wrote:
I would like to help however I can. I already maintain the Haskell wiki, and I would like to improve and document its configuration using devops techniques, preferably consistent with gitlab.haskell.org.
Thanks, Howard!
I will try to take you up on your offer to help: do you think you could start this documentation process more broadly? That is, not just covering the Haskell Wiki, but also, say, gitlab.haskell.org. (You say you wish to document the wiki's configuration consistently with gitlab.haskell.org, but I don't know that the latter is documented!)
Ideally, I would love to know what services haskell.org hosts, who runs them, and what happens if those people become unavailable. There's a zoo of services out there, and knowing who does what would be invaluable.
Of course, anyone can start this process, but it takes someone willing to stick with it and see it through for a few weeks. Since Howard boldly stepped forward, I nominate him. :)
Thanks, Richard