Changes to generated views to use 'relativeUrlRoot'#594
Open
dimircea wants to merge 2 commits into
Open
Conversation
…t view URLs to use it for being able to run Geddy app under proxies pointing to sub-folders.
Contributor
|
This looks great, but we'll need updates for the other template engines (e.g., Jade, Mustache), before we can merge this to master. |
Contributor
|
Cross reference issue #592 |
Author
|
Ok. I will take care of these changes. One question: how do I enforce "geddy gen app/scaffold" tool(s) to use a specific template engine so I can test these changes ? |
Contributor
|
You can use the -j -H -m and -s options -- it's in the docs for the CLI: http://geddyjs.org/guide#cli_geddy_gen_[command]_[options]_[arguments] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add 'relativeUrlRoot' property to configuration file, allowing to set a relative URL when running Geddy apps behind proxies or as sub-folder of a domain/sub-domain.
Next step is to adapt generated routes for scaffolds.