-
-
Notifications
You must be signed in to change notification settings - Fork 46
serve does not work with watch #243
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
Comments
I just tried
And it worked using marmite 0.2.5 I also tried to invert the position of arguments and all worked. |
Hi @rochacbruno If I use the same folder like: |
Ohh @neiesc you found a bug, when you use the same folder it enters in an endless loop because the generated site counts as a change. I think we need to address that on Lines 241 to 263 in 4b14084
Make the output folder to be ignored when located in the same folder. |
Uh oh!
There was an error while loading. Please reload this page.
Expected:
marmite --serve --watch <input> <output>
should auto-build on file changes and serve those new filesActual: The default "No Content Found" page is served
When combining
--watch
and--serve
in the same command, the generated site files do not serve properly. I am unable to determine from the debug output why this might be but I've outlined some tests below that seem to indicate that this feature is not working as intended:marmite --serve <input>
-- works as expectedmarmite <input> <input>/site
followed bymarmite --serve <input>
-- No content foundmarmite --watch <input> <output> --serve <input>
-- unexpected argument for the second <input>marmite --watch <input> --serve <output>
-- No content foundmarmite --watch <input> --serve <input>
-- infinite regeneration loopPlease let me know if I can provide any further detail or clarification. I am, admitedly, new to the project so I readily admit I may be using this incorrectly but the use case as described in #34 seems to indicate this is a bug.
The text was updated successfully, but these errors were encountered: