cache: Since the "static range" (the data your client responsible for) is distributed by HatH network, keeping the cache data is essential behavior of a good/healthy client.Using docker image in a VM-like docker way (instead of "designed way" docker should be used), most files can be store in the container directly.īut according to the mechanism how docker works and also for a better experience, link several volumes to external storage will be recommended: Which is built by Docker Hub according to this repository. The list can be found at wikiĭocker build -t hath:tagwhateveryoulike. HatH_ARGS: The parameter which will be used after HatH client.HatH_JAR: The filename which HatH client is (inside the archive).HatH_ARCHIVE: The filename which HatH_DOWNLOAD_URL will be downloaded as.HatH_PATH: The path which extracted HatH client will be deployed to.HatH_USER: The username which will be created in image and will be used to run the HatH client.Execution related but recommend not to modify:.HatH_PORT: The port you choose which HatH client will used to provide traffic, must be configured correctly at corresponding client configuration page and Internet reachable."Client Key" you get from Clients dashboard and enter the corresponding client configuration page. HatH_KEY: DO NOT FILL YOUR INFO IF YOU ARE GOING TO BUILD PUBLIC IMAGE.5 digits (at the time) number "Client ID#" you get from Tenboro. HatH_ID: DO NOT FILL YOUR INFO IF YOU ARE GOING TO BUILD PUBLIC IMAGE.HatH_DOWNLOAD_SHA256: SHA256 hash provided at Clients dashboard, used for file integrity check.HatH_VERSION: HatH version used to composite downloading URL and note.Had been verified in Docker environment of Synology DSM, should be no problem in others. A simple container of based on openjdk image and one-liner shell script only.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |