sebboh
/
tilde.club
forked from team/tilde.club
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Sorry! `` looks awful in GitHub headers. Removed.

This commit is contained in:
reppep 2014-10-08 23:21:33 -04:00
parent aaeef92564
commit 1c4789dba9
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ircserver.md
View File

@ -1,4 +1,4 @@
# Setting up the `tilde.club` IRC server # Setting up the tilde.club IRC server
We chose to go with `charybdis`, mostly because it's in the Debian/Ubuntu package repository (universe), so we can update it without having to go through the `configure`/`make`/`make install` process. We chose to go with `charybdis`, mostly because it's in the Debian/Ubuntu package repository (universe), so we can update it without having to go through the `configure`/`make`/`make install` process.
@ -10,14 +10,14 @@ The IRC server is an Amazon EC2 instance running Ubuntu. Initial system setup on
* updating the `/etc/hosts` file (add `172.30.0.216 irc.tilde.club irc` and `172.30.0.176 tilde.club tilde`) * updating the `/etc/hosts` file (add `172.30.0.216 irc.tilde.club irc` and `172.30.0.176 tilde.club tilde`)
* setting the EC2 security group to allow TCP traffic on port 6667 from the `tilde.club` shell server only * setting the EC2 security group to allow TCP traffic on port 6667 from the `tilde.club` shell server only
### Setup changes on the `tilde.club` shell server to access the IRC server ### Setup changes on the tilde.club shell server to access the IRC server
The `tilde.club` shell server needed a few tweaks as well: The `tilde.club` shell server needed a few tweaks as well:
* updating `/etc/hosts` (add `172.30.0.216 irc.tilde.club irc` so users can reach the IRC server by hostname) * updating `/etc/hosts` (add `172.30.0.216 irc.tilde.club irc` so users can reach the IRC server by hostname)
* setting the EC2 security group to allow TCP traffic on port 113 (`identd`) from the IRC server only * setting the EC2 security group to allow TCP traffic on port 113 (`identd`) from the IRC server only
## Installing `charybdis` ## Installing charybdis
First we needed to add the "universe" repository to the `apt` repository list: First we needed to add the "universe" repository to the `apt` repository list:

4
docs/shellserver.md
View File

@ -1,4 +1,4 @@
# Setting up the `tilde.club` shell server (user host) # Setting up the tilde.club shell server (user host)
We want to document the ins and outs of setting up the server so others who are interested can learn (and help!). We want to document the ins and outs of setting up the server so others who are interested can learn (and help!).
@ -13,7 +13,7 @@ The default MTA on CentOS is `postfix`. Our goal was to have a `localhost`-only
* the `inet_interfaces` value should just be `localhost` (`inet_interfaces = localhost`) * the `inet_interfaces` value should just be `localhost` (`inet_interfaces = localhost`)
* the `default_transport` parameter should be the bounce message we want (so add `default_transport = error: outside mail is not deliverable` to the bottom of the file) * the `default_transport` parameter should be the bounce message we want (so add `default_transport = error: outside mail is not deliverable` to the bottom of the file)
## `identd` ## identd
Users will connect from their shell account to an IRC server, so it is *very* handy to have an `identd` server. For us that just meant installing the standard CentOS `identd` server and configuring it to start automatically: Users will connect from their shell account to an IRC server, so it is *very* handy to have an `identd` server. For us that just meant installing the standard CentOS `identd` server and configuring it to start automatically: