Telling Mailman/Hyperkitty where sass is
Hi all,
Another issue that's cropped up when I am trying to run Mailman 3 on apache. I've downloaded and installed Mailman core, Django, Postorius & Hyperkitty. I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However when I run the site from apache it's not finding sass.
Specifically I'm getting errors like: FilterError at /accounts/login/ /bin/sh: sass: command not found
I triple checked that sass is installed which sass /Applications/MAMP/Library/bin/sass
/Applications/MAMP/Library/bin/ is in $PATH when I checked that and I was thinking that it maybe wasn't getting to python properly. However pprint(sys.path) contains the same items whether I start the site from the dev server or apache.
Any pointers would be appreciated.
-Erin
On Wed, 9 Aug 2017 17:12:35 -0700 Erin Justice <galaxyjustice@gmail.com> wrote:
Hi all,
Another issue that's cropped up when I am trying to run Mailman 3 on apache. I've downloaded and installed Mailman core, Django, Postorius & Hyperkitty. I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However when I run the site from apache it's not finding sass.
Specifically I'm getting errors like: FilterError at /accounts/login/ /bin/sh: sass: command not found
I triple checked that sass is installed which sass /Applications/MAMP/Library/bin/sass
/Applications/MAMP/Library/bin/ is in $PATH when I checked that and I was thinking that it maybe wasn't getting to python properly. However pprint(sys.path) contains the same items whether I start the site from the dev server or apache.
You change the command to be executed when the compressor is called in your Django's configuration file which in your case should be at
mailman-suite/mailman-suite_project/settings.pySee here https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/s...
Instead of just sass or sassc command, you can change that to reflect the
full path of the binary and it should work.
Hope that is helpful!
-- thanks, Abhilash Raj
As this pops up relatively often how about removing the dependency on sass completely? It's only needed for hyperkitty, and I don't quite get why we don't just compile and minify js and css files during a release (or every commit that changes the files - don't think it happens too often). Interface devs will probably already have everything installed. It would also make life easier for packagers, as we would drop at least three dependencies (sassc, django-compressor, django-appconfig)
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 10-Aug-17 02:50, Simon HANNA wrote:
As this pops up relatively often how about removing the dependency on sass completely? It's only needed for hyperkitty, and I don't quite get why we don't just compile and minify js and css files during a release (or every commit that changes the files - don't think it happens too often). Interface devs will probably already have everything installed. It would also make life easier for packagers, as we would drop at least three dependencies (sassc, django-compressor, django-appconfig)
+3
Anything to make an install simpler!
However, you may want to have a 'devel' or 'customize' kit, however, for the css. I could certainly see where people would want to provide their own branding; in that case they would need to know how to compile/minify. Perhaps a stand-alone script for that (which would have the extra dependencies, but could be a separate install package).
participants (4)
-
Abhilash Raj -
Erin Justice -
Simon HANNA -
tlhackque