Hi,
I recently became curious about gopher, its history, the page syntax and how it all works. To satisfy curiosity I decided to get get "hands-on" with writing a gophermap and see if I could serve that page on my home network. I have a raspberrypi-400 running the 64 bit version of Debian Bookworm. I installed gophernicus with...
sudo apt-get install gophernicus
I then created the required /srv/gopher directory, placed a temporary gopher map file in /srv/gopher and then launched gophernicus with...
gophernicus -h 192.168.1.45 -o UTF-8
This worked and gophernicus now serves gopher pages on my local area network. I can view the pages using the Kristall browser on another machine. Everything seems to be working fine except I have not been able to find a way to stop gophernicus starting automatically when the pi is re-booted. So I wanted to ask, does anyone know if there is a way to start/stop gophernicus manualy?
If I understand correctly, gophernicus runs under the control of "systemctl" but I dont really understand how to make starting-stopping a manual operation. So, I began experimenting and atempted to stop gophernicus with...
sudo systemctl stop gophernicus
That failed to work but after some looking around the system I discovered gophernicus.socket and using the following terminal command...
sudo systemctl stop gophernicus.socket
I was able to stop gophernicus serving pages. Re-starting gophernicus.socket would restore service again...
sudo systemctl start gophernicus.socket
The socket service start/stop command seems to work but I wondered if there is a better way to manualy start/stop the gophernicus server?
Regards,
titanic (AKA Des)
I see that gophernicus has some ways to run a 'virtual server'
which isn't working right now on my server
(lucid.observer and l0tek.press both run on my server)
I was told that using nginx reverse proxy wouldn't help either,
as gopher would have a 'domain' in the url requests.
What other ways could be use to run 2 gopher server on the same
machine? I tried to follow gophernicus virtual domain / server
but that didn't work. Not sure what I did wrong there, I've
setup the 2 domain / home in /var/gopher/...
--
gef(a)sdf.org
https://gef.ink
Hi everybody
First all excuse my poor english. It's not my first language.
I have installed and configured gophernicus on my debian server (my root is /srv/gopher/)
I can access my gophermap locally via lynx. Everything working!
But I can't access via gopher://myip from outside the server!
Do I need to configure anything else?
Thanks for any direction.
Sérgio F. Lima
https://sfl.pro.br
Este e-mail foi escrito por um humano!
Prefiro e-mail que mensageiros instantâneos!
http://psfl.in/use-email
Hello, I installed and launched the Gophernicus server on Linux Debian i686.
I managed to get CGI scripting working. However, I have a problem with passing parameters to the CGI script via itemtype=7.
I don't know how to configure the server to make it work. I tried to apply the information from https://boston.conman.org/2020/01/06.1 but it didn't help.
My server address: gopher://dyn.tuffo.ovh
I make the following call in the gophermap file:
7->Witaj - wprowadzv swoje imieq /cgi-bin/hello.cgi? dyn.tuffo.ovh 70
The script I want to pass a parameter to is as follows hello.cgi:
(the script is executable)
#!/bin/sh
NAME="$1"
echo "iHello $NAME - welcome to $HOSTNAME"
exit 0
Please help.
I'm trying to set a gopher server for the first time. However nothing
seems to work!
First I plan to Reconfigure all the stuff on the command line.
Robert D. Houlihan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I posted in chan about this, but I'll post it here on the official
list as well.
https://github.com/gophernicus/gophernicus/issues/97
All the best!
- --
Bradley D. Thornton
Manager Network Services
http://NorthTech.US
TEL: +1.310.421.8268
-----BEGIN PGP SIGNATURE-----
Comment: Find this cert at hkps://keys.openpgp.org
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQEzBAEBCAAdFiEENWT7St9Eg6sLyiLAuIw5wQytyEkFAmCvvysACgkQuIw5wQyt
yElEXAgAonhzaPSqjTdbv6cw8qE/J0nWhWQK7cQq8Ajyg6pDXuO0Akcy/0IlFyKj
1FQ4/SLaW4LKlq9xURXh295ZO5C1o3Acncy/U9zUcBzD+m/Ph+8x6gAPtZrU5K4s
9AS+Ala4ruCJKp244OCsSrS/MZNVfXnZ1KXKNCs6T+2RAlsuThqiDF7JRr+6rpTU
8ldpGm8z6aelRw2FYflAIa6J/+ctIjJaNx6sFHZSPoVRKXb3Ckp9ybND2XkJImnE
9tFC83X41uuSA89aJFLClzYu0n1UhjGwQqq11th92yc+SYnUHwazQsm2cHXvlRZW
XdFN8AfpFhVPfBsx0C8SJuvIA6pukA==
=H7Jg
-----END PGP SIGNATURE-----
Hi all,
Gophernicus 3.1.1 is a small build system fix release that makes various
configurations and listeners work correctly and makes it more clear as
to what extra steps are required by the user in this version (3.1 and
up). Also, it makes it obvious that a listener was required, whereas the
configure script would previously erroneously succeed even when no
listener was given.
Changes:
* Fix various build system issues
* Add better install messages
Binaries are not being recreated for this release, as there is no
difference between 3.1 and 3.1.1 binaries.
This release completely supersedes 3.1.
Please contact fosslinux at gophernicus(a)gophernicus.org or on
irc.freenode.net#gophernicus if you encounter any further issues.
There is currently a warning when gophernicus is built without libwrap
support on some system configurations. This warning is harmless.
- fosslinux and the Gophernicus developers
Hi all,
I am very happy to release Gophernicus version 3.1. A large number of
changes have been made since the last release, including:
* OpenBSD pledge and unveil support.
* A new filetypes system.
* -nH to disable HTTP responses.
* A new build system.
* A manual page.
* An official Debian package coming in the next stable release of Debian!
* A wide variety of bug fixes.
Please note that the way in which Gophernicus is built and installed has
changed significantly. It now uses a more traditional `./configure &&
make && make install` setup, with a hand-written configure script, that
attempts to emulate autotools to an extent. Please note that a
`--listener` argument is required. As you may be aware, Gophernicus does
not listen to a port. It requires a tool such as systemd, inetd or
xinetd to work and pass through requests to Gophernicus. In the past,
this was auto-detected in the Makefile, but often poorly and not
portably. The option to autodetect is still there, but you must be
explicit about it, by using `--listener=autodetect`. Otherwise, choose a
listener using the same argument, for example `--listener=systemd`.
For clarity, this is an example install:
```
./configure --listener=xinetd
make
sudo make install
```
The previous build system did not support parallelization, but the new
one does. You can pass `-jx` to make now.
Thanks to the work of @ryanakca, we will now have a Debian package
available just in time for the next stable release of Debian
(hopefully!). If you are a deb package user, note that we have removed
the debian packaging scripts from the repository, to allow downstream to
manage this. You have 3 options.
* wait for the official Debian package to come into your repositories
and apt will handle the rest. You will not need to do anything but will
not have the 3.1 release for a number of months.
* compile and install manually, preferably to /usr/local or /opt as not
to mess with the system package; when the new Debian package comes, you
can easily remove the manual install.
* take the Debian package scripts from the downstream repository and
manually create a package, once these scripts are complete. This
document will be edited when this occurs.
Along with this release we are now distributing binaries. They are:
* An x86_64 glibc binary, linked against glibc 2.30.
* An x86_64 static binary.
* An x86_64 musl-linked binary (1.1 series).
* An AARCH64 glibc binary, linked against glibc 2.30.
* An AARCH64 static binary.
These are available here.
https://github.com/gophernicus/gophernicus/releases/tag/3.1.
I would like to thank all these contributors, especially those who made
quite significant changes, particularly @augfab (proper manual page,
`-nH`) and @vext01 (OpenBSD pledge and unveil support), as well as
@hb9kns (Gophernicus maintainer).
```
72 fosslinux
9 Augustin Fabre
4 Emil Engler
2 Bradley D. Thornton
2 Yargo
2 bdeshi
1 Edd Barrett
1 Ryan Kavanagh
1 cdmnky73
```
Full list of (user-seen) changes (not all commits included):
- Allow document roots specified with relative paths
- Drop debian packaging
- New build system
- Rework logging logic
- Replace spurious tabs in menu with dashes
- Don't install documentation
- Fix parallel builds
- Declare function prototypes explicitly
- Sort the ~ selector by date modified
- Rework manual page
- Propagate FLAGS value to recursive MAKE calls
- Fix memory leak in gophermap parsing
- Add option -nH to disable HTTP response to HTTP GET/POST requests (#66)
- Make description in die() appears everywhere
- fix LDFLAGS
- Filetypes2 (#57) Re-do filetypes system.
- corrected some typos in author's names (#55)
- build: Force create symlink
- ci: New Travis system for linux and macOS builds and installs
- refactor: New hierarchy and refactored Makefile
- use user-defined CC by default
- add -b option to git clone instead of git checkout
- Add OpenBSD pledge(2) and unveil(2) support.
- change default charset to utf-8
- change max-width to 67 (#39)
Please feel free to ask any questions!
-fosslinux and the Gophernicus developers
Hi all!
I have just released the first (and probably final) Release Candidate
for Gophernicus version 3.1. This brings a host of improvements to
gophernicus, notably including:
- OpenBSD pledge and unveil support.
- A new filetypes system.
- `-nH` to disable HTTP responses.
- A new build system.
- A manual page.
- An official Debian package coming in the next stable release for 3.1!
- A wide variety of bug fixes.
I would really appreciate testing, especially of the new build system.
You can get sources and binaries here:
https://github.com/gophernicus/gophernicus/releases/tag/3.1rc1.
Please read INSTALL.md, the process has changed (you now need to run
`./configure` first).
If you are a deb package user, please either:
1. wait for the official Debian package to come into your repositories
and apt will handle the rest.
2. if you want the new releases sooner, please compile and install
manually, preferably to `/usr/local` or `/opt` as not to mess with the
system package. Then, when the new Debian package comes, you can easily
remove the manual install.
Along with this release we are now distributing binaries. There are
currently two binaries, and there will be more added for the final
release. The current two are:
1. An x86_64 glibc binary, linked against glibc 2.30, without libwrap.
2. An x86_64 static binary, which will work on any system, even running
alternative libcs or older versions of glibc, without libwrap.
Full list of changes:
* Allow document roots specified with relative paths
* Drop debian packaging
* New build system
* Rework logging logic
* Replace spurious tabs in menu with dashes
* Don't install documentation
* Fix parallel builds
* Declare function prototypes explicitly
* Sort the ~ selector by date modified
* Rework manual page
* Propagate FLAGS value to recursive MAKE calls
* Fix memory leak in gophermap parsing
* Add option `-nH` to disable HTTP response to HTTP GET/POST requests
(#66)
* Make description in die() appears everywhere
* fix LDFLAGS
* Filetypes2 (#57) Re-do filetypes system.
* corrected some typos in author's names (#55)
* build: Force create symlink
* ci: New Travis system for linux and macOS builds and installs
* refactor: New hierarchy and refactored Makefile
* use user-defined CC by default
* add -b option to git clone instead of git checkout
* Add OpenBSD pledge(2) and unveil(2) support.
* change default charset to utf-8
* change max-width to 67 (#39)
