💾 Archived View for singletona082.flounder.online › gemlog › phlog › gopher_stumbles_01.gmi captured on 2023-09-28 at 15:54:59. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-12-03)
-=-=-=-=-=-=-
There were some initial stumbling blocks getting gopher set up. Fine the basics take care of themselves when it coms to setting up pygopher on a debian based system. just sudo apt-get install pygopher' and then edit the config file to do what you want it to do and off you go, restart the server to reload the new configurations, then reload again each time there's a content edit.
I tried to follow what amounted to an automated generator:
https://gmap.dotcomboom.repl.co/
That sorta overcomplicated things. Yet at the same time? The real fault was found through more digging.
This link finally got me on track for sorting things out.
https://prgmr.com/blog/gopher/2018/11/09/setting-up-gopherserver.html
Turned out when setting the server's root path? I should have realized any local links after that? Need to tread that like the root of everything.
Before I was typing /home/USER/gopher/phlog
Instead I needed to define the phlog directory as /phlog
And call that good. Turns out I was overcomplicating things. Funny how that kinda thing works out. I go with an old format specifically because it is resource light and is text centric, and 'duuurrr how do I make it do the thing.' Ah well, no new venture comes without stumbling blocks. Dust myself off and keep on going.
Edit: 10.21.2020
I find the fact pygopher does not update content changes automatically annoying.