https://github.com/neutonfoo/cocos-concierge-old
https://github.com/neutonfoo/cocos-concierge-old
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/neutonfoo/cocos-concierge-old
- Owner: neutonfoo
- Created: 2023-03-23T14:16:58.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2024-04-03T03:42:29.000Z (about 2 years ago)
- Last Synced: 2025-01-29T15:24:51.644Z (over 1 year ago)
- Language: Shell
- Size: 43.9 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Coco's Concierge
Coco's Concierge contains two microservices, the reverse-proxy and updater.
This reverse proxy service is used to route all traffic on port 80 to the appropriate microservice. It opens port 80 to the internet and is the only publicly accessible port on the Droplet. The nginx-conf-generator.sh script generates an nginx.conf file based on the projects.json file, and this file is copied into the nginx container.
The updater service is used to manage microservice deployment (with the exception of the reverse-proxy and itself/updater).
## projects.json
There are two types of microservices that can be listed in the projects.json directory: services and daemons.
Allow for direct incoming traffic on port 80 (has to be port 80). Whereas daemons do not allow for incoming traffic and will not be included in the nginx.conf routing.
## updater
The updater microservice is a Flask application that manages the deployment of microservices within the Droplet (wth the exception of reverse-proxy and itself).
> The deployment of reverse-proxy and updater are managed entirely through GitHub Actions in this repository.
## Deploying to Coco's House
1. All services share a bridge network `cocos-network`. This allows the reverse proxy to route the connection to the correct microservice.