Cutlery/homepage
1
0
Fork 0
mirror of https://github.com/gethomepage/homepage.git synced 2025-06-01 04:34:31 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix: remove non-working pathPrefix option for docker connections

Browse Source
This commit is contained in:
shamoon 2025-05-22 09:45:18 -07:00
parent 6cf3abd45e
commit ee07a7dcbe
No known key found for this signature in database
2 changed files with 2 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/configs/docker.md
View File

@ -79,16 +79,15 @@ my-docker:
Note: This does not require TLS certificates if the proxy handles encryption. Do not use `protocol: https` unless you’re sure the target host supports HTTPS. Note: This does not require TLS certificates if the proxy handles encryption. Do not use `protocol: https` unless you’re sure the target host supports HTTPS.
You can further customize the connection options via `pathPrefix` and `headers`: You can also include `headers` for the connection, for example, if you are using a reverse proxy that requires authentication:
```yaml ```yaml
my-docker: my-docker:
host: dockerproxy host: dockerproxy
port: 443 port: 443
protocol: https protocol: https
pathPrefix: /docker_api/ # If a reverse proxy serves the API on a subpath
headers: headers:
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ== # Send an authorization header if the API access is secured via basic auth Authorization: Basic <base64-encoded-credentials>
``` ```
## Using Socket Directly ## Using Socket Directly

4
src/utils/config/docker.js
View File

@ -47,10 +47,6 @@ export default function getDockerArguments(server) {
res.conn.protocol = servers[server].protocol; res.conn.protocol = servers[server].protocol;
} }
if (servers[server].pathPrefix) {
res.conn.pathPrefix = servers[server].pathPrefix;
}
if (servers[server].headers) { if (servers[server].headers) {
res.conn.headers = servers[server].headers; res.conn.headers = servers[server].headers;
} }