loop/srv
1
0
Fork 0
Code Issues Pull requests Activity

Makes small adjustments et cetera.

Browse source
This commit is contained in:
Circling Skies 2024-12-17 15:09:07 -03:00
parent 63d78f0e56
commit de6c586755
1 changed files with 6 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
README
View file

@ -6,20 +6,12 @@ LOOP is an NNTP server written in Common Lisp.
We assume We assume
- you run SBCL - you run SBCL, Quicklisp and git installed
- you have Quicklisp installed and knows how to use it
- you know how to use a TCP server such as - you know how to use a TCP server such as
https://cr.yp.to/ucspi-tcp.html https://cr.yp.to/ucspi-tcp.html
- you know how to manage a daemon witha package such as
- you know how to manage a daemon with
https://cr.yp.to/daemontools.html https://cr.yp.to/daemontools.html
- you have git and knows how to use it
(*) How to install it (*) How to install it
LOOP is not in the Quicklisp repository, so we'll instruct you to LOOP is not in the Quicklisp repository, so we'll instruct you to
@ -34,9 +26,6 @@ and say
$ echo /path/to/loop/home > conf-home $ echo /path/to/loop/home > conf-home
$ make install $ make install
If you just installed SBCL and quicklisp, the build might take a
little while due to downloading dependencies. Be patient.
(*) Systems with no installation issues (*) Systems with no installation issues
We installed LOOP just fine on We installed LOOP just fine on
@ -123,8 +112,8 @@ It's easy and fun.
(*) LOOP's REPL (*) LOOP's REPL
LOOP is totally hackable. Even if you're remotely connected, you can LOOP is hackable. If you're remotely connected, you can get total
have total control over the loop process with the repl command: control over the loop process using the repl command.
$ telnet example.com 119 $ telnet example.com 119
Trying example.com... Trying example.com...
@ -137,16 +126,14 @@ repl
LOOP> *client* LOOP> *client*
#S(CLIENT :GROUP NIL :ARTICLE 1 :USERNAME YOU :AUTH? YES) #S(CLIENT :GROUP NIL :ARTICLE 1 :USERNAME YOU :AUTH? YES)
LOOP> (list-groups) LOOP> (list-groups)
(comp.editors.emacs comp.lisp comp.programming comp.unix (local.control.news local.test)
humanities.poetry local.control.news local.havoc local.system.reports
local.test local.users.evalu math.calculus math.havoc)
LOOP> quit LOOP> quit
200 Okay, no more REPL hacking. 200 Okay, no more REPL hacking.
(*) Cron jobs (*) Cron jobs
If you'd like to remove inactive accounts, we wrote If you'd like to remove inactive accounts, we wrote
scripts/cron-remove-inactive-users.lisp. Her's our crontab: scripts/cron-remove-inactive-users.lisp. Here's our crontab:
$ crontab -l $ crontab -l
@daily cd /path/to/loop/home && sbcl --script scripts/cron-remove-inactive-users.lisp @daily cd /path/to/loop/home && sbcl --script scripts/cron-remove-inactive-users.lisp