I thought I would write a little about my experience with
installing the Gophernicus server software, as it's not entierly
trivial how one should get it going. Initially I tried
installing it via the apt repositories, by doing the usual
apt-get install <package>
This turned out to be an extremely bad idea, since it installs
only partially, leaving out important things like the listener
socket in the OS. It also fails to properly read from the root
directory. It does see the files in the directory, but it can't
do anything with them. I spent way too many hours on that, and
nearly gave up.
I then decided to try the other approach, of manually building
it from source, using the github repository, simply following
the instructions. This worked a lot better, but I still had
some minor issues. The problem was that that it simply would
not compile. After some digging I found out that I was missing
the build-essential package, which can be installed from the
apt repositories. After I installed that, Gophernicus
compiled without issues, created the root directory
automatically, with a gophermap demo file and all. I also got to
pick the socket listener this time. I picked systemd, since it
was already in the OS. It then allows you to start, stop and
restart the server by typing
systemctl <start/stop/restart> gophernicus.socket

So the bottom line is, don't bother with the apt repository
install option. It's just buggy and weird. Building it from
source is totally the way to go.

-Headcrash

You are viewing proxied material from gopher.deadnet.se. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.