mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #1320] php #1055
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#1055
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 @modaresimr on GitHub (Aug 15, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1320
nginx proxy manager is a very great tool for managing different websites.
if it is possible to add website serving (static or dynamic) to it it would be great
is there any branch or fork for that?
@aab12345 commented on GitHub (Aug 16, 2021):
You could just use a php docker container and use npm to proxy request to that docker container.
Hope this makes sense.
@modaresimr commented on GitHub (Aug 17, 2021):
I understand such a way. But we have to define a proxy to PHP-fpm and set up a PHP container for each website and map it
It is not an easy way and is not consistent.
@chaptergy commented on GitHub (Aug 19, 2021):
I don't think php will ever be officially integrated. There is a feature request for static website serving, but PHP is explicitly excluded during the discussion.
But there is a code snippet in there which could help you.
@github-actions[bot] commented on GitHub (Mar 6, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 8, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 31, 2025):
Issue was closed due to inactivity.