Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

lessc not working on initial installation #6

Closed
se1exin opened this issue May 19, 2015 · 6 comments
Closed

lessc not working on initial installation #6

se1exin opened this issue May 19, 2015 · 6 comments

Comments

@se1exin
Copy link

se1exin commented May 19, 2015

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.

@kaedroho
Copy link

Yep, it looks like we're installing node v0.10.0 which is ancient. Thanks!

I'll update the box.

@kaedroho
Copy link

Could you check that the box in the "rewrite" branch works for you?

#7

@se1exin
Copy link
Author

se1exin commented May 19, 2015

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:

==> default: createdb: could not connect to database template1: FATAL: Peer authentication failed for user "postgres"

The second was the very last part of provisioning which junked the virtualenv - see this gist for the full error list.

@se1exin
Copy link
Author

se1exin commented May 19, 2015

Additionally, when connecting to the box via vagrant ssh, these errors also occurred

@kaedroho
Copy link

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.

@se1exin
Copy link
Author

se1exin commented Mar 1, 2017

Closing to clean up old still-open issues

@se1exin se1exin closed this as completed Mar 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants