Bug 37802

Summary: Setup Koha Aliases (or virtual directory)
Product: Koha Reporter: Aditya Sethi <adifbbk1>
Component: REST APIAssignee: Bugs List <koha-bugs>
Status: CLOSED INVALID QA Contact: Testopia <testopia>
Severity: normal    
Priority: P3 CC: dcook, tomascohen
Version: 23.11   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Aditya Sethi 2024-09-02 07:23:42 UTC
Hi

I do not have access to create subdomains for koha, instead I have been provided to use virtual directory "/library" to the VM. 

The url https://example.com has another application hosted and the DNS is pointing to that VM. 

The VM that has Koha installed has access to host https://example.com/library. So, even if we change koha-shared-intranet.conf and point aliases to /library, the website opens as expected without loading CSS. And all hyperlinks are pointing to https://example.com/cgi-bin or https://example.com/intranet-tmpl, which the Koha VM do not have the access to. And, due to restrictions, I am not allowed to create additional subdomains specifically for Koha. 

What should I do? Is there any script to reinstall Koha with aliased paths?
Comment 1 Katrin Fischer 2024-09-02 07:32:41 UTC
Hi, Bugzilla should be used only for bugfixes and enhancement requests. As yours is a support/installation question, please use one of our free support channels (mailing lists and chat mostly) instead. 

See: https://koha-community.org/support/community-support/

This has the additional advantage of many more people reading your questions that might be able to help.
Comment 2 David Cook 2024-09-03 01:50:27 UTC
(In reply to Aditya from comment #0)
> What should I do? Is there any script to reinstall Koha with aliased paths?

I can answer this one here. 

It's impossible.

Koha has hard-coded to be served from the root path. You cannot serve it from "/library". It's an unfortunate limitation, but one that would require a prohibitive amount of work to fix.
Comment 3 Katrin Fischer 2024-09-03 07:15:19 UTC
Maybe if you can't use sub-domains using different ports for staff and OPAC is an option for you.
Comment 4 David Cook 2024-09-04 05:39:24 UTC
(In reply to Katrin Fischer from comment #3)
> Maybe if you can't use sub-domains using different ports for staff and OPAC
> is an option for you.

Agreed. That's really the only other option I'd say.