There's not much on it yet. It uses my special software #burrow to build the gopherhole. I'll write about the setup soon.
I still really like my phlogging module as seen here in #burrow: https://github.com/hyperrealgopher/burrow/blob/master/src/Phlog.hs #haskell
Linux x86_64 friends: here's a pre-release static build of #burrow!
Try cloning https://github.com/hyperrealgopher/burrow and running this command:
burrow --source example-gopherhole/ --destination built/ --spacecookie
I made a #github #workflow for #haskell which enables you to tag for a release and the workflow will set your project.cabal to the version specified by the tag, make a commit that moves the tag to that new commit, and make a release for that tag which includes a static binary that is in a tar.gz.
Speaking of which, here's the first release of #burrow (an alpha) which was built with that system: https://github.com/hyperrealgopher/burrow/releases
Could someone please give this test static build of #burrow a try (just try building the example gopherhole like the README in the repo mentions)?
More info: https://github.com/hyperrealgopher/burrow
Taking time to configure more stuff on my server, go over backups, get my bouncer back online, and some other server-related-things.
A good opportunity to start using #burrow and restarting my gopherhole. Maybe I'll setup my gopherhole with a git service and something that watches files for changes... that would make a good docker image.
I think I will just remove the option to specify an input and output directory with the CLI in #burrow for now and just totally rely on the INI/config file. Debating if I should just assume .gophermap support through a daemon like Spacecookie or not right now.
Thanks for your input!
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.