# Reliable Web Deploy
Note: You need to run both the database container (reliable-mysql) and the app (reliable-web) container for reliable to work.
# Using docker-compose (opens new window) (recommended)
# production
# start services
$ docker-compose -p reliable -f docker-compose.yml up -d
# NOTE: if you meet the problem, maybe the issue caused by the existed service, just run the stop command below.
# stop services
$ docker-compose -p reliable -f docker-compose.yml down
Execute docker ps, we can see:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7c641bdb57c6 macacajs/reliable-web:v2 "./entrypoint.sh npm…" 6 seconds ago Up 5 seconds (health: starting) 0.0.0.0:9900->9900/tcp reliable_web_1
f589b1c9046f macacajs/reliable-mysql "docker-entrypoint.s…" 6 minutes ago Up 6 seconds 0.0.0.0:3306->3306/tcp, 33060/tcp reliable_mysql_1
During the first deployment, seed the database before accessing the web portal. Otherwise 500 will be thrown:
$ NODE_ENV=production npm run db:seed:all
To go into the MySQL:
$ docker exec -it reliable_mysql_1 mysql -uroot -preliable
mysql> use reliable;
mysql> show tables;
mysql> select * from reliable.jobNames;
# development
# start services
$ docker-compose up
# stop services
$ docker-compose down
Reliable server is running on http://127.0.0.1:9900 by default.
Edit docker-compose.yml (opens new window) to fit your need.