- Desktop Application - This where you will enter data. You will be able to add new episodes, blog posts, or modify site data (text, images, etc.). This will include all necessary data for generating your website, and can be used as a backup for the site itself along with having an option to export the data for separate backup as well. This same data could then be imported into the application (for example, if you move to a new computer).
- Static site - This is a static site which is generated completely from the data entered in the desktop application. This will be the main show site. As a static site (meaning, unchanging files served as-is without having to generate dynamic files based on data from a database like WordPress), it will be able to be served extremely cheaply through a CDN. Since the entire site will be on a CDN, it will be able to handle an unlimited amount of traffic and never risk going down. It will also include a page where users can log in to post links. Eve
| import Dexie from 'dexie'; | |
| import * as uuid from 'uuid'; | |
| const { TableNames } = Constants; | |
| class DBTable { | |
| _name = ''; | |
| _db = null; | |
| _table = null; |
| server { | |
| # Port 80 is the default port for accepting HTTP connections | |
| listen 80; | |
| # These are the domain names (including subdomains) which this configuration will accept connections for | |
| server_name mydomain.com; | |
| # This line is for permanently redirecting to SSL/TLS | |
| return 301 https://mydomain.com$request_uri; | |
| } |
- Install git.
- Install Node.js v14.
- Change npm's default global directory in order to avoid having to run global installs with
sudo. - Install Docker.
- Clone the repo:
git clone https://github.com/blocknetdx/xlite.git - Open the directory:
cd xlite - Checkout the appropriate branch e.g.
git checkout dev. - Install dependencies:
npm install - Run build script:
npm run build - Set
GH_TOKENenvironment variable to a GitHub Token with appropriate permissions for creating releases and pushing release builds.
Ubuntu makes it very easy to record scripts into files that can be run anywhere from the command line, allowing you to script out common tasks and easily run them without always having to copy/paste or remember long, very technical commands.
Ubuntu will automatically look to see if there is a ~/.local/bin folder and will allow any script file in there to be run as a command.
For example, you might enter sudo mount /dev/nvme0n1p1 /media/8tb to mount an external drive. You can easily script that to run as a command.
First, check inside the .local folder:
ls ~/.local| #!/bin/bash | |
| set -e | |
| EMAIL="my@emailaddress.com" | |
| PASSWORD="mypassword" | |
| DOMAIN="mysubdomain.mydomain.com" | |
| echo "-> Start Node Pilot" |
The Node Pilot JSON-RPC server provides API access to every single Node Pilot operation, from initial registration to creating, staking, and updating nodes.
The RPC server is available both via HTTP and via the command line using the Node Pilot CLI.
The server can be accessed via port 34417 on the host machine at path /v1 e.g. http://localhost:34417/v1. It follows the JSON-RPC 2.0 Specification. All requests must be POST requests sent with a Content-Type of application/json. The payload must be in the following form:
- Ethereum 2.0 support
- Pocket BETA-0.9.x support
- Ethereum Goerli testnet support
- Pocket nodes are now served via Node Launcher which allows for one-click updating like other Node Pilot supported chains
- All Node Pilot functionality is exposed via a JSON-RPC server at port 34417 (temporary documentation can be found here: https://gist.github.com/rBurgett/22605a4880e6f6e1cda15e426d02b299)
- All key passwords are now encrypted
- Nodes now automatically restart if they unexpectedly shut down
- You can shut down Node Pilot while leaving your nodes running
Provider Story:
- Provider contacts us and gives us
- email address
- pokt address
- for each gateway
- public IP address of gateway server
- each supported chain ID and accompanying local endpoint e.g. http://10.10.0.1:9500.
- SSH login (w/ sudo privileges) via port 39889
- Direct public ports from 39880-39888 to the gateway server
- We create a provider account for them which includes