[Feature Request] NGINX and/or Apache proxies to other local dev servers.

Indigo

@jafenech Welcome to the forums! And glad you found Indigo 🙂

Everything inside ~/.indigo/stacks/* is actually ephemeral, and is compiled each time you start a stack. So anything you put in there will be blown away regularly.

What you actually need to do is documented at https://indigostack.app/docs/how-to/advanced-service-configuration/

I feel your frustration in this — a bunch of people have been tripped up in the same way you have so I need to have a good think about how to make overriding config clearer.

Do let me know if the docs linked above don't clarify things sufficiently — Indigo is absolutely intended to enable the exact scenario you're hoping for, so I want you to succeed in it! 🙂

Indigo

On a secondary note, we're getting very close to releasing v.1.0.0 so I'd value any further thoughts you might have re: installed-device-count limits.

Do you have more than 3 Macs you use personally, or is it a team scenario, or some ambiguous in-between situation?

Mamp Pro's one-at-a-time restriction seems very unusual; we certainly won't be doing that. However a limit of 3 didn't seem too unusual... until your comment above, which has me worried that in some cases it will be a problem 🙂 I've coded our upcoming licensing backend to allow per-customer device limit overrides, so we can easily do that on a case-by-case basis, over and above whatever the standard limit eventually is.

jafenech

Indigo Hi, will definitely try when home.

So my scenario is two pc's once at home and one at the office, and two runabout machines (a 16 inch and a 14 inch macbook) basically. The 14 inch i only use when i travel, and the 16 inch i use when visiting clients but regulalry swap between 14 / 16 depending on battery / client. With mamp it was very easy as long as no two instances are running at the same time, save to cloud (dropbox) and restore on any machine for db's (and git for code). The db part i am replicating by dumping db and storing to cloudflare when i do my final git push for the day. So whichever machine i cam on, dropbox is always up to date

I am happy to pay a license for up to 5 machines or for 3 and something extra for another two if needed, but it would be great to have to option as long as only one instance is running at any one point basically. (ideally ofc)

jafenech

To clarify further, one machine and one laptop belong to a specific employer and have MDM installed, Thats 1 mac and 1 laptop, The other 2 machines, 1 mac mini, and 1 14inch mbp, are exclusively mine. So the machines also have different projects running on them.

Indigo

Thanks for your replies. How do you keep track of all those Macs!? 🤣 Haha.

I think it would work to simply offer the option for anyone who needs it to contact us with how many macs you personally use and we'll stick an override into the system just for you. You can run Indigo on them all at once if that's useful to you (I can think of several use-cases myself eg I have an Indigo install running several personal websites on our LAN 24/7). The default limit's there simply to avoid people buying one copy for their whole team, basically.

jafenech

How do you keep track of all those Macs!? 🤣 Haha. With frequent trips back home in the begining 😃 . One final question if I may please, how do I add a proxy configuration to the existing front proxy so it listens for a specific server name, and proxies that to 3005 .... like this ?

server {
    server_name api.mylocalsetup.com;

    location / {
        proxy_pass https://localhost:3005/;
        proxy_http_version 1.1;
        proxy_set_header Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        chunked_transfer_encoding off;
        proxy_buffering off;
        proxy_cache off;
    }

listen 443 ssl;
    ssl_certificate     "{{ssl_certificate_dir}}/cert.pem";
    ssl_certificate_key "{{ssl_certificate_dir}}/key.pem";

}

Where do I need to put this config, so that is permanently added to my "System" proxy if I am understanding this well

I tried adding a system/nginx_reverse_proxy/conf/sites-enabled/mycustomreverseproxy.conf to an nginx only stack, but since the nginx stack requires the addition of a site, it keeps trying to get the files from there (although i could see my conf file being added to the system) if that makes any sense

jafenech

Another attempt, I have added a stack with just nginx. I have added my url (my-local-proxy.com) inside nginx (so it is added to my hosts file) and pointed the site root to an empty folder. Added my proxy config (below) which I can now see under my compiled "system" nginx reversed proxy (I added it to the stack under system/nginx_reverse_proxy/conf/sites-enabled/my-reverse-proxy.conf) and this is being copied correctly to the running (compiled) folder in .indigo/stacks/system-stack/nginx_reverse_proxy/my-reverse-proxy.conf. Changes are also being picked up.

My proxy looks like this :

`server {
server_name my-local-proxy.com;

resolver 127.0.0.1;

listen  80;

listen 443 ssl;
ssl_certificate     "/Users/myname/.indigo/ssl/cert.pem";
ssl_certificate_key "/Users/myname/.indigo/ssl/key.pem";

access_log  "{{log_path}}/proxy-test-local.log";



location  ~ ^/ {
    proxy_ssl_verify off;  
    proxy_pass  https://localhost:3005;
    proxy_http_version 1.1;
    proxy_set_header Host $http_host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    chunked_transfer_encoding off;
    proxy_buffering off;
    proxy_cache off;
}

https://localhost:3005 opens ok in my web browser (with the obvious ssl error since the container is using self signed ssl). I have also tried https://127.0.0.1:3005 as proxy pass to no avail. The errors vary from 500 internal server error, to bad gatway to 403 forbidden.

Any further pointers as to what I am doing wrong would be greatly appreciated. Thank you in advance

Indigo

Thanks for your patience awaiting my follow-up.

I've realised my instructions above were rather horribly incomplete — I really do apologise for any time you've spent unsuccessfully attempting to get this to work.

I've created a test stack using my own Indigo install, and customised it as necessary to provide an external reverse proxy, and it does work rather nicely. I have to admit though, the steps to get there weren't fun 🙁

This is a pretty great feature and I'd love to add it to Indigo. I just have to get past the feature freeze of the current release candidate rounds first!

In the meantime, I'm adding a page to the docs to explain how I went about setting this up. It's not so hard to replicate when you know all the required steps! I'll post here again once that's up — should only be a couple of hours.

jafenech

Absolutely no apology necessary ! Will test (probably later on this afternoon).

Indigo

Thanks!

The doc is now up at https://indigostack.app/docs/how-to/creating-a-custom-reverse-proxy/

It turned out rather longer than I hoped, and only at the very end of creating it did I realise it would be far easier simply providing a downloadable example stack, which self-illustrates everything much more easily. So I added that to the top, probably rendering the entire rest of the tutorial worthless lol Ah well...

Hope it helps you get your scenario running, and as always, any thoughts you have on the new documentation will be gratefully accepted.

jafenech

I confirm that that worked !!!! Thank you so much. I must admit, I went down the route of the downloadable stack, and editing my proxy conf directly there. Which also made me realise, that if i sync Documents/Indigo via dropbox, I might also potentialy be able to sync changes between laptop and pc (if I turn on always available offline). I will report back on this later .

Indigo

Great! Glad it worked.

jafenech sync changes between laptop and pc

Absolutely — this was a primary design goal right from the start with Indigo, and a driver for using a simple json data format for the stack configs. My own use-case is to store my various *.indigostack config files in the root of their related projects, which are all version controlled in git. That way I have a commit history for my infrastructure, just like I did in the bad old days of docker-compose.yaml 🙂 Oh and of course other team members automatically get infrastructure updates when they pull git changes.