search

eudicots / Cactus

Static site generator for designers. Uses Python and Django templates.
BSD 3-Clause "New" or "Revised" License
3.46k stars 314 forks source link

Cactus won't serve files #197

Open cjrider opened 8 years ago

cjrider commented 8 years ago

Hi. Cactus updated itself this morning, now it seems broken.

Reports this error when trying to serve files:

Traceback (most recent call last):
File "/Users/cjjr/Applications/Cactus.app/Contents/Resources/python/run.py", line 32, in <module>
from cactus import cli
File "/Users/cjjr/Applications/Cactus.app/Contents/Resources/python/CactusSource/cactus/cli.py", line 9, in <module>
import colorama
ImportError: No module named colorama
cjrider commented 8 years ago

Should say, I'm on Yosemite 10.10.5, running cactus 1.1.18 (the mac GUI, not the naked CLI).

federicocalvo commented 8 years ago

Hi, me too. ImportError: No module named colorama.

With OSX 10.11 El Capitan

ghost commented 8 years ago

Hi, I am on Yosemite 10.10.5 and updated cactus as well and getting the "ImportError: No module named colorama.

screen shot 2015-10-13 at 10 44 50 am

danthorpe commented 8 years ago

On El Capitain, Cactus updated to 1.1.18 (436) and I had these problems. I fixed it by doing this...

$ pip install colorama
$ pip install django-markwhat

If these commands both error due to "Permission denied" just type sudo !! to tell the captain you really mean it.

And now Cactus serves locally. There is still an issue of projects disappearing from the list, #191 mentions this.

funkyboy commented 8 years ago

For sake of completeness I tried @danthorpe's solution on 10.10.5 but it doesn't work :)

funkyboy commented 8 years ago

In case you wanna go back to previous version this link is still available: http://update.cactusformac.com/static/downloads/Cactus-1.1.15.zip

ghost commented 8 years ago

@funkyboy I went back to the previous version but now getting a CertificateError. Have you seen this before?

screen shot 2015-10-14 at 6 04 25 am

funkyboy commented 8 years ago

@mhefferon sorry no, I don't use the deploy functionality :(

crashpodel commented 8 years ago

I am getting the same error :(

L-A commented 8 years ago

@mhefferon @dilbertoid This is Boto failing because it is now too (?) strict on certificate checks – any bucket with a period in its name fails. Boto is the library Cactus uses to manage its communication with S3.

To solve this ,create a .boto file in your home (~) directory. It's your local Boto configuration file. It needs these two lines:

[s3]
calling_format = boto.s3.connection.OrdinaryCallingFormat

Afterwards, deployment from Cactus.app should work as expected. Hopefully, this is temporary.

Gist for reference: https://gist.github.com/L-A/480a1e8b46fdb4fd6537