mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #331] Upgrade Instructions? #291
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#291
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @mikepruett3 on GitHub (Mar 16, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/331
My appoligies if this has been documented somewhere else, but I did look at both all of the Issues and documentation from the site.
I am currently running v2.0.14, which was built and started via docker-compose...and I was wondering what I would need to do to upgrade to the latest version?
docker-compose.yml
@jc21 commented on GitHub (Mar 16, 2020):
Nope you should be fine. Both images have updates though, I would recommend making a backup of your folders beforehand.
@mikepruett3 commented on GitHub (Mar 16, 2020):
So I did the following:
Yet the version number did not change (still says v2.0.14 at bottom of page). I might have missed something easy. When I started, I copied the doc/example folder to a new folder called "prod" at the top of the nginx-proxy-manager directory.
Sorry, I am not really good with docker-compose.
Thanks for any assistance!
@mikepruett3 commented on GitHub (Mar 16, 2020):
Nevermind... I'm kind of slow on this one! :)
I ran a 'docker-compose down', and pulled the latest image, then started it again.
Thanks for your help!