Hi, Thinking deeply about this I wonder if the problem would by "how to process it on-the-fly".
If execute "lessc file.less" LESS works properly, but the problem is I can't base my solution on a save-to-disk solution because it would cause a kind of race-condition on high load. So I need that LESS processing happens on-the-fly. Any tip would be appreciated? Ronan Em quinta-feira, 20 de junho de 2013 15h00min36s UTC-3, Ronan Lucio escreveu: > > Hi All, > > I need to deliver dynamic css content. In short, I need this: > > <link href="/css/site.css?color=111111" rel="stylesheet" type="text/css"> > > where site.css has unprocessed less code. > > > So I installed Node.js+LESS on server-side. > The follow line works fine: > > $ lessc testless.less > > > But I still didn't figure out how should I configure the server to answer > these http requests. > > 1) What is the best option: apache or node.js+express? (I have an apache > webserver already installed, but that is no problem starting a Node.js > webserver on another port) > 2) How should I configure my server and application to achieve this? > > Thanks > Ronan > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
