tfurrows
|
|
On gopher cgi and quotas
|
Jan 20 00:35 UTC 2018 |
A few quick questions about gopher on grex.
First, do we have any kind of CGI available? If so, what languages can we use?
Second, how hard and fast are our quotas here on grex? I want to have a Gopher
version of the public domain Websters 1928 dictionary available through
gopher. I have the dictionary in a database, with permission from the creator
of the database to use it. As a database, it's a single file at about 16MB,
which isn't a problem; with some kind of cgi access that is. I also have the
contents of that DB broken out into text files in folders, for easy gopher
browser... but that equals about 62k files (broken into A-Z folders, and then
folders with the first two letters of the word under that.) Depending on how
much disk space a folder takes on grex, that might break the quota bank; and
the quota command shows a folder limit as well, which would be 6x broken.
Another option would be to drop it all in my SDF gopherhole, but the SDF
gopher server has been quite unreliable lately, so I hesitate to keep putting
content there.
Any thoughts?
|
cross
|
|
response 1 of 10:
|
Jan 24 02:04 UTC 2018 |
CGI, no; the gopher server runs as a single, global user. There's no good
way to get it to run a program as a particular user account, so any gopher
CGI could, by definition, muck with any other gopher CGI.
I'm still baffled by all this fascination with Gopher with HTTP is manifestly
better at this point, but if folks are having fun with it, then go for it.
Re: quotas, we've got hard and fast quotas and I think they stretch up to
something like 100MB. If you need more for some reason, let me/us know and
we can plus you up.
|