Using a subdomain (e.g. bungeeweb.domain.tld) instead of a port.

[ethanwaite]

Using a subdomain (e.g. bungeeweb.domain.tld) instead of a port.

[lenovouser]

This is actually possible:

NGINX:

server {
    listen 80;

    server_name bungeeweb.domain.tld;

    location / {
        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;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:<BungeeWebPort>/;
        proxy_redirect off;
    }
}

With Apache2 it is a little more difficult, I am searching for an easy solution right now.

[Arzte]

@Dead-i I would like to see something like this, I think this would be kinda cool, plus you can always call on recon when you separate the webserver from the plugin.

[EthanWaite]

Thanks for the suggestion. :)

Allowing people to host the files could be a good option to achieve this, yes. However, my main concern with this is that, with the current setup, BungeeWeb's standalone webserver could never go away completely, even with the files separated.

This is because any query sends an Ajax HTTP request to the webserver. For example, when logs are retrieved or refreshed, it will send a request to 127.0.0.1:8080/api/getlogs. For searching a player, the plugin will send a request to 127.0.0.1:8080/api/getplayers. If we remove the webserver completely, there would be nothing to serve these requests.

Would still keeping the barebones of the webserver (the API) be a problem? Perhaps a good way to get around this would be to use web sockets...

[EthanWaite]

However, it is still possible to run BungeeWeb on a subdomain anyway with the current setup, provided you have an IP address spare. You could theoretically run BungeeWeb on port 80 on a spare IP address, and then point the subdomain of your choice to this IP address.

[Arzte]

be cool also if there was a way to get something like mything.bw.domainexstension if your going to add support for this.

[lenovouser]

Well, I dont understand your problem here right now, BungeeWeb is running perfectly fine with this NGINX configuration, and why you would want to remove the internal webserver from BungeeWeb? This is just proxying the results from BungeeWeb to the subdomain.

[EthanWaite]

@Apfeluser I was more responding to @TheDoctorsLife's message than you, sorry, as he mentioned:

you can always call on recon when you separate the webserver from the plugin.

I've always intended for BungeeWeb to have an integrated webserver as it does now, as it really simplifies the installation process. However, I've had quite a few requests to separate the webserver, and I was curious what you all thought about this.

Practically though, it doesn't seem to make much sense to separate them, as you said.

Anyway, it's great that you've got a nginx configuration working, and I'll definitely be playing around with this later! =)

Thanks

[Arzte]

When I said that I wasn't meaning to get rid of the webserver but to offer the ability to do so.