Permalink
Browse files

Basic notes about generating a production release

  • Loading branch information...
oestrich committed Sep 24, 2018
1 parent fb67ccc commit 6da761189c2aa7098ce5502bb3cbca4614eb2670
Showing with 43 additions and 0 deletions.
  1. +43 −0 docs/deploy.md
View
@@ -1,5 +1,48 @@
## Deployment
### Configuration
Before you generate a production release, you need to set up your `config/prod.secret.exs` file
```elixir
use Mix.Config
config :ex_venture, Data.Repo,
adapter: Ecto.Adapters.Postgres,
database: "fill me in",
hostname: "fill me in",
port: "5432",
ssl: true,
username: "fill me in",
password: "fill me in",
pool_size: 20
config :gossip, :client_id, "fill me in"
config :gossip, :client_secret, "fill me in"
config :pid_file, file: "/home/user/ex_venture.pid"
```
Other configuration you may want to include in this file is cluster configuration (if you're clustering) and Sentry configuration to get error reporting.
You also need several environment variables to be present when the server is running. A simple way of doing this is adding the following to `/etc/profile.d/game.sh`, so they are sourced when logging in.
```bash
export HOST="fill me in"
export HTTP_PORT="443"
export HTTP_SCHEME="https"
export SMTP_SERVER="fill me in"
export SMTP_PORT="fill me in"
export SMTP_USERNAME="fill me in"
export SMTP_PASSWORD="fill me in"
export EXVENTURE_MAILER_FROM="fill me in"
```
### Generating a release
Distillery is used to generate releases. Once a release is generated you can copy the tar file to the server and start it up.
```bash

0 comments on commit 6da7611

Please sign in to comment.