Self Hosted - Self-hosting your services.

12312 readers

29 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 3 years ago

MODERATORS

Zoe8338@lemmy.ml

dogmuffins@lemmy.ml

testman@lemmy.ml

GitHub PAT in docker-compose file? (infosec.pub)

submitted 2 years ago* (last edited 2 years ago) by TheButtonJustSpins@infosec.pub to c/selfhost@lemmy.ml

3 comments fedilink hide all child comments

I used to have this working, but I haven't used it in a while and had to rebuild the server in between, and now it doesn't. How do you set up the PAT in the URL in order to access private repos when building using docker compose?

build: 'https://PAT@github.com/username/repo.git#branch' is what I'm trying to use, but I get:

failed to solve: failed to read downloaded context: failed to load cache key: invalid response status 404

EDIT: See comment for (silly) resolution. The above works.

top 3 comments

sorted by: hot top controversial new old

[–] TheButtonJustSpins@infosec.pub 2 points 2 years ago

I'm an idiot and can't read. There are two services in the compose file and it was the other one that was throwing the error, and that was because I forgot the .git.

[–] terribleplan@lemmy.nrd.li 1 points 2 years ago (1 children)

Pretty sure it needs to be https://$user:$pat@github.com/username/repo.git#branch.

[–] TheButtonJustSpins@infosec.pub 1 points 2 years ago

Same behavior if I add the username: before the PAT.