Issues running on Ubuntu 20.10 about micro-frontends-in-action-code HOT 6 CLOSED

Got the same problem. But now I got it working by comment the access_log declaration at 04_routing/webserver/nginx.conf.
The problem that its just runs with root user only still remains. Even www-data as user (default for nfinx service) was not possible.

# comment out on windows
#access_log /dev/stdout compact;

Starting the app using

 sudo -u root  npm run 04_routing  

from micro-frontends-in-action-code.

Final solution which solve all the problems was the following.

daemon off;
error_log  /tmp/error.log;
pid        /tmp/nginx.pid;
events {}

http {
  upstream team_decide {
    server localhost:3001;
  }

  upstream team_inspire {
    server localhost:3002;
  }

  log_format compact ':3000$uri $status';

  server {
    listen 3000;

    
    # comment out on windows
    access_log /tmp/access.log compact;

    location /product/ {
      proxy_pass  http://team_decide;
    }

    location /decide/ {
      proxy_pass  http://team_decide;
    }

    location /recommendations {
      proxy_pass  http://team_inspire;
    }

    location /inspire/ {
      proxy_pass  http://team_inspire;
    }
  }
}

I found that by visiting the full example at https://www.nginx.com/resources/wiki/start/topics/examples/full/. This sets log an Pid files to /tmp which is accessible for all users by default.

from micro-frontends-in-action-code.

Thanks @hurzelpurzel . Dumb question - where do I put that configuration? I see under 04_routing/webserver there's a nginx.conf. I tried updating that, but it didn't seem to help.

from micro-frontends-in-action-code.

from micro-frontends-in-action-code.

Yeah, what you did makes sense. It's just that after modifying 04_routing/webserver/nginx.conf to look like your sample nginx config above, and then running npm run 04_routing, it still complains:

nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)

This despite the fact that I look at package.json, and for the 04_routing script, I see:

"04_routing": "concurrently --names \"nginx ,decide ,inspire\" \"node nginx.js 04_routing/webserver/nginx.conf\" \"mfserve --listen 3001 04_routing/team-decide\" \"mfserve --listen 3002 04_routing/team-inspire\" \"wait-on http://localhost:3000/product/porsche && opener http://localhost:3000/product/porsche\"",

So, it looks like it should be referencing the nginx.conf in the 04_routing/webserver folder.

I did try sudo npm run 04_routing and that did get past the original problem. It introduce a 2nd problem though:

Running Firefox as root in a regular user's session is not supported.

I could work around this problem by taking the URL the script tried to load, and manually copying it into the browser:

http://localhost:3000/product/porsche

Thanks for the help!

from micro-frontends-in-action-code.

@hurzelpurzel, well I spoke too soon. Running as sudo did work for 04_routing example. But once I got to the next chapter, 05_ssi, it fails:

nginx: [emerg] open() "/dev/stdout" failed (6: No such device or address)

I can confirm that 05_ssi/webserver/nginx.conf contains the ssi on feature. So, I'm quite sure that's the intended configuration file.

If I run npm run 05_ssi without sudo, then the error message is different:

nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)

I tried commenting out this line in 05_ssi/webserver/nginx.conf:

access_log /dev/stdout compact;

Since there's a comment mentioning that it should be commented out in Windows (even though I'm on Ubuntu), but no luck.

It's clearly a file permission issue, but I'm not sure what's going wrong. Any further suggestions?

EDIT: Oh, wait. It still works with sudo, provided I comment out the line above

from micro-frontends-in-action-code.