search

stephenlb / nodejuice

Automatic browser refresh on file change or update is what you can call it. NodeJuice is a set of tools which allows you to develop with a push connection to your web browser. JavaScript V8 Seeker Server and Web Server Gateway Interface. nodeJuice Seeker Server works with all other servers including Apache, Passenger, Nginx, Cherokee, and more. A web server isn't required, NodeJuice comes with one in case you forgot yours. It runs on NodeJS; a low level non-blocking network ready process with many capabilities. This is a tool that every web developer needs and has wanted for a very long time. IRC @ #node.js
http://nodejuice.com
Other
78 stars 3 forks source link

Feature request: More command line options and/or user default config. #9

Open adrinux opened 11 years ago

adrinux commented 11 years ago

Having the nodejuice.js config file in with my project files is a bit of a pain with my workflow.

How feasible would it be to have most config options set (optionally) via the command line when starting seeker/sidekick?

Another (not mutually exclusive) possibility would be a command line option to reference a custom nodejuice.js config file, rather than nodejuice just falling back on its default if none is found in the project directory.

Something that could be added easily? Or would it need a libary like commander.js or node-optimist to parse command line options?

stephenlb commented 11 years ago

Hi Adrian,

You have Great ideas. Feel free to make any modifications an submit a pull request.

Cheers! Stephen Blum http://twitter.com/PubNub https://github.com/pubnub/pubnub-api - GitHub www.pubnub.com +1-425-830-6711

On Sep 10, 2012, at 8:36 AM, Adrian Simmons notifications@github.com wrote:

Having the nodejuice.js config file in with my project files is a bit of a pain with my workflow.

How feasible would it be to have most config options set (optionally) via the command line when starting seeker/sidekick?

Another (not mutually exclusive) possibility would be a command line option to reference a custom nodejuice.js config file, rather than nodejuice just falling back on its default if none is found in the project directory.

Something that could be added easily? Or would it need a libary like commander.js or node-optimist to parse command line options?

— Reply to this email directly or view it on GitHub.