frosty5689/hath

Usage

docker run \
  --name hath \
  --user 99:100 \
  -v /path/to/your/hath/cache:/hath/cache \
  -v /path/to/your/hath/data:/hath/data \
  -v /path/to/your/hath/download>:/hath/download \
  -v /path/to/your/hath/log:/hath/log \
  -v /path/to/your/hath/tmp:/hath/tmp \
  -e HATH_CLIENT_ID=YOUR_HATH_CLIENT_ID \
  -e HATH_CLIENT_KEY=YOUR_HATH_CLIENT_KEY \
  -e UMASK=000 \
  -e TZ=YOUR_TIMEZONE \
  -p YOUR_HATH_PORT/tcp \
  frosty5689/hath

Or if bridge mode doesn't work on your Docker host for some reason...

docker run \
  --name hath \
  --net=host \
  --user 99:100 \
  -v /path/to/your/hath/cache:/hath/cache \
  -v /path/to/your/hath/data:/hath/data \
  -v /path/to/your/hath/download>:/hath/download \
  -v /path/to/your/hath/log:/hath/log \
  -v /path/to/your/hath/tmp:/hath/tmp \
  -e HATH_CLIENT_ID=YOUR_HATH_CLIENT_ID \
  -e HATH_CLIENT_KEY=YOUR_HATH_CLIENT_KEY \
  -e UMASK=000 \
  -e TZ=YOUR_TIMEZONE \
  frosty5689/hath

Parameters

• --net=host - Uses host network with container, use this if H@H have trouble accepting connections. This will let H@H use the host's internal IP for routing instead of the internal IP used by Docker bridge.
• --user 99:100 - Replace the UID and GID with the user and group you want H@H to run as. This will affect the file ownership of the cache and downloads
• -v /hath/cache - H@H cache
• -v /hath/data - H@H data
• -v /hath/download - H@H download
• -v /hath/log - H@H log
• -v /hath/tmp - H@H tmp
• -e HATH_CLIENT_ID - H@H Client ID
• -e HATH_CLIENT_KEY - H@H Client Key
• -e UMASK - This overrides the default umask of 022 which lets all users access the directory and files, but only let the owner modify it. If you set it to 000, then all users will be read and write files created by H@H.
• -e TZ - Timezone H@H will run in
• -e EXTRA_ARGS - Extra arguments added to H@H client command
  • --image-proxy-host=<host> - hostname or IP address for the image proxy
  • --image-proxy-type=<type> - can be "socks" or "http". defaults to "socks" if not provided
  • --image-proxy-port=<port> - the port of the image proxy. defaults to 1080 for SOCKS and 8080 for HTTP if not provided
  • --disable-flood-control - disables the rate limit on connections per IP address. This may be necessary to use with the above trigger unless the non-transparent proxy appears as a private network IP.
  • --disable-ip-origin-check - disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow H@H to work in some common non-transparent proxy configurations. Note that if the non-transparent proxy is a local network IP, speed and rate limits will not be enforced.
  • --disable-file-verification - disable this verification check starting the client. Note however that if the monitoring system detects corrupted files in your cache, your client will be flagged for a full cache verification on next startup, which can take a long time, so it is recommended to leave it enabled unless the client is actually CPU-starved.
  • more that may not be documented here, feel free to create PR to add more
• -p YOUR_HATH_PORT/tcp - The port used by H@H as set in the configuration page. The container port should match the host port.

Buy me a coffee

If you appreciate what I do and would like to show some support, buy me a coffee :)