e6b6ab2b11
The variables were often referenced with a trailing slash, and having `//` works, but is sloppy. |
||
---|---|---|
cmd/oragono-web | ||
docs | ||
irc | ||
mkcerts | ||
vendor@1259bb541b | ||
web | ||
.gitignore | ||
.gitmodules | ||
CHANGELOG.md | ||
DEVELOPING.md | ||
Gopkg.lock | ||
Gopkg.toml | ||
LICENSE | ||
Makefile | ||
oragono-web.yaml | ||
oragono.go | ||
oragono.motd | ||
oragono.yaml | ||
README.md |
Oragono is a modern, experimental IRC server written in Go. It’s designed to be simple to setup and use, and it includes features such as UTF-8 nicks / channel names, client accounts with SASL, and other assorted IRCv3 support.
Oragono is a fork of the Ergonomadic IRC daemon <3
This project adheres to Semantic Versioning. For the purposes of versioning, we consider the “public API” to refer to the configuration files, CLI interface and database format.
Oragono
Features
- UTF-8 nick and channel names with rfc7613
- yaml configuration
- native TLS/SSL support
- server password (
PASS
command) - an extensible privilege system for IRC operators
- ident lookups for usernames
- automated client connection limits
- on-the-fly updating server config and TLS certificates (rehashing)
- client accounts and SASL
- passwords stored with bcrypt (client account passwords also salted)
- banning ips/nets and masks with
KLINE
andDLINE
- IRCv3 support
- a heavy focus on developing with specifications
- integrated (alpha) REST API and web interface
Installation
To go through the standard installation, download the latest release from this page: https://github.com/oragono/oragono/releases/latest
Extract it into a folder, then run the following commands:
cp oragono.yaml ircd.yaml
vim ircd.yaml # modify the config file to your liking
oragono initdb
oragono mkcerts
Note: This installation will give you unsigned certificates suitable for testing purposes. For real certs, look into Let’s Encrypt!
Platform Packages
Some platforms/distros also have Oragono packages maintained for them:
- Arch Linux AUR - Maintained by Sean Enck (@enckse).
From Source
You can also install this repo and use that instead! However, keep some things in mind if you go that way:
devel
branches are intentionally unstable, containing
fixes that may not work, and they may be rebased or reworked
extensively.
The master
branch should usually be stable, but
may contain database changes that either have not been finalised or not
had database upgrade code written yet. Don’t run master
on
a live production network.
The stable
branch contains the latest release. You can
run this for a production version without any trouble.
Building
Clone the appropriate branch. From the root folder, run
make
to generate all release files for all of our target
OSes:
make
You can also only build the release files for a specific system:
# for windows
make windows
# for linux
make linux
# for osx
make osx
# for arm6
make arm6
Once you have made the release files, you can find them in the
build
directory. Uncompress these to an empty directory and
continue as usual.
Configuration
The default config file oragono.yaml
helps walk you through
what each option means and changes. The configuration’s intended to be
sparse, so if there are options missing it’s either because that feature
isn’t written/configurable yet or because we don’t think it should be
configurable.
You can use the --conf
parameter when launching Oragono
to control where it looks for the config file. For instance:
oragono run --conf /path/to/ircd.yaml
. The configuration
file also stores where the log, database, certificate, and other files
are opened. Normally, all these files use relative paths, but you can
change them to be absolute (such as /var/log/ircd.log
) when
running Oragono as a service.
Logs
By default, logs are stored in the file ircd.log
. The
configuration format of logs is designed to be easily pluggable, and is
inspired by the logging config provided by InspIRCd.
Passwords
Passwords (for both PASS
and oper logins) are stored
using bcrypt. To generate encrypted strings for use in the config, use
the genpasswd
subcommand as such:
oragono genpasswd
With this, you receive a blob of text which you can plug into your configuration file.
Running
After this, running the server is easy! Simply run the below command and you should see the relevant startup information pop up.
oragono run
How to register a channel
- Register your account with
/quote ACC REGISTER <username> * passphrase :<password>
- Join the channel with
/join #channel
- Register the channel with
/msg ChanServ REGISTER #channel
After this, your channel will remember the fact that you’re the owner, the topic, and any modes set on it!
Make sure to setup SASL in your client to automatically login to your account when you next join the server.
Credits
- Jeremy Latt, creator of Ergonomadic, https://github.com/jlatt
- Edmund Huber, maintainer of Ergonomadic, https://github.com/edmund-huber
- Niels Freier, added WebSocket support to Ergonomadic, https://github.com/stumpyfr
- Daniel Oakley, maintainer of Oragono, https://github.com/DanielOaks
- apologies to anyone I forgot.