evernode1 landing page
Frequently Asked Questions
SO how do we use the extra setting for docker images?
when you enter the image name, you append the information you want to give AFTER the version. (MUST start with --, even if you dont state a version, you MUST start with --) then using -- to divide each. the things you can state are; --peer--[value] --user--[value] --gptcp1--[value] --gpudp1--[value] --gptcp2--[value] --gpudp2--[value] --contract--[false] --env1--[KEY]-[VALUE] --env2--[KEY]-[VALUE] --env3--[KEY]-[VALUE] --env4--[KEY]-[VALUE] --domain--[domainname.com] --subdomian--[name] --ssl--false you can add these in any order, and as many as you want to change, if you dont state, then the default will be used. for example... jgraph/drawio:latest--user--8443 this will then map the, "user port" to which ever is assigned on acquiring, to the internal port of 8443. (so effectively it performs the docker command of - p [$acquired_user-port]:[custom_user-port]) this allows this STOCK image of jgraph/drawio:latest to be used DIRECTLY. when it pulls the image, it uses the stated image(and the version) ONLY, so it works on the stock images still. (also of note, for variable Values, using __ will equate to a "space" and .. will equate to a $ character, which could be handy) another example with MORE fields, how about a minecraft server, setting EULA, and two PORTS 'evdevkit acquire -i itzg/docker--minecraft-server:latest--user--25565--gptcp1--19133--env1--EULA-TRUE'
So how does website hosting work?
when you specify the --domain--yourdomain.com the specified domain, gets routed to the "gp_tcp_port" port (this will automatically route the assigned given external port) so depending on the docker image that you use, will depend on how you assign the "gp_tcp_port" port internally. for example if using a wordpress docker image, you would specify --gptcp1--443 as port 443 is the https port they tie to internally, so when this gets routed external to the internal tcp port, it goes to the internal port of the instance 443... so effective will be a direct link -p 443:443 to use YOUR domain, on a evernode you will need to; set "A" record(s) for each IP of the evernode(s) you want to use. set "NS" record(s) to subdomain "_acme-challenge." for every evernode you want to use. set a "TXT" record to the root of your domain, of the instances public key. (FYI, we use the TXT record to protect your domain, so ONLY the instance that YOU create can be tied to YOUR domain, and the NS record on the subdomain _acme-challenge. so we can use DNS-01 mothod of getting SSL files for your domain) FYI if you DONT need a SSL/TLS type connection (http://) you need to state --ssl--false this is optional, as you may have you OWN ssl proxy before its routed to the evernode. the tls files are provided and updated weekly within your instance at; /contract/tls/cert.pem /contract/tls/privkey.pem /contract/tls/chain.pem /contract/tls/fullchain.pem /contract/tls/domain_ssl_update.log and just a FYI, the "hosts" tls/ssl files are still provided at; /contract/cfg/tlscert.pem /contract/cfg/tlskey.pem
You mentioned Environment Variables what about those ?
yes "Environment variables" will also be added to the docker instance to allow their use within the entry point script thats set within the docker image. needs to be within the the start.sh/entrypoint.sh or child processes to be used. OR they are also written to file /contract/env.vars so that you can source /contract/env.vars this is also pre sourced in the file .bashrc for terminal use. these are the names of all the variables added, i think they are all are self explanatory! $HOST_DOMAIN_ADDRESS $CUSTOM_DOMAIN_ADDRESS $EXTERNAL_PEER_PORT $INTERNAL_PEER_PORT $EXTERNAL_USER_PORT $INTERNAL_USER_PORT $EXTERNAL_GPTCP1_PORT $INTERNAL_GPTCP1_PORT $EXTERNAL_GPUDP1_PORT $INTERNAL_GPUDP1_PORT $EXTERNAL_GPTCP2_PORT $INTERNAL_GPTCP2_PORT $EXTERNAL_GPUDP2_PORT $INTERNAL_GPUDP2_PORT