NginxProxyManager
Feature: Load balancer functionality
This was a quickly put together implementation of NPM with the ability to add and manage upstreams. Im very open to comments since i just kinda hacked this together so I could use this for myself ive never worked in most of these frameworks so if anything looks wrong let me know :)
This adds an upstream tab where you can manage the upstreams avaliable maybe this should be put somewhere else im not sure this worked for now! You then can select the upstream in the proxy_host see screenshots below. At the moment if you want a weight you have to set weight=2 instead of just 2 since there are a few other options there that i actually use like turning off hosts and whatnot
Docker Image for build 2 is available on DockerHub:
nginxproxymanager/nginx-proxy-manager-dev:pr-4739
[!NOTE] Ensure you backup your NPM instance before testing this image! Especially if there are database changes. This is a different docker image namespace than the official image.
[!WARNING] Changes and additions to DNS Providers require verification by at least 2 members of the community!
![nginxproxymanagerci[bot] avatar](https://avatars.githubusercontent.com/in/231045?v=4 "Published by a pub.dev verified publisher"){kind=small}
Now that im thinking of it maybe putting the upstream form within the forward proxy form would be better instead of separating them does anyone have any ideas if thats a better idea?
id look something like this (photoshopd)
I think it may still be worth it to have them separated as you could want to include the same upstream for proxy hosts and stream hosts if possible?
I think it may still be worth it to have them separated as you could want to include the same upstream for proxy hosts and stream hosts if possible?
Thats actually a great point I dont use the streams ill setup a test and implement that.
Great work! But I have some bad news, I rewrote the interface in React and merged it to develop.. Your changes could still be applied, but it will need more work and thought.
I was working on upstreams in the v3 branch, but I'm moving some of that functionality back to v2, and this work is great.
