Skip to content

Using symbolic links to shadow dist folder into the DNN Skin folder #29

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.

Sign up for GitHub

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

Jump to bottom
Closed
weggetor opened this issue Jun 7, 2018 · 1 comment
Closed

Using symbolic links to shadow dist folder into the DNN Skin folder #29

weggetor opened this issue Jun 7, 2018 · 1 comment
Assignees
@david-poindexter
Labels
question Further information is requested

Comments

@weggetor
Copy link

weggetor commented Jun 7, 2018

Would be a good idea to use symbolic links to "shadow" the dist folder of the skin project into the DNN skin folder. Otherwise these files needed to be copied after each build to test the changes!
@david-poindexter david-poindexter self-assigned this Jun 8, 2018
@david-poindexter david-poindexter added the question Further information is requested label Jun 8, 2018
@david-poindexter
Copy link
Member

david-poindexter commented Jun 8, 2018 •
edited
Loading

Great question @weggetor! Most people use mklink to shadow the entire nvQuickTheme clone directory during development. Combing that with the gulp watch command makes for a nice workflow - just refresh page and see the latest theme file changes in action. For those that do not know about mklink, SEE HERE. Another helpful link is HERE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@david-poindexter david-poindexter

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@david-poindexter @weggetor