I got it solved:
First I noticed:
I'm working via nginx, as stated in the flow install instructions. (changed port to 8080 instead of 80)
The example app works fine this way, including pharo rest communication.
But as stated, committing a package other than my own, raises the warning dialog.
On the other hand, when I use amber directly via port 3000 (amber serve --port 3000), and I then publish the library package, it works fine.
The example application does not, especially not the rest messaging with pharo.
Then I changed the nginx config file: (see addition in red)
server {
listen 8080;
server_name flow.dev;
## Configure here your path to the frontend.
## Have in mind that this is for development.
## For production you should somehow use the public/ dir with the built output
root "C:/nodejsprojects/testingFlow4/frontend";
try_files $uri $uri/index.html $uri.html @pharoFlow;
#map $http_upgrade $connection_upgrade {
# default upgrade;
# '' close;
#}
location @pharoFlow {
proxy_pass http://127.0.0.1:3333;
proxy_http_version 1.1;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#proxy_set_header Upgrade $http_upgrade;
#proxy_set_header Connection $connection_upgrade;
}
location @amberFlow {
proxy_pass http://127.0.0.1:3000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_redirect off;
}
location ^~ /src/ {
error_page 405 = @amberFlow;
try_files $uri @amberFlow;
}
location ^~ /bower_components/ {
error_page 405 = @amberFlow;
try_files $uri @amberFlow;
}
gzip on;
}
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
.
Locked
