starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-13 15:13:33 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

.gitignore add challenges/* #268

New Issue
Closed
opened 2025-12-29 01:20:39 +01:00 by adam · 3 comments
adam commented 2025-12-29 01:20:39 +01:00
Owner
Copy Link

Originally created by @gertcuykens on GitHub (Dec 16, 2017).

Can challenges/* be added to .gitignore please thx

Originally created by @gertcuykens on GitHub (Dec 16, 2017). Can `challenges/*` be added to .gitignore please thx
adam closed this issue 2025-12-29 01:20:40 +01:00
adam commented 2025-12-29 01:20:43 +01:00
Author
Owner
Copy Link

@lukas2511 commented on GitHub (Dec 16, 2017):

I was asked this several times by now, and I'm still saying no.

My opinion on this is that public(!) challenge files have nothing to do right next the very private key files, they should be somewhere like /var/www and considered completely public.

@lukas2511 commented on GitHub (Dec 16, 2017): I was asked this several times by now, and I'm still saying no. My opinion on this is that public(!) challenge files have nothing to do right next the very private key files, they should be somewhere like /var/www and considered completely public.
adam commented 2025-12-29 01:20:45 +01:00
Author
Owner
Copy Link

@gertcuykens commented on GitHub (Dec 17, 2017):

I put boilerplate code in it that dispatches the challenges either true scp or gcloud app deploy acme.yaml --project $(PROJECT) it's like a extension of the hook.sh script. In case of scp i can find a work around referring to /tmp/challenges or something but in case of gcloud it gets messy to put it somewhere else

@gertcuykens commented on GitHub (Dec 17, 2017): I put boilerplate code in it that dispatches the challenges either true `scp` or `gcloud app deploy acme.yaml --project $(PROJECT)` it's like a extension of the hook.sh script. In case of `scp` i can find a work around referring to /tmp/challenges or something but in case of gcloud it gets messy to put it somewhere else
adam commented 2025-12-29 01:20:45 +01:00
Author
Owner
Copy Link

@lukas2511 commented on GitHub (Dec 17, 2017):

You can add a local exclusion using .git/info/exclude, but I'm suggesting to find a way to work with a tmp directory.

@lukas2511 commented on GitHub (Dec 17, 2017): You can add a local exclusion using `.git/info/exclude`, but I'm suggesting to find a way to work with a tmp directory.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#268
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?