How vince demo server is deployed

[gernest]

I have been seeing a lot of questions regarding deploying vince. It is beyond me to support how vince is deployed.

Here are some details about how I deploy the demo site

• system: debian
• installation: I download the debian package from release page and run dpkg -i vince***.deb
• update /etc/vince/vince.conf with vince command args. For my case it looks like this

ARGS="serve --data=/var/lib/vince-data --adminName gernest --adminPassword ***** --autoTLS=true --acmeDomain=demo.vinceanalytics.com --acmeEmail=**** --listen=:443 --domains=vinceanalytics.com --url=https://demo.vinceanalytics.com"

reload systemd

systemd daemon-reload

This is pretty much it, with automatic tls.

I hope this helps.

[EvilBMP]

How about running vince behind a reverse proxy in a virtual "sub-path" of the main domain?

I tried to run vince with --url https://example.com/vince, but that doesn't seem to work.

[gernest]

--url is mainly for links generated with vince to point to the domain you are hosting. Forwarding with reverse proxy should work. Unfortunately I can only help with vince issues and not reverse proxy configurations.

[EvilBMP]

Well, assets are included with leading slash / - e.g. /public/css/app.css. Therefore, only the root domain is requested without the "sub-path".

[gernest]

I see, that is a valid point indeed. Since the root domain hits the reverse proxy maybe you can do a url rewrite for those absolute paths ?