mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2257] configure in advanced #1608
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#1608
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 @keivanipchihagh on GitHub (Sep 7, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2257
Hello there! I was wondering if it's possible to pre-configure the Nginx-Proxy-Manager to have -for instance- a few Proxy Hosts when the container is created? I couldn't find anything related to this on the internet.
Thank you
@the1ts commented on GitHub (Sep 10, 2022):
Not sure 100% sure what you are requesting but my thoughts below:
If you are using SQLlite rather than MySQL as the backing DB, you can simply have a copy of the NPM starter volumes with the required hosts already provisioned so NPM will start an existing config and password. If the certs are old, they will automatically be updated by the standard process.
If you are using MySQL, you will have to have MySQL and NPM volumes created with the Proxy Hosts and password you require so they are both provisioned with that data.
@keivanipchihagh commented on GitHub (Sep 13, 2022):
Oh I did not know that. So having copied the preserved data should do the job?
@the1ts commented on GitHub (Sep 13, 2022):
Since good container deployments keep their config and data outside the container to allow updates, yes if you follow the setup guide, all data will be in the volumes so can be plugged back in recovering back to the state when it was copied.
@keivanipchihagh commented on GitHub (Sep 14, 2022):
Great! thank you! will test it asap.