This is still a work in progress but loosely the sequence of steps you will need to take to setup a Teiserver is:
You will need to install:
Make sure that Elixir is in correct version (currently using 1.16). You can find required version here.
You can use asdf to install correct version, picked up from the file .tool-version
.
git clone [email protected]:beyond-all-reason/teiserver.git
cd teiserver
sudo apt update
sudo apt install build-essential libssl-dev
mix deps.get
mix deps.compile
If you want to change the username or password then you will need to update the relevant files in config.
sudo su postgres
psql postgres postgres <<EOF
CREATE USER teiserver_dev WITH PASSWORD '123456789';
ALTER USER teiserver_dev WITH SUPERUSER;
CREATE USER teiserver_test WITH PASSWORD '123456789';
ALTER USER teiserver_test WITH SUPERUSER;
EOF
exit
# You should now be back in the teiserver folder as yourself
# this next command will create the required database.
# Set the MIX_ENV environment variable to perform tasks in a different mix
# environment (e.g. `MIX_ENV=test`).
mix ecto.create
# This next command will run all pending db migrations.
mix ecto.migrate
To run the TLS server locally you will also need to create localhost certificates in priv/certs
using the following commands
mkdir -p priv/certs
cd priv/certs
openssl dhparam -out dh-params.pem 2048
openssl req -x509 -out localhost.crt -keyout localhost.key \
-newkey rsa:2048 -nodes -sha256 \
-subj '/CN=localhost' -extensions EXT -config <( \
printf "[dn]\nCN=localhost\n[req]\ndistinguished_name = dn\n[EXT]\nsubjectAltName=DNS:localhost\nkeyUsage=digitalSignature\nextendedKeyUsage=serverAuth")
cd ../..
We use sass for our css generation and you'll need to run this to get it started.
mix sass.install
Standard mode
mix phx.server
Interactive REPL mode
iex -S mix phx.server
If all goes to plan you should be able to access your site locally at http://localhost:4000/.
The site makes liberal use of FontAwesome so if you are using the site you'll need to download the free version and do the following
fontawesome/css/all.css -> priv/static/css/fontawesome.css
fontawesome/webfonts -> priv/static/webfonts
If you want to use the blog you will also need to place ace.js folder in the same place.
Most of the configuration takes place in config/config.exs with the other config files overriding for specific environments. The first block of config.exs
contains a bunch of keys and values, which you can update.
telnet localhost 8200
openssl s_client -connect localhost:8201
If you want to do things like have a discord bot in development you don't want these details going into git. It is advisable to create a file config/dev.secret.exs
where you can put these config details. I would suggest a file like so:
import Config
config :teiserver, Teiserver,
enable_discord_bridge: true
config :teiserver, DiscordBridgeBot,
token: "------",
bot_name: "Teiserver Bridge DEV",
bridges: [
{"---", "main"},
{"---", "promote"},
{"---", "moderation-reports"},
{"---", "moderation-actions"}
]
# Comment the below block to enable background jobs to take place locally
config :teiserver, Oban,
queues: false,
crontab: false
Running this:
mix teiserver.fakedata
Will generate a large amount of fake data and setup a root account for you. The account will have full access to everything and the database will be populated with false data as if generated over a period of time to make development and testing easier.
When running locally it's likely you won't want to connect the server to an email account, as such password resets need to be done a little differently.
Run your server with iex -S mix phx.server
and then once it has started up use the following code to update your password.
user = Teiserver.Repo.get_by(Teiserver.Account.User, email: "root@localhost")
Teiserver.Account.update_user(user, %{"password" => "password"})
The main dependencies of the project are:
- Phoenix framework, a web framework with a role similar to Django or Rails.
- Ecto, database ORM
- Ranch, a tcp server
- Oban, a backend job processing framework.
In we've started requiring compliance with mix format
- this meant we had to use that on the entire codebase.
This obviously breaks git blame
, but you can sidestep that by using
git config blame.ignoreRevsFile .git-blame-ignore-revs
The attached .git-blame-ignore-revs
file contains a list of commit hashes which modify a large number of lines with trivial changes.
See this blog post by Stefan Judis for reference.
If you want to develop features that interact with the lobby, then you will need to set up SPADS.