github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 14:47:04 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #633] Installer does not escape password in config.yml #1540

New Issue
Closed
opened 2026-04-16 08:12:14 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 08:12:14 -05:00
Owner
Copy Link

Originally created by @rovingclimber on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/633

Hi!
New user here, I just used the installer on a new system and Pangolin container failed to start. On checking the container logs it pointed to an error with the admin password not being escaped (pw generated by Keepass contained a backslash). I guess the installer script has not handled this case ....
Thanks!

Originally created by @rovingclimber on GitHub (May 1, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/633 Hi! New user here, I just used the installer on a new system and Pangolin container failed to start. On checking the container logs it pointed to an error with the admin password not being escaped (pw generated by Keepass contained a backslash). I guess the installer script has not handled this case .... Thanks!
GiteaMirror added the stale label 2026-04-16 08:12:14 -05:00
GiteaMirror commented 2026-04-16 08:12:15 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (May 2, 2025):

Ah I think you're right! We're likely going to remove the set password step from the installer & config file very soon in favor of doing it through the UI and optionally reset the admin password via a CLI tool of some kind.

<!-- gh-comment-id:2846198368 --> @miloschwartz commented on GitHub (May 2, 2025): Ah I think you're right! We're likely going to remove the set password step from the installer & config file very soon in favor of doing it through the UI and optionally reset the admin password via a CLI tool of some kind.
GiteaMirror commented 2026-04-16 08:12:16 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 17, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:2887884944 --> @github-actions[bot] commented on GitHub (May 17, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-16 08:12:16 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 31, 2025):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:2923784109 --> @github-actions[bot] commented on GitHub (May 31, 2025): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1540
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?