ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Nginx Proxy Manager

    IT Discussion
    4
    6
    500
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      VoIP_n00b
      last edited by

      https://nginxproxymanager.com/

      I've seen this before, but never used it because I know how to setup a nginx reverse proxy, but I really like the GUI - and it only took 5 minutes to install.

      1 Reply Last reply Reply Quote 0
      • stacksofplatesS
        stacksofplates
        last edited by

        This seems to add a lot of complexity. Nginx configs can be complex but this abstraction in a database seems worse than writing the configs.

        I think you should practice using a config management tool or even terraform templates to generate the configs based on variables.

        scottalanmillerS 1 Reply Last reply Reply Quote 4
        • scottalanmillerS
          scottalanmiller @stacksofplates
          last edited by

          @stacksofplates said in Nginx Proxy Manager:

          This seems to add a lot of complexity. Nginx configs can be complex but this abstraction in a database seems worse than writing the configs.

          I think you should practice using a config management tool or even terraform templates to generate the configs based on variables.

          And you have to set up a Docker environment, likely just for this one workload. Not the end of the world, but one additional layer in all of this. Just manage the configs, they are pretty easy.

          stacksofplatesS 1 Reply Last reply Reply Quote 1
          • stacksofplatesS
            stacksofplates @scottalanmiller
            last edited by

            @scottalanmiller said in Nginx Proxy Manager:

            @stacksofplates said in Nginx Proxy Manager:

            This seems to add a lot of complexity. Nginx configs can be complex but this abstraction in a database seems worse than writing the configs.

            I think you should practice using a config management tool or even terraform templates to generate the configs based on variables.

            And you have to set up a Docker environment, likely just for this one workload. Not the end of the world, but one additional layer in all of this. Just manage the configs, they are pretty easy.

            To be fair, I prefer to use nginx with k8s, but the nginx-ingress operator will auto generate configs based on whatever ingress you define for the cluster. It's really easy. It also works really well with cert-manager who will auto generate TLS certs with letsencrypt and external-dns will auto generate the DNS entries for you in your provider.

            The whole database thing to me is the biggest turn off. Backups become annoying at that point. With bare nginx you just need the configs, with kube you just need the ingress manifests.

            JaredBuschJ 1 Reply Last reply Reply Quote 1
            • JaredBuschJ
              JaredBusch @stacksofplates
              last edited by

              @stacksofplates said in Nginx Proxy Manager:

              To be fair, I prefer to use nginx with k8s,

              I don't see the benefit to Kubernetes in the small shops.

              stacksofplatesS 1 Reply Last reply Reply Quote 0
              • stacksofplatesS
                stacksofplates @JaredBusch
                last edited by

                @jaredbusch said in Nginx Proxy Manager:

                @stacksofplates said in Nginx Proxy Manager:

                To be fair, I prefer to use nginx with k8s,

                I don't see the benefit to Kubernetes in the small shops.

                It genuinely makes things a lot easier. It's really easy to get up and running. Rancher makes federation really easy. Monitoring and central logging can be handled through a single helm chart. mTLS can also be handled through a single helm chart. Service discovery means your networking just works. Developing containerized apps is multiple times easier than developing legacy apps. 12 factor apps make setup easy.

                It's much easier than using config management/infrastructure automation to manage multiple vms.

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post