-
Notifications
You must be signed in to change notification settings - Fork 50
lessc not working on initial installation #6
Comments
Yep, it looks like we're installing node v0.10.0 which is ancient. Thanks! I'll update the box. |
Could you check that the box in the "rewrite" branch works for you? |
The initial box build worked fine along with lessc successfully compiling css, however when used in conjunction with vagrant-django-template I received 2 lots of errors, the first halfway through provisioning, being about postgres:
The second was the very last part of provisioning which junked the virtualenv - see this gist for the full error list. |
Additionally, when connecting to the box via vagrant ssh, these errors also occurred |
Thanks, I rebuilt this box on the wagtail base box which has some recent changes that appear to be incompatible with the old template. I'll update that too in a bit. In the mean time, that particular error can be solved by removing the -Upostgres part of all postgresql comments. And also removing the 'USER' setting from the database configuration. |
Closing to clean up old still-open issues |
The default install of lessc on this box produces absolutely no output when running via terminal or when run through django compressor.
After some Google'in I have been able to successfully correct the problem for each box instance I have created locally using these instructions - which essentially just manually removes all node-less binaries and then re-installs node-less via apt-get instead of npm. It would be great if this box was updated to have a working version of lessc pre-installed without the need to do this for every box launched.
Note that I use this box in conjunction with TorchBox's vagrant-django-template repo - so I am not 100% sure if the source of the issue lies with the box or the provisioning script in the template repo.
The text was updated successfully, but these errors were encountered: