search

cliftonc / calipso

Calipso is a simple NodeJS content management system based on Express, Connect & Mongoose.
calip.so
1.71k stars 307 forks source link

404s when running not from source #233

Open laurelnaiad opened 11 years ago

laurelnaiad commented 11 years ago

I'm getting 404 errors in my heroku logs. The following urls show 404:

It should be noted that the behavior of the app is the same as if I had created a site using ./bin/calipso site /my/path -- and maybe this is a clue:

When I run from the calipso source, aloha works and I get yellow borders around stuff (I'm not in love with the yellow borders, but they're there).

When I run from a site created with ./bin/calipso site those yellow borders are absent and I get no aloha. Same with running on heroku.

So it seems like there may be something going on when one either pushes calipso source via git or they create a site from the source, that messes up a path. Is this possible?

Incidentally, I wondered about these lines in package.json:

    "subdomain": "calipso",
    "domains": [
        "calip.so",
        "www.calip.so"
    ]

What is their purpose? Obviously a bit of a shot in the dark, but could they have something to do with the 404s?

In any case, I'm headed in a direction that won't involve aloha -- so not a support request but a heads up.

richtera commented 11 years ago

Is aloha turned on? It's possible that the site doesn't behave right without aloha Andy

Sent from my iPhone

On Sep 28, 2013, at 4:43 PM, Stu Salsbury notifications@github.com wrote:

I'm getting 404 errors in my heroku logs. The following urls show 404:

It should be noted that the behavior of the app is the same as if I had created a site using ./bin/calipso site /my/path -- and maybe this is a clue:

When I run from the calipso source, aloha works and I get yellow borders around stuff (I'm not in love with the yellow borders, but they're there).

When I run from a site created with ./bin/calipso site those yellow borders are absent and I get no aloha. Same with running on heroku.

So it seems like there may be something going on when one either pushes calipso source via git or they create a site from the source, that messes up a path. Is this possible?

Incidentally, I wondered about these lines in package.json:

"subdomain": "calipso",
"domains": [
    "calip.so",
    "www.calip.so"
]

What is their purpose? Obviously a bit of a shot in the dark, but could they have something to do with the 404s?

In any case, I'm headed in a direction that won't involve aloha -- so not a support request but a heads up.

— Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/233 .

laurelnaiad commented 11 years ago

This happens when aloha is turned on. When it's off, no errors. Put simply, aloha fails with those 404s when I don't run from my cloned directory -- it gets turned on and doesn't work.

richtera commented 11 years ago

Hmmm. Is the static module on? Hmm interesting Andy

Sent from my iPhone

On Sep 28, 2013, at 5:10 PM, Stu Salsbury notifications@github.com wrote:

This happens when aloha is turned on. When it's off, no errors. Put simply, aloha fails with those 404s when I don't run from my cloned directory -- it gets turned on and doesn't work.

— Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/233#issuecomment-25308556 .

laurelnaiad commented 11 years ago

I had all included modules enabled. I've since disabled aloha. I just tried enabling aloha and dsabling static and it doesn't seem to make a different w/respect to the 404s.

richtera commented 11 years ago

I'll check tomorrow Andy

Sent from my iPhone

On Sep 28, 2013, at 5:43 PM, Stu Salsbury notifications@github.com wrote:

I had all included modules enabled. I've since disabled aloha. I just tried enabling aloha and dsabling static and it doesn't seem to make a different w/respect to the 404s.

— Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/233#issuecomment-25309091 .

laurelnaiad commented 11 years ago

np -- as I mentioned, I'm not planning to use aloha but wanted to pass on the info. LMK if you want me to try anything.

richtera commented 10 years ago

BTW: The domain and subdomain references are for the nodejitsu deployment. I wish they didn't use the package.json file for their settings, but since I deploy the package from the same folder I had to merge the nodejitsu settings.