FullJS application server is a JavaScript runtime built on Chrome’s V8 JavaScript engine. The application server is multi-threaded and uses event-driven, non-blocking I/O model that makes it lightweight and efficient for running separate isolates of javascript applications.

Application structure

FullJS applications has some required files and the rest is up to the developer:
| – client.js -> Client side source code
| – client.html -> GUI design for the main application window
| – client.css -> Stylesheet for the main window
| – server.jss -> Server side source  code

Applications’ path

Web applications created by FullJS developer are stored at the folder: /var/www/html and can be access by a browser (after it is started) at http://[yourip]/[endpoint]/

Server configuration

The main configuration file for fulljs application server can be found at /etc/fulljs/fulljs.conf

Starting and Stopping FullJS server

To start the FullJS server use the systemd’s start command. If you are running as a non-root user, you will have to use sudo since this will affect the state of the operating system:

sudo systemctl start fulljs.service

To stop a running fulljs server, you can use the stop command

sudo systemctl stop fulljs.service

Enabling and Disabling Services

The above commands are useful for starting or stopping FullJS during the current session. To tell systemd to start FullJS server automatically at boot, you must enable it.

To start the server at boot, use the enable command:

sudo systemctl enable fulljs.service

To disable the service from starting automatically, you can type:

sudo systemctl disable fulljs.service

Keep in mind that enabling a service does not start it in the current session. If you wish to start the service and enable it at boot, you will have to issue both the start and enable commands.

Checking FullJS server status

To check the status of the server on your system, you can use the status command:

systemctl status fulljs.service

This will provide you with the server state.