< Previous Article Next Article >

Working With Files

The Files tree is where you will manage your code and other types of files. You can add, delete, and move both files and directories within your space.

file-tree

Your public directory

In NodeRun, static files such as images, CSS files, and client-side JavaScript files are served out of a directory named public.

When files are placed in public, they are automatically accessible to your application as follows:

  • At runtime, via this URL pattern: noderun.com/run/[owner]/[space]/public/[filename]
  • In the IDE (e.g. in the Visual Designer), via this URL pattern: noderun.com/ide/[owner]/[space]/public/[filename]

Setting your Start File

When you launch a NodeRun application, NodeRun looks for a Start File within your space to execute or serve. Your Start File can be a Node.js script or a static HTML file.

To set a Start File, right-click the desired file and click select Properties. Once, a Start File is set, you will be ready to Launch your application.

launch

Setting an Express route

The default server already configured for each NodeRun space is Express. Express is one of the more popular light-weight web application servers for Node.js. For more information on Express, visit https://expressjs.com.

Since NodeRun is already configured for Express, you don't have to write any code to configure an Express route. Simply, right-click any file, select Properties, and then select Express Route.

You can then specify whether this is your App Start Route or provide a custom HTTP Method and Route Path.

express-route

Creating a Custom Server

If your application is not using the Express server shipped with NodeRun, you should locate your application's main Node.js server file, select Properties, and mark the checkboxes labeled App Start File and Custom Server.

custom-server

To be accessible via NodeRun, your custom application server must listen on port 8081, which you can access dynamically by using process.env.PORT.

Below are some simple custom server examples.

Custom Node.js HTTP Server:

const http = require("http");

http.createServer(function(request, response) {
  response.writeHead(200, {'Content-Type': 'text/plain'});
  response.end('Hello World from a Custom Server!!!!');
}).listen(8081);

Custom Express Server:

const express = require('express');
const app = express();
const port = process.env.PORT || 8081;

app.get('/', (req, res) => res.send('Hello World from Express!'));

app.listen(port, () => console.log(`Example app listening on port ${port}!`));

With custom servers, when you make changes to your server-side code, you must restart the application server. You can do this from the Server menu in the IDE.

Questions?

Have questions about this topic? Ask for help on our NodeRun Discussion Forum.

< Previous Article Next Article >