The node shebang is:

&lt;!-- language: lang-sh --&gt;

    #!/usr/bin/env node

Not all systems place node in the same location, its possible that you have the location incorrectly. This will find them all.

[Source](http://dailyjs.com/2012/03/01/unix-node-arguments/)

[Also](https://stackoverflow.com/questions/10696222/how-to-make-javascript-support-shebang)

I am migrating a `UIViewController` class to train a bit with Swift. I am successfully using Objective-C code via the bridging header but I have the need of importing a constants file that contains `#define` directives.

I have seen in [Using Swift with Cocoa and Objective-C][1] (Simple macros) the following:

&gt; **Simple Macros**
&gt;
&gt; Where you typically used the `#define` directive to define a primitive constant in C and Objective-C, in Swift you use a global constant instead. For example, the constant definition `#define FADE_ANIMATION_DURATION 0.35` can be better expressed in Swift with `let FADE_ANIMATION_DURATION = 0.35`. Because simple constant-like macros map directly to Swift global variables, the compiler automatically imports simple macros defined in C and Objective-C source files.

So, it seems it&#39;s possible. I have imported the file containing my constants into the bridging header, but I have no visibility from my `.swift` file, cannot be resolved.

What should I do to make my constants visible to Swift?

**UPDATE:**

It seems working with `NSString` constants, but not with booleans:

    #define kSTRING_CONSTANT @&quot;a_string_constant&quot; // resolved from swift
    #define kBOOL_CONSTANT YES // unresolved from swift

  [1]: https://developer.apple.com/library/prerelease/ios/documentation/swift/conceptual/buildingcocoaapps/BuildingCocoaApps.pdf

How to use a Objective-C #define from Swift

How can I get the Device Token for remote notification in iOS 8?
I used the method `didRegisterForRemoteNotificationsWithDeviceToken` in `AppDelegate` in iOS &lt; 8, and it returned the device token. But in iOS 8, it does not.

Remote Notification iOS 8

My node installation is at:

`/usr/local/bin/node`

and I&#39;ve added the shebang:

`#!/usr/local/bin/node`

to the top of the file and given my node app file the permissions 755, but when I try to run:

`&gt; ./my-app`

I get the old:

`-bash: ./my-app: No such file or directory`

What am I doing wrong?

node and shebang : help executing via command line

My node installation is at:
<code>/usr/local/bin/node</code>
and I've added the shebang:
<code>#!/usr/local/bin/node</code>
to the top of the file and given my node app file the permissions 755, but when I try to run:
<code>> ./my-app</code>
I get the old:
<code>-bash: ./my-app: No such file or directory</code>
What am I doing wrong?

Following the upgrade to Express 4, and the removal of app.router, I&#39;m struggling to get middleware to execute after routes execute.

e.g. the following code correctly responds with &quot;hello&quot;, but never calls the configured middleware

    var express = require( &quot;express&quot; )();
    
    express.get( &quot;/&quot;, function( req, res ) {
    
    	res.send( &quot;hello&quot; );
    
    } );
    express.use( function( req, res, next ) {
    
    	console.log( &quot;world&quot; );
        next();
    
    } );
    
    express.listen( 8888 );

CLARIFICATION:

the following code shows &quot;before&quot; on the console, but not &quot;after&quot;:

    var express = require( &quot;express&quot; )();
    
    express.use( function( req, res, next ) {
    
    	console.log( &quot;before&quot; );
    	next();
    
    } );
    express.get( &quot;/&quot;, function( req, res ) {
    
    	res.send( &quot;hello&quot; );
    
    } );
    express.use( function( req, res, next ) {
    
    	console.log( &quot;after&quot; );
    	next();
    
    } );
    
    express.listen( 8888 );

Node Express 4 middleware after routes

After [yesterday&#39;s news of Shocker][1], it seems like apps inside a Docker container should not be run as root.  I tried to update my `Dockerfile` to create an app user however changing permissions on app files (while still root) doesn&#39;t seem to work.  I&#39;m guessing this is because some LXC permission is not being granted to the root user maybe?

Here&#39;s my Dockerfile:

    # Node.js app Docker file

    FROM dockerfile/nodejs
    MAINTAINER Thom Nichols &quot;thom@thomnichols.org&quot;

    RUN useradd -ms /bin/bash node

    ADD . /data
    # This next line doesn&#39;t seem to have any effect:
    RUN chown -R node /data 

    ENV HOME /home/node
    USER node

    RUN cd /data &amp;&amp; npm install

    EXPOSE 8888

    WORKDIR /data

    CMD [&quot;npm&quot;, &quot;start&quot;]


Pretty straightforward, but when I `ls -l` everything is still owned by root:

    [ node@ed7ae33e76e1:/data {docker-nonroot-user} ]$ ls -l /data
    total 64K
    -rw-r--r--  1 root root  383 Jun 18 20:32 Dockerfile
    -rw-r--r--  1 root root  862 Jun 18 16:23 Gruntfile.js
    -rw-r--r--  1 root root 1.2K Jun 18 15:48 README.md
    drwxr-xr-x  4 root root 4.0K May 30 14:24 assets/
    -rw-r--r--  1 root root  416 Jun  3 14:22 bower.json
    -rw-r--r--  1 root root  930 May 30 01:50 config.js
    drwxr-xr-x  4 root root 4.0K Jun 18 16:08 lib/
    drwxr-xr-x 42 root root 4.0K Jun 18 16:04 node_modules/
    -rw-r--r--  1 root root 2.0K Jun 18 16:04 package.json
    -rw-r--r--  1 root root  118 May 30 18:35 server.js
    drwxr-xr-x  3 root root 4.0K May 30 02:17 static/
    drwxr-xr-x  3 root root 4.0K Jun 18 20:13 test/
    drwxr-xr-x  3 root root 4.0K Jun  3 17:38 views/


---

[My updated dockerfile works great][2] thanks to @creak&#39;s clarification of how volumes work.  Once the initial files are `chown`ed, `npm install` is run as the non-root user.  And thanks to a `postinstall` hook, npm runs `bower install &amp;&amp; grunt assets` which takes care of the remaining install steps and avoids any need to `npm install -g` any node cli tools like bower, grunt or coffeescript.

  [1]: https://news.ycombinator.com/item?id=7909622
  [2]: https://gist.github.com/thom-nic/5e561e800cbc0f71555c

Running app inside Docker as non-root user

I am using express 4.0 and I&#39;m aware that body parser has been taken out of the express core, I am using the recommended replacement, however I am getting 

`body-parser deprecated bodyParser: use individual json/urlencoded middlewares server.js:15:12
body-parser deprecated urlencoded: explicitly specify &quot;extended: true&quot; for extended parsing node_modules/body-parser/index.js:74:29`

Where do I find this supposed middlewares? or should I not be getting this error?

    var express 	= require(&#39;express&#39;);
	var server 		= express();
	var bodyParser 	= require(&#39;body-parser&#39;);
	var mongoose 	= require(&#39;mongoose&#39;);
	var passport	= require(&#39;./config/passport&#39;);
	var routes		= require(&#39;./routes&#39;);

	mongoose.connect(&#39;mongodb://localhost/myapp&#39;, function(err) {
		if(err) throw err;
	});

	server.set(&#39;view engine&#39;, &#39;jade&#39;);
	server.set(&#39;views&#39;, __dirname + &#39;/views&#39;);

	server.use(bodyParser()); 
	server.use(passport.initialize());

	// Application Level Routes
	routes(server, passport);

	server.use(express.static(__dirname + &#39;/public&#39;));

	server.listen(3000);


bodyParser is deprecated express 4

NOTE: I have tried other solution given [here][1] but it didn&#39;t work

A newbie with NodeJs. I am trying to follow AngularJS pro and got stuck with setting up NodeJs server. According to book, I installed nodejs and then installed connect package using
npm install connect

then downloaded angularjs in folder next to nodejs folder. Then wrote server.js file to connect to server. Here is the content of the file:

        var connect = require(&#39;connect&#39;);
    connect.createServer(connect.static(&quot;../angularjs&quot;)).listen( 5000);


  When I run this server.js file using: 

    node server.js

I get following error:

     function app(req, res, next){ app.handle(req, res, next); }
     merge(app, proto);
     merge(app, EventEmitter.prototype);
     app.route = &#39;/&#39;;
     app.stack = [];
     return app;
     has no method &#39;static&#39;
       at Object.&lt;anonymous&gt; (C:\web\nodejs\server.js:2:36)
       at Module._compile (module.js:456:26)
       at Object.Module._extensions..js (module.js:474:10)
       at Module.load (module.js:356:32)
       at Function.Module._load (module.js:312:12)
       at Function.Module.runMain (module.js:497:10)
       at startup (node.js:119:16)
       at node.js:906:3
    
    
  [1]: https://stackoverflow.com/questions/23978734/node-connect-issue-object-function-createserver-has-no-method-static

Any ideas guys?
Thanks.


nodejs connect cannot find static

I&#39;m trying to select only a specific field with

    exports.someValue = function(req, res, next) {
        //query with mongoose
        var query = dbSchemas.SomeValue.find({}).select(&#39;name&#39;);

        query.exec(function (err, someValue) {
            if (err) return next(err);
            res.send(someValue);
        });
    };

But in my json response i&#39;m receiving also the _id, my document schema only has two fiels, _id and name

    [{&quot;_id&quot;:70672,&quot;name&quot;:&quot;SOME VALUE 1&quot;},{&quot;_id&quot;:71327,&quot;name&quot;:&quot;SOME VALUE 2&quot;}]

Why???


Mongoose, Select a specific field with find

I&#39;m on Ubuntu 14.04 and I&#39;ve been trying all possible methods to install Laravel to no avail. Error messages everything I try. I&#39;m now trying the first method in the quickstart documentation, that is, via Laravel Installer, but it says to &quot;Make sure to place the `~/.composer/vendor/bin` directory in your `PATH` so the Laravel executable is found when you run the Laravel command in your terminal.&quot; so my question is, how do I do that? This may be a simple question but I&#39;m really frustrated and would appreciate any help.

How to place the ~/.composer/vendor/bin directory in your PATH?

If I do a 

    res.sendfile(&#39;public/index1.html&#39;); 

then I get a server console warning 

&gt; express deprecated `res.sendfile`: Use `res.sendFile` instead

 but it works fine on the client side.

But when I change it to 

    res.sendFile(&#39;public/index1.html&#39;);

I get an error 

&gt; TypeError: path must be absolute or specify root to `res.sendFile`

 and `index1.html` is not rendered.

I am unable to figure out what the absolute path is. I have `public` directory at the same level as `server.js`. I am doing the `res.sendFile` from with `server.js`. I have also declared `app.use(express.static(path.join(__dirname, &#39;public&#39;)));`

Adding my directory structure:

	/Users/sj/test/
	....app/
	........models/
	....public/
	........index1.html

What is the absolute path to be specified here ? 

I&#39;m using Express 4.x.

res.sendFile absolute path

I have a path which looks like

    /First/Second/Third/Fourth/Fifth

and I would like to remove the `First` from it, thus obtaining

    Second/Third/Fourth/Fifth

The only idea I could come up with is to use recursively `os.path.split` but this does not seem optimal. Is there a better solution?

Removing the first folder in a path

This should be the easiest problem on earth, but even after extensive searching and tinkering, I&#39;m still in deep trouble with finding a &quot;correct&quot; way to lay a directory structure and manage to run pytest etc correctly.

Let&#39;s say my I have a program called apple.

	|- README.md
	|- apple
	|   |-- __init__.py
	|   |-- apple.py
	| - tests
	|   |-- test_everything.py

The apple.py contains some functions, for examples sake let&#39;s call one `eat()`. And the `test_everything.py` file contains some tests like `assert eat()==&quot;foobar&quot;`. So good so easy, but then the fun begins:

- What about the `__init__.py` in the apple directory... correct? Empty or what should be inside?
- Is it best practice to call `py.test` from the root directory? Or `py.test tests`?
- So many projects have a `__init__.py` in their test directory, but that&#39;s explicitly said to be wrong in the py.test documentation. So why god why
- What comes at the top of the `test_everything.py` file: an `import apple` or `from apple import *`? or something else entirely
- Do you call the functions then by `eat()` or `apple.eat()`?
- Some even recommend manipulating `os.path.dirname` in python

This should be easy, but I&#39;ve seen every combination of the above, not even speaking about tox and the myriad of other tools. Yet with the slightest error, you get thrown some `ImportError: No module named &#39;apple&#39;` or some other funky error. 

What is the &quot;right&quot; way? The advice and the existing code on github etc follows extremely different conventions. For a medium-experienced coder, this should be much easier.

Python project directory structure / pytest trouble

I am having difficulty in importing a local go file into another go file.

My project structure is like something below

    -samplego
    --pkg
    --src
    ---github.com
    ----xxxx
    -----a.go
    -----b.go
    --bin

I am trying to import a.go inside b.go. I tried the following,

    import &quot;a&quot;
    import &quot;github.com/xxxx/a&quot;

None of these worked..I understand I have to meddle up with GOPATH but I couldn&#39;t get it right. Presently my GOPATH is pointing to samplego(/workspace/samplego).I get the below error

    cannot find package &quot;a&quot; in any of:
    /usr/local/go/src/pkg/a (from $GOROOT)
    /workspace/samplego/src/a (from $GOPATH)

Also, how does GOPATH work when these source files are imported into another project/module? Would the local imports be an issue then? What is the best practice in this case - is it to have just one go file in module(with associated tests)? 



importing go files in same folder

I had seen this line `#!/usr/bin/env node` at the beginning of some examples in `nodejs` and I had googled without finding any topic that could answer the reason for that line.

The nature of the words makes search it not that easy.

I&#39;d read some `javascript` and `nodejs` books recently and I didn&#39;t remember seeing it in any of them. 

If you want an example, you could see the `RabbitMQ` official [tutorial][1], they have it in almost all of their examples, here is one of them:

    #!/usr/bin/env node
    
    var amqp = require(&#39;amqplib/callback_api&#39;);
    
    amqp.connect(&#39;amqp://localhost&#39;, function(err, conn) {
      conn.createChannel(function(err, ch) {
        var ex = &#39;logs&#39;;
        var msg = process.argv.slice(2).join(&#39; &#39;) || &#39;Hello World!&#39;;
    
        ch.assertExchange(ex, &#39;fanout&#39;, {durable: false});
        ch.publish(ex, &#39;&#39;, new Buffer(msg));
        console.log(&quot; [x] Sent %s&quot;, msg);
      });
    
      setTimeout(function() { conn.close(); process.exit(0) }, 500);
    });

Could someone explain me what is the meaning of this line?

What is the difference if I put or remove this line? In what cases do I need it?

  [1]: https://www.rabbitmq.com/tutorials/tutorial-three-javascript.html

What exactly does &quot;/usr/bin/env node&quot; do at the beginning of node files?

I know shebang line like this: 

    #!/bin/sh
but I found out I can also use shebang line like this: 

    #!/usr/bin/env python3
This confuses me, can someone explain to me how Linux will process this one? 


Content Type	Original Author	Original Content on Stackoverflow
Question	asking	View Question on Stackoverflow
Solution 1 - node.js	secretformula	View Answer on Stackoverflow

node and shebang : help executing via command line

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Remote Notification iOS 8

How to use a Objective-C #define from Swift

Attributions