Point domain name at home page of an app

[rpmcoding]

Currently I have several apps at

domain.com/app/app1
domain.com/app/app2
domain.com/app/app3

etc.

I would like to point

newdomain1.com to what you currently see on domain.com/app/app1 home page
newdomain2.com to what you currently see on domain.com/app/app2 home page
newdomain3.com to what you currently see on domain.com/app/app3 home page

Does anyone know how this would be done? Thanks in advance.

[melohagan]

Hey @rpmcoding

There's some nginx docs here that may be useful: https://docs.budibase.com/docs/reverse-proxy

[shogunpurple]

you will need to replicate your server block to serve from the different domains:

  server {
    listen       10000 domain1.net;

...

  server {
    listen       10000 domain2.net;

This will show you what you need to do.
https://www.nginx.com/resources/wiki/start/topics/examples/server_blocks/

Not really budibase specific so marking this as answer.

[rpmcoding]

@shogunpurple thanks.

I had previously set up the server blocks so that I can serve budibase from multiple domains and that worked just fine.

The part I am struggling with is pointing a domain or subdomain in this case to the deployed app's home page rather than the budibase builder login screen.

When accessing ila.domain.com I get the error:- "There was an error loading your app
The Budibase client library could not be loaded. Try republishing your app."

Here is the server block code:-

server {
    server_name ila.domain.com;

    location / {
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_pass http://localhost:10000/app/ila;
    }

    client_max_body_size 50m;

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/ila.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/ila.domain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

server {
    if ($host = ila.domain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    server_name ila.domain.com;
    listen 80;
    return 404; # managed by Certbot
}

[JayP718]

Hi did you ever get this working and if so how? @rpmcoding

[rpmcoding]

Unfortunately not...

[IchthysMaranatha]

Can be done this way, only showing key changes needed
location / {

rewrite ^(/.+)$ $1 break;
rewrite ^(.*)$ /app/ila;
.....
.....
proxy_pass http://localhost:10000;
}
Now landing on the domain or subdomain which has been set up, it will directly go to the app