||2 years ago|
|.vscode||2 years ago|
|app||2 years ago|
|client||2 years ago|
|config||2 years ago|
|docs||2 years ago|
|lib||2 years ago|
|ssl||2 years ago|
|supervisord||2 years ago|
|.env.default||2 years ago|
|.gitignore||2 years ago|
|.jshintrc||2 years ago|
|LICENSE||2 years ago|
|NOTES.md||2 years ago|
|README.md||2 years ago|
|deploy||2 years ago|
|dtp-webapp-cli.js||2 years ago|
|dtp-webapp.js||2 years ago|
|gulpfile.js||2 years ago|
|ncd-live-volcano.code-workspace||2 years ago|
|package.json||2 years ago|
|push||2 years ago|
|release||2 years ago|
|start-local||2 years ago|
|start-production||2 years ago|
|stop-production||2 years ago|
|update-deps.js||2 years ago|
|yarn.lock||2 years ago|
NCD Live (In a Volcano)
A bigoted online card gaming experience.
The only qualified operated system for hosting a Live (In a Volcano) is Ubuntu 20.04 LTS. It is acceptable to run it in a virtual machine for development and testing, but it should be run as close to bare metal as can be had for production environments.
You will need MongoDB and MinIO installed and running before you can start Live (In a Volcano) web services.
sudo apt-get install redis
On a new host or host image, copy
.env and edit it as necessary.
For password salt and service passwords, the
uuidgen tool may be useful to help generate hard-to-guess passwords for use in a development environment. Something more sophisticated than a UUID should be used in production.
Install application dependencies by running Yarn. You should do this on initial install and after every update or
git pull as dependencies do change often, become upgraded to new versions, receive security fixes, etc.
Starting In Development Mode
- Make sure
NODE_ENVis set to
./sites-start-localin a VS Code terminal, then rename that terminal to
- In a new VS Code terminal, run
gulpand rename that terminal
- Open https://localhost:3000 in your web browser.
You can now make changes to program source code, and the environment will automatically respond, build, pack, and re-load things as needed depending on what you did and what's open/running.
Live (In a Volcano) is a multi-tier web hosting engine built on:
Production Environment Information
It's impossible to give 100% generic advice here, but it all depends on how large your audience is and how much they use your website. Larger, more active audiences will require a different kind of production server deployment than smaller and less active audiences.
Generally, it's possible to stack all components on one host and operate a fast site for small-to-medium audiences. The size of the host may vary, but it's possible to keep the system stacked and handle quite a large audience.
Beyond a point, you'll need to start isolating services away from each other. Storage will want it's own system(s), MongoDB will want it's own systems (plural), Redis will want it's own system(s), and the Node.js components can each start to want their own system(s).
Once you start scaling horizontally, the host requirements change a little. You will need two networks and network interfaces per host. The production network to handle public requests; and a management network for handling IPC and data-sharing among the hosts themselves.
Some useful links for learning more about hosting MinIO:
Redis simply has many different documents to describe it's many different features and their requirements. I'd like to give you a summary page link, but it doesn't exist. This is that summary page. These are those links.
Live (In a Volcano) Copyright (C) 2022 Pixie All Rights Reserved