github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-08 21:59:09 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

Traefik updating? #218

New Issue
Closed
opened 2025-11-13 11:53:27 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-13 11:53:27 -06:00
Owner
Copy Link

Originally created by @AleksCee on GitHub (Apr 6, 2025).

Crowdsec container is on latest (by the installer), pangolin is pined to the version while building the installer, in the doc for pangolin and the other contains says latest is ok, is this the best way, too?

And what about Traefik, in this doc https://doc.traefik.io/traefik/migration/v3/#v334 there is a migration hint. So is it’s safety to use latest here to? What is the best way for traefik related to pangolin?

Thanks, Alex

Originally created by @AleksCee on GitHub (Apr 6, 2025). Crowdsec container is on latest (by the installer), pangolin is pined to the version while building the installer, in the doc for pangolin and the other contains says latest is ok, is this the best way, too? And what about Traefik, in this doc https://doc.traefik.io/traefik/migration/v3/#v334 there is a migration hint. So is it’s safety to use latest here to? What is the best way for traefik related to pangolin? Thanks, Alex
GiteaMirror commented 2025-11-13 11:53:27 -06:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Apr 6, 2025):

Generally it's safe to update Traefik as it's very stable but of course always check their release notes for any changes you may have to make. We will also keep track of this update it in the installer periodically.

You can always test a version to see if it works, by first backing up your entire config so you can easily roll back.

@miloschwartz commented on GitHub (Apr 6, 2025): Generally it's safe to update Traefik as it's very stable but of course always check their release notes for any changes you may have to make. We will also keep track of this update it in the installer periodically. You can always test a version to see if it works, by first backing up your entire config so you can easily roll back.
GiteaMirror commented 2025-11-13 11:53:28 -06:00
Author
Owner
Copy Link

@wouldntyouknow commented on GitHub (Apr 8, 2025):

I have updated to v3.3.5 (along updating Pangolin to v1.2.0) and am having zero issues.

@wouldntyouknow commented on GitHub (Apr 8, 2025): I have updated to v3.3.5 (along updating Pangolin to v1.2.0) and am having zero issues.
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
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#218
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?