1. 24
  1.  

  2. 5

    This is exactly the sort of clear, well-explained reasoning that I wish I saw any of at work. :(

    1. 3

      This shit right here was illuminating af. I run a similar local stack except I throw in a nix build script.

      1. 1

        Just bragging for a moment: you can build non trivial applications in clojure with auth and file backends and business logic in under 10k lines. I’ve done it for various employers.

        1. 1

          Mistyped, 1k lines.

        2. 1

          It’s like a generic design doc for all backends :)

          1. 0

            I come from the Windows world (where IIS is the only web server that matters) so the idea of having to use a (reverse) proxy to (easely) support HTTPS is ludicrous to me.

            1. 4

              IIS fills the same place as nginx in this design.

              1. 2

                You don’t have to, but it is convenient.

                1. 2

                  It’s really easy. Here’s a trivial nginx conf to enable that:

                  server {
                          server_name api.myhost.com;
                          listen 80;
                  
                          location / {
                                  include proxy_params;
                                  proxy_pass http://localhost:5000/;
                          }
                  
                         # Certbot will put in SSL for you
                  }
                  

                  And then you can easily get SNI-based multiple hosts on the same ‘node’ if you’d like. This lets you easily handle SSL stuff and still have whatever web-server you want bound to the local host:port to actually do the action. You can also do all the fun URL rewrite stuff up there if you’d like.

                2. -1

                  This is comprehensive af! It’s bedtime for me but I look forward to delving more into this tmrw.