Closed mwmiller closed 9 years ago
Oh, I don't believe it matters, but in the interest of completeness: this is specifically the result of a request for http://localhost:5005/ddh-intro
Hmm... I'll look into this right now...
@mwmiller I'm unable to reproduce running this:
duckpan publisher --duckduckhack http://duck.co/
and then going to http://localhost:5005/ddh-intro, I'm seeing the docs as expected.
@moollaza Thanks for confirming this for me. I found the problem.
On a tangentially related note, would it be OK for me to update the default URL for duckduckhack to duck.co
? I seem to forget that invocation a lot.
@mwmiller actually I think we still need to keep Port 5005 pointing to duckduckhack.com because we do still have/use that domain. I know in the coming weeks there are plans to redesign it at the very least so it's likely to get used shortly.
My thinking was that we could have port 5006 point to duck.co for the docs, or we could simply make a new duckpan docs
command that does what we want?
My thinking was that we could have port 5006 point to duck.co for the docs, or we could simply make a new duckpan docs command that does what we want
This is almost certainly a better idea. :grin:
I am no longer able to view changes locally with
duckpan publisher
. I had some local changes to the duckpan application, which I thought might be responsible. However, I did aduckpan reinstall
, cleared my publisher cache and still get this same result: