Must the polr webpage be at the base of the domain?

[ifuchs]

I have a domain which has a webpage and I would like to use this domain for shortened urls but keep the existing index.html. Is this possible? That is, say the domain is my.domain, must the polr webpage be at that address or could it be anywhere else and still create shortened urls beginning with my.domain?

[ifuchs]

Can anyone please answer this or at least make an informed guess?

[steveroot]

Some guesses; A) use a subdomain, eg: polr.my.domain B) use redirects in nginx/Apache I think harder. You'd have to know all things you don't want polr to process (index.html, stuff/about.php, newstuff/video.mp4) and direct them first. Then pass anything bthat doesn't match to polr. It's been a long while since I used polr and I can't recall how it was setup with nginx. I think subdomain is easiest way sent from my mobile

…

On Tue, 3 Nov 2020, 18:05 ifuchs, ***@***.***> wrote: Can anyone please answer this or at least make an informed guess? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#573 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABVV7ZYUUMY5H5MEREJZKLSOBA55ANCNFSM4TG5WX4Q> .

[ifuchs]

Subdomain is fine but does that mean all shortened urls will have to use the subdomain or can the polr ui page be accessed via the subdomain while shortened urls use the (shorter) root domain?

…

On Nov 5, 2020, at 12:20 PM, Steve Root ***@***.***> wrote: Some guesses; A) use a subdomain, eg: polr.my.domain B) use redirects in nginx/Apache I think harder. You'd have to know all things you don't want polr to process (index.html, stuff/about.php, newstuff/video.mp4) and direct them first. Then pass anything bthat doesn't match to polr. It's been a long while since I used polr and I can't recall how it was setup with nginx. I think subdomain is easiest way sent from my mobile On Tue, 3 Nov 2020, 18:05 ifuchs, ***@***.***> wrote: > Can anyone please answer this or at least make an informed guess? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#573 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AABVV7ZYUUMY5H5MEREJZKLSOBA55ANCNFSM4TG5WX4Q> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#573 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLDPSBNDNJR7HLAFY4FLUTSOLNGHANCNFSM4TG5WX4Q>.

[steveroot]

They'd all use the subdomain. The subdomain can be a single letter, A link would be l.domain.com/short => www.domain.com/some/other/place sent from my mobile

…

On Thu, 5 Nov 2020, 17:47 ifuchs, ***@***.***> wrote: Subdomain is fine but does that mean all shortened urls will have to use the subdomain or can the polr ui page be accessed via the subdomain while shortened urls use the (shorter) root domain? > On Nov 5, 2020, at 12:20 PM, Steve Root ***@***.***> wrote: > > > Some guesses; > A) use a subdomain, eg: polr.my.domain > > B) use redirects in nginx/Apache > I think harder. You'd have to know all things you don't want polr to > process (index.html, stuff/about.php, newstuff/video.mp4) and direct them > first. Then pass anything bthat doesn't match to polr. > > It's been a long while since I used polr and I can't recall how it was > setup with nginx. I think subdomain is easiest way > > sent from my mobile > > On Tue, 3 Nov 2020, 18:05 ifuchs, ***@***.***> wrote: > > > Can anyone please answer this or at least make an informed guess? > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > <#573 (comment)>, or > > unsubscribe > > < https://github.com/notifications/unsubscribe-auth/AABVV7ZYUUMY5H5MEREJZKLSOBA55ANCNFSM4TG5WX4Q > > > . > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub < #573 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABLDPSBNDNJR7HLAFY4FLUTSOLNGHANCNFSM4TG5WX4Q >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#573 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABVV77Q3C7RPJ2ALRB4WTLSOLQKXANCNFSM4TG5WX4Q> .

[ifuchs]

Thanks. I’m looking for a way to use the domain name with no subdomain but keep polr page anywhere else. I gather yourls can do that so perhaps best bet is to use that.

…

On Thu, Nov 5, 2020 at 1:10 PM Steve Root ***@***.***> wrote: They'd all use the subdomain. The subdomain can be a single letter, A link would be l.domain.com/short => www.domain.com/some/other/place sent from my mobile On Thu, 5 Nov 2020, 17:47 ifuchs, ***@***.***> wrote: > Subdomain is fine but does that mean all shortened urls will have to use > the subdomain or can the polr ui page be accessed via the subdomain while > shortened urls use the (shorter) root domain? > > > On Nov 5, 2020, at 12:20 PM, Steve Root ***@***.***> > wrote: > > > > > > Some guesses; > > A) use a subdomain, eg: polr.my.domain > > > > B) use redirects in nginx/Apache > > I think harder. You'd have to know all things you don't want polr to > > process (index.html, stuff/about.php, newstuff/video.mp4) and direct them > > first. Then pass anything bthat doesn't match to polr. > > > > It's been a long while since I used polr and I can't recall how it was > > setup with nginx. I think subdomain is easiest way > > > > sent from my mobile > > > > On Tue, 3 Nov 2020, 18:05 ifuchs, ***@***.***> wrote: > > > > > Can anyone please answer this or at least make an informed guess? > > > > > > — > > > You are receiving this because you are subscribed to this thread. > > > Reply to this email directly, view it on GitHub > > > <#573 (comment) >, > or > > > unsubscribe > > > < > https://github.com/notifications/unsubscribe-auth/AABVV7ZYUUMY5H5MEREJZKLSOBA55ANCNFSM4TG5WX4Q > > > > > . > > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub < > #573 (comment)>, or > unsubscribe < > https://github.com/notifications/unsubscribe-auth/ABLDPSBNDNJR7HLAFY4FLUTSOLNGHANCNFSM4TG5WX4Q > >. > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#573 (comment)>, or > unsubscribe > < https://github.com/notifications/unsubscribe-auth/AABVV77Q3C7RPJ2ALRB4WTLSOLQKXANCNFSM4TG5WX4Q > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#573 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLDPSAH6FEA5FRSIAUCK53SOLTBXANCNFSM4TG5WX4Q> .