You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As now, it seems Linkace can only be installed at the root of a website: it is not really possible to install it in a subdirectory (example.com/linkace for example), because some elements, such as the CSS, are expected to load from the root:
Describe the solution you'd like
A variable to set prior to install process, for example in the .env file, to specify the base path for the app
Describe alternatives you've considered
Not really relevant. This would be a secondary feature, but still useful for those who do not have a lot of power over their environment (or just do not want to create a whole subdomain for Linkace)
The text was updated successfully, but these errors were encountered:
I am using Apache indeed. I applied what is being said in the article, and in the meantime fixed something on my side that was preventing .htaccess to be read...
Here is what is happening now:
If I do not put the RewriteBase directive, the site goes in an error 500 (the reason being the same than the one in the article)
If I put the correct RewriteBase directive, the installer loads successfully; however, this does not solve the issue about the CSS.
Here is more detail:
(By the way, is there any way to contribute on the documentation? Since I run into several issues while installing, I feel like it would be good if I could mention them somewhere on the install documentation)
I'm trying to get LinkAce to work in a subdirectory too, but using Nginx. Please don't drop support for this feature, even if it may be somewhat niche. You are already using a framework that supports this so LinkAce should not really have to deal with any of this anyways …
Is your feature request related to a problem? Please describe.
As now, it seems Linkace can only be installed at the root of a website: it is not really possible to install it in a subdirectory (
example.com/linkace
for example), because some elements, such as the CSS, are expected to load from the root:Describe the solution you'd like
A variable to set prior to install process, for example in the
.env
file, to specify the base path for the appDescribe alternatives you've considered
Not really relevant. This would be a secondary feature, but still useful for those who do not have a lot of power over their environment (or just do not want to create a whole subdomain for Linkace)
The text was updated successfully, but these errors were encountered: