3
0
mirror of https://github.com/ergochat/ergo.git synced 2024-11-10 22:19:31 +01:00
Go to file
Sean Enck 242dbfd72c
how do you do let's encrypt? let's move this from an issue to the FAQ,
this probably takes care of #118 and #231 well enough to at least
resolve them and start using the md/docs
2018-04-10 21:26:44 -04:00
docs how do you do let's encrypt? let's move this from an issue to the FAQ, 2018-04-10 21:26:44 -04:00
irc Back to -unreleased 2018-04-11 10:12:11 +10:00
languages languages: Mark Turkish as incomplete, since we updated strings 2018-04-09 23:45:41 +10:00
vendor@f606564da4 vendor: Updated submodules 2018-02-11 09:16:04 +10:00
.gitignore Start making builds with goreleaser 2018-01-07 12:40:26 +10:00
.gitmodules vendor: Updated packages 2017-06-14 12:12:17 -06:00
.goreleaser.yml Expose current git commit 2018-04-09 10:08:54 +10:00
.travis.yml try to fix travis by pinning a goreleaser release 2018-03-16 13:16:23 -04:00
CHANGELOG.md Back to -unreleased 2018-04-11 10:12:11 +10:00
DEVELOPING.md refactor account registration, add nick enforcement 2018-02-11 05:30:40 -05:00
Gopkg.lock vendor: Updated submodules 2018-02-11 09:16:04 +10:00
Gopkg.toml vendor: Updated submodules 2017-04-30 13:09:36 +10:00
LICENSE Update license 2018-04-09 23:26:34 +10:00
Makefile makefile: Add an explicit buildrelease case 2018-04-11 10:12:28 +10:00
oragono.go when entering/generating the password it's helpful to at least be asked to confirm the input so if you get something like an extraneous character, on confirmation, you could catch that 2018-04-10 13:21:51 -04:00
oragono.motd Add colour charts to the default MOTD, including 16-98 extended colours 2018-04-01 00:35:41 +10:00
oragono.yaml Enable languages and motd formatting by default 2018-04-11 09:26:42 +10:00
README Start making builds with goreleaser 2018-01-07 12:40:26 +10:00
README.md readme: Update ns reg instructions 2018-04-01 12:04:44 +10:00
updatetranslations.py Fix translation script for weird OS encodings 2018-04-01 18:31:45 +10:00

Oragono logo

Oragono is a modern, experimental IRC server written in Go. Its 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


Go Report Card Build Status Download Latest Release Freenode #oragono Crowdin

darwin.network and testnet.oragono.io are running Oragono in production if you want to take a look.


Features

  • UTF-8 nick and channel names with rfc7613 (PRECIS)
  • 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 and DLINE
  • supports multiple languages (you can also set a default language for your network)
  • IRCv3 support
  • a heavy focus on developing with specifications

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 self-signed certificates suitable for testing purposes. For real certs, look into Lets Encrypt!

Platform Packages

Some platforms/distros also have Oragono packages maintained for them:

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. Dont 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

Build Status

Clone the appropriate branch. If necessary, do git submodule update --init to set up vendored dependencies. 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 configurations intended to be sparse, so if there are options missing its either because that feature isnt written/configurable yet or because we dont 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

  1. Register your account with /NS REGISTER <username> [<password>]
  2. Join the channel with /join #channel
  3. Register the channel with /CS REGISTER #channel

After this, your channel will remember the fact that youre 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