Supporting both HTTP Auth & Private Repos #8

New Issue

2024-06-12T14:04:50Z

basebuilder commented

2024-06-12 14:04:50 +00:00

How to configure a site which uses both HTTP Basic Auth and Private Repository options. The app config file has the following two stanzas:

# HTTP basic auth protected deploy endpoint
COMPOSE_FILE="compose.yml:compose.auth.yml"
AUTH_ENABLED=1
AUTH_USERNAME=foo
SECRET_AUTH_PASSWORD_VERSION=v1

# Private repository deployment
COMPOSE_FILE="compose.yml:compose.private.yml"
PRIVATE_ENABLED=1
SECRET_DEPLOY_KEY_VERSION=v1

Simply un-commenting out both COMPOSE_FILE= lines causes what seems the second one to supercede the naming the compose.auth.yml variable which once running the secret generate -a command for HTTP Auth results in:

$ abra app secret list sub.domain.org
+------------+---------+-----------------------------------------------+-------------------+
|    NAME    | VERSION |          GENERATED NAME                       | CREATED ON SERVER |
+------------+---------+-----------------------------------------------+-------------------+
| deploy_key | v1      | chaffing-traffic-stony-illusive-baked-bridged | true              |
+------------+---------+-----------------------------------------------+-------------------+

Which should be labeled auth_password but is wrongly labeled deploy_key
I tried making a new single-line such as:

COMPOSE_FILE="compose.yml:compose.auth.yml:compose.private.yml"

But this does now seem to address the issue either.

How to configure a site which uses *both* `HTTP Basic Auth` and `Private Repository` options. The app config file has the following two stanzas: ``` # HTTP basic auth protected deploy endpoint COMPOSE_FILE="compose.yml:compose.auth.yml" AUTH_ENABLED=1 AUTH_USERNAME=foo SECRET_AUTH_PASSWORD_VERSION=v1 # Private repository deployment COMPOSE_FILE="compose.yml:compose.private.yml" PRIVATE_ENABLED=1 SECRET_DEPLOY_KEY_VERSION=v1 ``` Simply un-commenting out both `COMPOSE_FILE=` lines causes what seems the second one to supercede the naming the `compose.auth.yml` variable which once running the `secret generate -a` command for HTTP Auth results in: ``` $ abra app secret list sub.domain.org +------------+---------+-----------------------------------------------+-------------------+ | NAME | VERSION | GENERATED NAME | CREATED ON SERVER | +------------+---------+-----------------------------------------------+-------------------+ | deploy_key | v1 | chaffing-traffic-stony-illusive-baked-bridged | true | +------------+---------+-----------------------------------------------+-------------------+ ``` Which should be labeled `auth_password` but is *wrongly* labeled `deploy_key` I tried making a new single-line such as: ``` COMPOSE_FILE="compose.yml:compose.auth.yml:compose.private.yml" ``` But this does now seem to address the issue either.

basebuilder referenced this issue from a commit

2024-06-13 09:47:05 +00:00

update .env.sample and README to clarify HTTP Auth & Private repos #8

stevensting commented

2026-04-05 16:03:14 +00:00

this one is solved

🎉 1

stevensting closed this issue

2026-04-05 16:03:14 +00:00

Sign in to join this conversation.