nginx example in doc?

[r3k2]

Hello,
I look all over for an example nginx config so I can compare with mine, I have my app working but websockets is not connecting, so I think I need to add something to my nginx vhost entry for my domain for this app wrote in rust with yew.
app loads but cant register users etc because I have a
"NS_ERROR_WEBSOCKET_CONNECTION_REFUSED"
my setup in nginx is not as suggested using the dev command trunk run so I pointed nginx vhost to the "dist" folder. and runs but websockets fails. :( I asked people but they all want me to run the whole thing as a with nginx as a reverse proxy with trunk but I refuse nginx should run this.

[futursolo]

I will convert this to a discussion since WebSocket is part of the backend server and I do not think Yew documentation should cover backend deployment.

[futursolo]

my setup in nginx is not as suggested using the dev command trunk run

Are you trying to run Yew in production?

If you are trying to run Yew in production, then you should not use trunk command.
You need to build Yew with trunk build --release and deploy it as a static website.

If you are trying to develop a Yew application, then you should use trunk serve as this starts Trunk Development Server that can provide additional features than using Nginx.

[r3k2]

Hello, I got it working, and yes in production, is why I wanted to have a good nginx config example, because I did not wanted to run trunk but to have nginx run it and now is working, and the only reverse proxy /api I have is to talk with my backend (not related to yew) what is important is that nginx is the one serving the wasm to the client browser with out having to run yew on its own dev http server.
here is the example we can use for others that had my issue so they do not spend like me 5 days hearing people telling me that I should use nginx as a reverse proxy for yew(wrong because yew runs on the browser)

server {
    listen 443 ssl; # IPv4
    listen [::]:443 ssl; # IPv6
    server_name my-portal.org;

    
    ssl_certificate /etc/letsencrypt/live/my-portal.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/my-portal.org/privkey.pem;
    ssl_dhparam /etc/letsencrypt/ssl-dhparams-2048.pem;

# yew frontend
    location / {
      root /home/portal/my-portal/dist;
      try_files $uri $uri/ /index.html;
      include /etc/nginx/mime.types;
      default_type application/octet-stream;
    }
 
# your backend if you have any.

    location /api {
        proxy_pass        http://localhost:8000;
        proxy_set_header  X-Real-IP $remote_addr;
        proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header  Host $http_host;

    }
}