Skip to content
This repository has been archived by the owner on Feb 10, 2023. It is now read-only.

get rid of /website/root #10

Open
flibustenet opened this issue Sep 3, 2014 · 5 comments
Open

get rid of /website/root #10

flibustenet opened this issue Sep 3, 2014 · 5 comments

Comments

@flibustenet
Copy link
Contributor

Looking for a clean way to get rid of /website/root

@adroullier
Copy link
Contributor

Basically both 'website' and 'root' are part of the application. The whole setup is made up of a few more parts like '/userdb/', '/website/editor', /website/en/' (once translations are supported), and so on.
So, from that point of view it doesn't make sense to change the routing.

However I have added a fix to support the virtual hosting root urls in combination with proxy servers.

@flibustenet
Copy link
Contributor Author

I understand the idea of /userdb /website... My point is to can switch existing website to nive without loosing the current urls. Users already said me about this. I'm afraid it will be a show-stopper for new users.

@flibustenet
Copy link
Contributor Author

I don't understand why, but it seems that x_vhm_root doesn't work more since the lasts versions... I try to see when and why.

@adroullier
Copy link
Contributor

I have always used proxy servers like nginx or apache to handle website migrations. Old urls are rewritten in the web in the servers configuration and redirected. This way you can point search engines to the new url by returning a 301 status (moved permanently).
And you are not forced to rebuild the url structure 1:1, for examlpe if the websites contents change.

@flibustenet
Copy link
Contributor Author

I forgot to say that x_vhm_root work and let me remove website/root, (the problem was of the possibility to change "root" part of the url).
Thought, i continue to think that it could be very convenient to can do it by a simple option on the app side.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants