Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create multi-tier docker compose #4

Merged
merged 1 commit into from
Mar 1, 2020

Conversation

shankari
Copy link
Contributor

@shankari shankari commented Jan 28, 2020

with a built-in crontab

@xubowenhaoren this is the multi-tier setup with the cronjob. I have added a short README.
Please let me know if it works for you, or whether there is anything that needs to be improved before I merge to master.

This fixes e-mission/e-mission-docs#493

with a built-in crontab
@shankari
Copy link
Contributor Author

@xubowenhaoren can you confirm that this works for you? If so, I can merge it.

@xubowenhaoren
Copy link

I confirm that I can successfully create and run the docker after changing the ports in the docker-compose.yml. However, I would love to see a more developed README on this new branch. Now I am tweaking the config files and will be able to contribute by adding some examples to README.

@shankari
Copy link
Contributor Author

shankari commented Mar 1, 2020

@xubowenhaoren please do. Documentation PRs are always welcome.

@shankari shankari merged commit 1cb7bdc into e-mission:master Mar 1, 2020
@shankari shankari deleted the multi-tier-example branch March 29, 2020 04:42
shankari added a commit to shankari/e-mission-docker that referenced this pull request Jun 4, 2020
One line fix.
This fixes e-mission/e-mission-docs#543

This has also been pushed to dockerhub as version 2.8.2
https://hub.docker.com/layers/emission/e-mission-server.dev.server-only/2.8.2/images/sha256-1f5ef249e90fbb5b1a5dbfdb0e12ee7b5e8f2bf9d837d1c3e70d63c58373ca30?context=repo

```
C02KT61MFFT0:em-server shankari$ docker-compose -f docker-compose.dev.yml up
WARNING: Some services (db, web-server) use the 'deploy' key, which will be ignored. Compose does not support 'deploy' configuration - use `docker stack deploy` to deploy to a swarm.
WARNING: The Docker Engine you're using is running in swarm mode.

Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

To deploy your application across the swarm, use `docker stack deploy`.

Creating em-server_db_1 ... done
Creating em-server_web-server_1 ... done
Attaching to em-server_db_1, em-server_web-server_1
web-server_1  | Cloning from repo https://github.com/e-mission/e-mission-server.git and branch master
db_1          | 2020-06-04T05:47:50.254+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=5bb3a71c1d34
db_1          | 2020-06-04T05:47:50.256+0000 I CONTROL  [initandlisten] db version v3.4.19
db_1          | 2020-06-04T05:47:50.257+0000 I CONTROL  [initandlisten] git version: a2d97db8fe449d15eb8e275bbf318491781472bf
...
web-server_1  | Installing manually downloaded packages
web-server_1  | Downloading and Extracting Packages
web-server_1  | Preparing transaction: ...working... done
web-server_1  | Verifying transaction: ...working... done
web-server_1  | Executing transaction: ...working... done
web-server_1  |
web-server_1  | Updating using conda now
web-server_1  | Solving environment: ...working... done
web-server_1  |
...
web-server_1  | /src/e-mission-server
web-server_1  | db
web-server_1  | {
web-server_1  |     "timeseries": {
web-server_1  |         "url": "db"
web-server_1  |     }
web-server_1  | }
web-server_1  | 0.0.0.0
web-server_1  | {
web-server_1  |   "paths" : {
web-server_1  |     "static_path" : "webapp/www/",
web-server_1  |     "python_path" : "main",
web-server_1  |     "log_base_dir" : ".",
web-server_1  |     "log_file" : "debug.log"
web-server_1  |   },
web-server_1  |   "__comment" : "Fill this in for the production server. port will almost certainly be 80 or 443. For iOS, using 0.0.0.0 allows you to test without an internet connection. For AWS and android, make sure that the host 0.0.0.0, localhost does not seem to work",
web-server_1  |   "server" : {
web-server_1  |     "host" : "0.0.0.0",
web-server_1  |     "port" : "8080",
web-server_1  |     "__comment": "1 hour = 60 min = 60 * 60 sec",
web-server_1  |     "timeout" : "3600",
web-server_1  |     "auth": "skip"
web-server_1  |   }
web-server_1  | }
web-server_1  | Enabling bottle live reload
web-server_1  | Replacing run.host=server_host -> run(reloader=True,host=server_host
db_1          | 2020-06-04T06:00:16.996+0000 I NETWORK  [thread1] connection accepted from 172.19.0.3:44572 e-mission#1 (1 connection now open)
db_1          | 2020-06-04T06:00:17.049+0000 I NETWORK  [conn1] received client metadata from 172.19.0.3:44572 conn1: { driver: { name: "PyMongo", version: "3.5.1" }, os: { type: "Linux", name: "Linux", architecture: "x86_64", version: "4.19.76-linuxkit" }, platform: "CPython 3.6.1.final.0" }
db_1          | 2020-06-04T06:00:18.188+0000 I NETWORK  [thread1] connection accepted from 172.19.0.3:44574 e-mission#2 (2 connections now open)
db_1          | 2020-06-04T06:00:18.189+0000 I NETWORK  [conn2] received client metadata from 172.19.0.3:44574 conn2: { driver: { name: "PyMongo", version: "3.5.1" }, os: { type: "Linux", name: "Linux", architecture: "x86_64", version: "4.19.76-linuxkit" }, platform: "CPython 3.6.1.final.0" }
web-server_1  | ERROR:root:habitica not configured, game functions not supported
web-server_1  | Traceback (most recent call last):
web-server_1  |   File "/src/e-mission-server/emission/net/ext_service/habitica/proxy.py", line 22, in <module>
web-server_1  |     key_file = open('conf/net/ext_service/habitica.json')
web-server_1  | FileNotFoundError: [Errno 2] No such file or directory: 'conf/net/ext_service/habitica.json'
db_1          | 2020-06-04T06:00:19.162+0000 I NETWORK  [thread1] connection accepted from 172.19.0.3:44576 e-mission#3 (3 connections now open)
db_1          | 2020-06-04T06:00:19.168+0000 I NETWORK  [conn3] received client metadata from 172.19.0.3:44576 conn3: { driver: { name: "PyMongo", version: "3.5.1" }, os: { type: "Linux", name: "Linux", architecture: "x86_64", version: "4.19.76-linuxkit" }, platform: "CPython 3.6.1.final.0" }
db_1          | 2020-06-04T06:00:19.708+0000 I NETWORK  [thread1] connection accepted from 172.19.0.3:44578 e-mission#4 (4 connections now open)
db_1          | 2020-06-04T06:00:19.710+0000 I NETWORK  [conn4] received client metadata from 172.19.0.3:44578 conn4: { driver: { name: "PyMongo", version: "3.5.1" }, os: { type: "Linux", name: "Linux", architecture: "x86_64", version: "4.19.76-linuxkit" }, platform: "CPython 3.6.1.final.0" }
web-server_1  | ERROR:root:habitica not configured, game functions not supported
web-server_1  | Traceback (most recent call last):
web-server_1  |   File "/src/e-mission-server/emission/net/ext_service/habitica/proxy.py", line 22, in <module>
web-server_1  |     key_file = open('conf/net/ext_service/habitica.json')
web-server_1  | FileNotFoundError: [Errno 2] No such file or directory: 'conf/net/ext_service/habitica.json'
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants