You have a shell. You run the bot.
SSH in, build or unpack Eggdrop, point it at a vhost, detach screen. You keep the config, the scripts, the blame. We keep the machine and the flood filter.
$./eggdrop
The bot should outlive the laptop.
This is most of the business. Channel owners who are tired of the bot vanishing every time the cable modem sneezes. Operators who already know how to compile Eggdrop and just want a box that does not fall over.
Eggdrop is the IRC bot that has been sitting in channels since before some of you had a distro. Tcl, partyline, userfile, the whole archaeology. It holds ops, runs scripts, and does not care that you went to lunch.
Two ways to run one here:
No setup. No Tcl. No “wait, which .conf?”
If you just want a bot in the channel and you do not want to learn Eggdrop, that is a different product. It lives at eggdrops.net. We put it in the channel. You remote-control it. Linux experience: optional.
$./self-managed
Not a timeline. The actual order of operations.
-
01
Get a shell. SSH in. You should see a prompt, not a marketing page.
- 02
-
03
Build or unpack Eggdrop. Bind it to the address you were given. Set ident. Do not skip ident.
-
04
Put it in
screenortmux. Detach. Close the laptop. Confirm it is still in the channel. -
05
If the hostname is still a raw IP, wait for PTR. It is DNS, not a vibe. FAQ has the impatient version.
$man eggdrop
For the one friend who got dragged here and is nodding politely.
You run an IRC channel. You need something that stays opped when everyone else is asleep, netsplit, or “just restarting mIRC.” That something is usually Eggdrop. It is a daemon. It speaks IRC. It runs scripts. It is not a SaaS.
If that already made sense, order a shell. If it did not, start at eggdrops.net and skip the compiler.