a628d56e25
+ Leveraging serde_json to use a config.json This lets us use the same config for both the json-api and the rtc-server without adding dependancies
32 lines
1.1 KiB
Bash
32 lines
1.1 KiB
Bash
# Example .env file
|
|
# In theory this file can be used for _both_ the rtc-server and the json-api server
|
|
|
|
# This field is required by the json-api binary to actually find the database
|
|
DATABASE_URL=mysql://freechat_dev:password@localhost:3306/freechat
|
|
# The fields below are unused but are here in case you're confused as to the
|
|
# structure of the url above
|
|
# It is perfectly safe to delete these
|
|
DATABASE_NAME=freechat
|
|
DATABASE_PASS=password
|
|
DATABASE_USER=freechat_dev
|
|
DATABASE_HOST=localhost
|
|
DATABASE_PORT=3306
|
|
|
|
# Note that these should literally never point to the same file
|
|
# that completely breaks the web socket's permissions+authentication model
|
|
HMAC_PATH=hmac.secret
|
|
WSS_HMAC_PATH=wss-hmac.secret
|
|
|
|
|
|
# Public name that your server has
|
|
SERVER_NAME="Freechat Dev Server"
|
|
# Public description of what youre server is about
|
|
SERVER_DESCRIPTION="Server for sick development things"
|
|
|
|
# These are the actual url's which are sent to/used by clients to communicate with
|
|
# your instance. If you have a reverse proxy setup then you can configure it so that
|
|
# the port numbers are not in the URL(suggested)
|
|
PUBLIC_URL=http://localhost:4536
|
|
PUBLIC_WS_URL=ws://localhost:5648
|
|
|