dev/prod tools for node.js
Get flash to fully experience Pearltrees
node.js IDEs
Autolint watches your files for jslint-errors. DRY up your js-files, freeing them of all those linting config comments. Gather all your linting preferences in one place per project. The configuration file is no longer a json -file, but a proper node module. Add module.exports = to the start of the file and rename to autolint.js to upgrade. Autolint no longer runs without a config file.
magnars/autolint - GitHub
Node-dev is a development tool for Node.js that automatically restarts the node process when a script is modified. With node-dev you don't have to manually specify which files should be watched nor do you have to deal with ignore lists for files that should be excluded. This is done using a thin wrapper script that hooks into the require() function as well as into several methods of the VM module to determine which files need to be monitored. This does not only work for .js files, but also for .json or .node or .coffee files or any other custom extension that has been added to require.extensions . Another great benefit of this zero-config approach is that it doesn't cause any unnecessary restarts when for example client-side only scripts are modified.
fgnass/node-dev - GitHub
Nodules is an asynchronous module loader for Node that provides URL/HTTP-based module ids, module hot-reloading, and package based module mapping. Nodules implements the CommonJS package.json mappings proposal and automatically analyzes modules references and downloads any dependencies on first access prior to executing modules.
kriszyp's nodules at master - GitHub
Deploying Node.js With Upstart and Monit - How To Node - NodeJS
If I heard two "Yes"'s, then you are in the some boat as me, and being in that boat feels really really vulnerable. Like the kind of vulnerable you would feel if you were trapped in a cage with lions.
Translation(s) : none Debian was converted to order the boot sequence using the LSB fields in the header of each init.d script. This has removed several bugs in the former boot sequence, and now makes it easier to keep the sequence correct. Advantages Did you ever need to insert a init.d scripts Y before init.d scripts Z and after init.d script X, where both Z and X is started using boot sequence number 20 (as in 20X and 20Z)? Adding your script as 20Y would not cut it, because you need Z to start before X.
LSBInitScripts/DependencyBasedBoot - Debian Wiki
[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ next ] Restricting services so that they can only be accessed from a given place can be done by restricting access to them at the kernel (i.e. firewall) level, configure them to listen only on a given interface (some services might not provide this feature) or using some other methods, for example the Linux vserver patch (for 2.4.16) can be used to force processes to use only one interface. Regarding the services running from inetd ( telnet , ftp , finger , pop3 ...) it is worth noting that inetd can be configured so that services only listen on a given interface (using service@ip syntax) but that's an undocumented feature. One of its substitutes, the xinetd meta-daemon includes a bind option just for this matter. See xinetd.conf(5) .
Securing Debian Manual - Securing services running on your system
Your Debian / Ubuntu Linux box security depends upon access to system services (one of many aspects).
Ubuntu / Debian Linux: Services Configuration Tool to Start / Stop System Services
Run Node.js as a Service on Ubuntu
Our servers run Ubuntu's latest: Karmic Koala, which packs a pretty decent version of upstart .Most programs can be easily packaged using debhelper; especially when using dh_make to make an initial debian/ tree. dh_make requires the directory containing the source code to be named - , After picking the right package class, an 'original' directory is created in ../ - .orig/ . dh_make proceeds to make the debian/ directory, and fills it with control files, and some example packaging scripts (these are postfixed with ' .ex '). These files can be customized or removed later on. Most of the 'important' debhelper utilities will be placed in the correct positions in the debian/rules file, commented out.
