Sub domain about awoo HOT 8 CLOSED

It looks like Vesta CP uses apache and nginx as its web frontend. Both of these can be configured to reverse proxy to a different port based on subdomain, so for example you could run awoo on port 8080 and have your regular web server forward requests that it recieves to that subdomain to awoo. I don't know how to configure that from Vesta CP, I would suggest just directly modifying the config files for your webserver.

from awoo.

Thanks for the response, I'll try to read the vesta docs.

from awoo.

@nilesr is it possible to set up unicorn to run sinatra with a web socket so i can use nginx listening on said socket instead of the automatic "rerun" server on localhost:8080 that's automatically set up in this repo?

I'm sorry for the noob question, i'm also new to ruby, learning it building this project.

from awoo.

from awoo.

@nilesr As of now, when the service starts the server, how does it work? I understood how sinatra works, but i'm still missing the glue between the service you use to run the web server and sinatra intself, how does "rerun" fit into this stack of tools?

from awoo.

from awoo.

@nilesr I have problems with permissions and how the repo has been set up to work with the Makefile :(.

When the service listed in the Makefile runs on its own my connections get rejected by NGINX (which is simply proxying 127.0.0.1:8080) for some reason (nginx errorl log):

If i manually run the following command (which i'm having an hard time understanding):

sudo /usr/bin/env rerun -b -p _watch rackup

the server actually starts and i can reach 127.0.0.1:8080 through nginx:

At this point, i can hit awoo.fieel.space (my domain) and reach the sinatra application, i get an exception though:

I didn't touch the source code yet - at this point i have no idea how i should approach the problem.

I come from a dotnet/angular/react environemnt, that might explain why i'm having an hard time understanding all of this?

from awoo.

from awoo.