Multihost doesn’t serve camelCase’d directories

[motleydev]

My folder structure looks like this:

-HarpJs
--theMan
--theMyth
--theLegend
#Hold your judgment, it was late, there may have been whisky involved.

when I run harp multihost HarpJs/ from the parent folder I get the listing of the apps at URL http://harp.nu:9000 but when I click on one it returns Cannot find project with url of http://thelegend.harp.nu:9000/

Thanks for any help!

[kennethormandy]

Hey, thanks for opening an issue!

When you say the parent folder, do you mean the parent of HarpJs? If you’re in the HarpJs/ directory, you should only need to run harp multihost. Right now, I think you’re trying to run it on HarpJs/HarpJs which doesn’t exist, hence the error.

There’s more details in the multihost docs, but let me know if you feel like something is missing and I’ll update them.

[motleydev]

Thanks for the reply. I’m the parent of HarpJs - so, for example, “Development>HarpJs>theMan,theMyth,theLegend

For the sake of testing, I did try and run harp multihost in the HarpJs dir and I get the same errors.

• Jesse

On Mar 18, 2014, at 7:55 PM, Kenneth Ormandy notifications@github.com wrote:

Hey, thanks for opening an issue!

When you say the parent folder, do you mean the parent of HarpJs? If you’re in the HarpJs/ directory, you should only need to run harp multihost. Right now, I think you’re trying to run it on HarpJs/HarpJs which doesn’t exist, hence the error.

There’s more details in the multihost docs, but let me know if you feel like something is missing and I’ll update them.

— Reply to this email directly or view it on GitHub.

[kennethormandy]

Hm, okay. Might be a bug then. Can you share what platform and version of Node you’re running? Thanks!

[mfrohberg]

I have had a similar issue when trying to run harp multihost over SSH from within in a sandbox. My fix was to manually edit my etc/hosts file by prepending the sites as subdomains. Not sure if that's your issue but that fix "worked" for me in development.

[kennethormandy]

@mfrohberg That sounds like it might be out of the area I can be very helpful, but we’d definitely like to hear more about it if it was a problem for you. Is that something you would have expected to work, or is it the nature of what you were trying to do? Thanks for commenting.

[motleydev]

So, about that platform… You mean like OS? I’m running it locally on OSX Mavericks with Node 102.6.

• Jesse

On Mar 19, 2014, at 7:00 AM, Kenneth Ormandy notifications@github.com wrote:

Hm, okay. Might be a bug then. Can you share what platform and version of Node you’re running? Thanks!

— Reply to this email directly or view it on GitHub.

[kennethormandy]

Sorry, yeah, that’s what I meant. Thanks, there shouldn’t be anything odd about that so I’ll see if I can replicate it.

[motleydev]

no, I just need to learn the lingo. I'm a marketing guy who's hacking my way through front end developer land.

I may have stumbled across an important fact, I tried replicating the issue without the camelcase naming convention and it works fine. Seems to be an issue with resolving an foo.harp.nu:9000 to a Foo directory?

[kennethormandy]

@motleydev That helps, thank you! We’re definitely hoping to help people newer to front end development, so if there’s other areas where Harp has been unclear, we’d definitely like to hear about it.

[motleydev]

will do - I did change the existing directory structure to all lowercase - theman, themyth, thelegend and it works just fine - so it seems very connected to a case sensitivity.

[kennethormandy]

Just to for future reference, this is still an issue.