Shawn, not sure what you are doing wrong. There are some other asset
management solutions out there, including connect-assets, it's on github.
One thought might be that if it is a platform as a service cloud offering,
then they might not let you write to disk. The less middleware might be
trying to write the compiled CSS to disk.
On Sunday, July 8, 2012 12:36:41 AM UTC-5, Shawn Wildermuth wrote:
>
> Is anyone using Less-Middleware and Express successfully in a cloud
> deployment (I've tried AppHarbor and Azure and getting the same behavior).
> Basically the less-middleware is working except that imports (in the same
> directory as the .less files) fail to load. Not sure if it's related to the
> src being public (my less files are in /public/styles). Locally I am
> testing against node 0.8.0 (not 0.8.1) but I think the Azure and AppHarbor
> versions are 0.6.x. I have tried command-line, through WebStorm (I think
> identical to command-line) and through IISNode (via WebMatrix 2) and all
> work flawlessly...it's only when I deploy to the cloud it gets all messed
> up. Ideas?
>
> ...
> // Configuration
> app.configure(function() {
> app.set('views', __dirname + '/libs/views');
> app.set('view engine', 'jade');
> app.use(require('less-middleware')(
> {
> src: __dirname + '/public',
> compress: false,
> debug: true,
> force: true
> }));
> app.use(express.static(publicFolder));
> app.use(express.bodyParser());
> app.use(express.methodOverride());
> app.use(app.router);
> });
> ...
>
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
