-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin assets+url rewriting #484
Plugin assets+url rewriting #484
Conversation
|
||
Since handling static assets, such as images, Javascript and CSS files of plugins, | ||
through the Dispatcher is incredibly inefficient, it is very recommended to symlink | ||
them for production. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be a good idea to give an example of how to do that here. An example of symlinking might be the easiest.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
you could also symlink
|
@@ -72,241 +72,6 @@ get as a result of using the wrong delimiter, and it makes your | |||
code more portable. | |||
|
|||
|
|||
Apache and mod\_rewrite (and .htaccess) | |||
======================================= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be a good idea to leave a link to the new page/file as there will be existing installs linking here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your point but it feels a bit like dragging unneeded load.
That's the downside of not having a dedicated version of the docs for old releases. (i don't want to downplay the upsides)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicating the content isn't a good idea. Just a link would be fine 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't thinking of duplicating content, especially since I just removed some ;-)
Put the title back and and created a link "moved to..."
…ient Moved url rewriting to a separate file Added a section about what if you can't use url rewriting Improved core config section about App.baseUrl Added section in deployment about improving performance due to symlinking Removed parts of the blog tutorial (duplicated content) Fixed toctrees and a typo deleted two .DS_Store files Fixed broken commits
Hope you like this somewhat bigger patch for the docs.
I built the docs on my machine but I was experiencing a strange behaviour in the sidebar tree. I've added a new file to installation and now links to this new file appear on at least two places where they shouldn't (and aren't)!