So the domain thing has been solved:
For anyone wanting to do what I am.
You need to create three NGINX virtual hosts:
the portal file needs to look like this:
server {
listen 80;
server_name portal.thisiswhereyoucanaccessmyportal.com;
rewrite_log on;
gzip on;
gzip_buffers 16 8k;
gzip_comp_level 4;
gzip_http_version 1.1;
gzip_min_length 1280;
gzip_types text/plain text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript image/x-icon image/bmp;
gzip_vary on;
# The Go application server
location / {
rewrite /(.*) /[CHANGE THIS TO THE ORGANISATION ID YOU ARE USING]/portal/$1 break;
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_pass http://dashboard;
}
location /portal-assets/ {
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_pass http://dashboard;
}
location /api/public {
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_pass http://dashboard;
}
}
If you need your ORGANISATIONID you can get that by clicking any user and copying their RPC credentials.
The portal should fire up given that you have set it up correctly.
Will post a solution for the “no nodes running” issue as soon as I have one.