Skip to content
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

Relative path issue #1

Closed
tythorsen opened this issue Feb 7, 2015 · 1 comment
Closed

Relative path issue #1

tythorsen opened this issue Feb 7, 2015 · 1 comment
Labels

Comments

@tythorsen
Copy link
Owner

h1. Issue Description

Splitting out planning-poker into a separate repo has resulted in an issue with relative paths given the current project setup. On local, the root directory is the planning-poker director while in production the root directory is thorsent.github.io. I.E. paths such as /scripts/* in local need to be /planning-poker/scripts/* in production

h2. Possible Resolutions

I think the easiest fix would be to keep the paths coded appropriately for production, and have grunt copy the necessary files into a /planning-poker/ directory on local that is ignored by git.

@tythorsen
Copy link
Owner Author

So the problem was using absolute paths. Converting them to relative paths fixed it. I.E. /scripts/.js should just omit the leading slash to become "scripts/.js.

Fixed as of commit 0e077a7.

Closing Issue.

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

No branches or pull requests

1 participant