starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #418] All in one docker container #354

New issue

Closed

opened 2026-02-26 06:32:31 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:32:31 +03:00

Owner

Originally created by @antipiot on GitHub (May 22, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/418

Hello!
First of all thanks for your great work, Nginx-proxy-manager looks great and is very easy to use!

I may suggest some changes to make things even easier for beginners:

Actually for Nginx Proxy Manager to work, you need 2 containers running and i feel it would be great and easier to run if everything was packed in a single container, so both Nginx and db would reside in the same docker container.

This way you may not to have to create a config file and use docker compose and just run docker run -d
As another + i have a lot of containers running, and if every one of them would reside on external db, it may possibly double the number of running containers .

It may be possible to leave support for an external db in case of need

Originally created by @antipiot on GitHub (May 22, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/418 Hello! First of all thanks for your great work, Nginx-proxy-manager looks great and is very easy to use! I may suggest some changes to make things even easier for beginners: Actually for Nginx Proxy Manager to work, you need 2 containers running and i feel it would be great and easier to run if everything was packed in a single container, so both Nginx and db would reside in the same docker container. This way you may not to have to create a config file and use docker compose and just run docker run -d As another + i have a lot of containers running, and if every one of them would reside on external db, it may possibly double the number of running containers . It may be possible to leave support for an external db in case of need

kerem

2026-02-26 06:32:31 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@chaptergy commented on GitHub (May 11, 2021):

As another + i have a lot of containers running, and if every one of them would reside on external db, it may possibly double the number of running containers .

Yes, but if every container uses an external DB you just need one single DB to provide storage for them all, and don't need to run many instances of the same little used DB system.

You already can run this without creating a config file (just via environment variables), or using SQLite.

@chaptergy commented on GitHub (May 11, 2021): > As another + i have a lot of containers running, and if every one of them would reside on external db, it may possibly double the number of running containers . Yes, but if every container uses an external DB you just need one single DB to provide storage for them all, and don't need to run many instances of the same little used DB system. You already can run this without creating a config file (just via environment variables), or using SQLite.

kerem commented

2026-02-26 06:32:31 +03:00

Author

Owner

@antipiot commented on GitHub (May 21, 2021):

Yes, but if every container uses an external DB you just need one single DB to provide storage for them all, and don't need to run many instances of the same little used DB system.

You already can run this without creating a config file, or using SQLite.

Sorry for my late answer - thanks for your reply.
You're absolutely right - i'm not used to this :-)

Thanks for helping and clarifying!

@antipiot commented on GitHub (May 21, 2021): > Yes, but if every container uses an external DB you just need one single DB to provide storage for them all, and don't need to run many instances of the same little used DB system. > > You already can run this without creating a config file, or using SQLite. Sorry for my late answer - thanks for your reply. You're absolutely right - i'm not used to this :-) Thanks for helping and clarifying!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#354

No description provided.

Rows
Columns