In iTerm2, in the menu bar go to Scripts > Manage > New Python Script
Select Basic. Select Long-Running Daemon
Give the script a decent name (I chose auto_dark_mode.py
)
Save and open the script in your editor of choice.
//how to execute: node verify.js <path file that you want to verify> <certificate path> <hash generate by sign.js> | |
//output: true if files are equal, false otherwise. | |
var crypto = require('crypto'); | |
var fs = require('fs'); | |
var args = process.argv.slice(2); | |
var fileName = args[0]; | |
var certPath = args[1]; | |
var sig = args[2]; |
//how to execute: node sign.js <path file> <path private key> | |
//output: signature of file | |
var crypto = require('crypto'); | |
var fs = require('fs'); | |
var args = process.argv.slice(2); | |
var fileName = args[0]; | |
var keyPath = args[1]; | |
//openssl genrsa -out key.pem 1024 |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
Node.js core does its best to treat every platform equally. Even if most Node developers use OS X day to day, some use Windows, and most everyone deploys to Linux or Solaris. So it's important to keep your code portable between platforms, whether you're writing a library or an application.
Predictably, most cross-platform issues come from Windows. Things just work differently there! But if you're careful, and follow some simple best practices, your code can run just as well on Windows systems.
On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation
// Flag Enumerations in JavaScript | |
// =============================== | |
// Flag enums | |
// ---------- | |
// Values must increment by powers of 2 | |
var SEASONS = { | |
Spring : 1, | |
Summer : 2, |