How to Deploy Nodize CMS into Jelastic Cloud

Nodize is an open source lightweight content management system, written in CoffeeScript. It offers such features as live articles’ update (by means of and JQuery), drag&drop uploads and pages sorting, helping to bring your website to a new level. Among other useful capabilities of this CMS you can benefit on, are easy integration of articles into HTML code and auto-generated SEO-friendly URLs. Nodize visual interface is truly simple and comfortable to work with, allowing to put together a website within minutes.

Below, you can find a simple step-by-step instruction on how to install, configure and run Nodize CMS at Jelastic Cloud. So, log in to your Jelastic account let’s go on!

Set Up Environment and Database

1. Click the New environment button on the top dashboard pane. In the appeared frame, switch to the Node.js tab (where NodeJS application server will be chosen automatically as the only available one), select the desired engine version and enable the MySQL node within the SQL database section to the left. nodize 01new wizard 3

Then, state the amount of resources for each layer using cloudlet sliders in the middle section, select the preferred environment region, name your environment (e.g. nodize) and click Create.

2. Once the environment is ready and appears at the dashboard, let’s proceed with DB configurations - namely, you need to create a dedicated database, where your project data will be stored. nodize 02db dash

So, access the MySQL web interface by clicking the Open in browser button next to your database node.

3. Use the credentials you’ve previously received via email to log in and navigate to the Users tab at the top pane. nodize 03db add user 1

Click the Add user link within the New section.

4. Specify the desired User name and Password within the appropriate fields. Tick the Create database with same name and grant all privileges option below and click on Go at the very bottom. nodize 04create user

5. As a result, you’ll see a message informing that your new user with a dedicated database was successfully added. nodize 05success add

Now, we can proceed to the app server configuration.

Deploy and Configure Nodize

Once the database is created, you need to deploy Nodize CMS itself and connect it to this DB.

1. Navigate to Nodize sources at GitHub and click Copy to clipboard next to the project link at the top pane. nodize 06git copy

2. Then, return to the Jelastic dashboard and select the Add project button for the NodeJS app server. nodize 07add proj

3. In order to launch the CMS, paste the URL you’ve just copied to the appropriate field within the Git tab and click Add.

nodize 08add

Wait a bit for all of the required operations to be completed (it will take some time to build and deploy the project).

4. Now, let’s configure the connection between application and database. nodize 09config

Open the configuration tab by clicking the Config icon next to your application server.

5. In the appeared tab, locate the webroot/ROOT/themes/pageone/settings/database.json file and adjust the parameters it comprises with your custom values (indicated with the curly brackets below):

"host" : "{db_ip}",
"port" : 3306,
"database" : "{db_name}",
"user" : "{db_user}",
"password" : "{user_password}",
"logging" : false,
"dialect" : "mysql"


  • {db_ip} - internal IP address of your database

You can find node IP by expanding the Additionally list (gear icon) at the appropriate line.

nodize 10note

  • {db_name} - name of the database you’ve created in the previous section
  • {db_user} - dedicated user for the stated database
  • {user_password} - user’s password

As a result, you should get the similar config:

nodize 11db json 1

Don’t forget to Save the changes with the appropriate button.

6. Next, navigate to the webroot/ROOT/settings/nodize.json file and substitute the default value of the pixlr_callback_server line (approximately at the 32nd line) with a link to your environment. nodize 12nodize json


The required URL can be found right under your environment name at the dashboard.

nodize 13note 1

Save the changes once again.

Start the Application

Finally, when all the preparations are done, let’s start Nodize CMS itself - follow the next steps to perform this:

1. Locate the package.json file within the webroot/ROOT folder and insert the following line into the scripts section (starts approximately at the 41st line):

"start": "cd ~/ROOT/ && coffee",

nodize 14scripts package 1 Save the changes with the appropriate button on the top pane.

Note: Do not miss the comma at the end of the line (unless it’s the last one in the section); otherwise, the script will throw an exception.

2. In order to apply the made changes, Restart your NodeJS app server by clicking the appropriate button. nodize 15restart

3. While this operation is performed, open the node.log file by clicking the Log button next to your app server node and selecting it within the list to the left. Here, you can track the current status of the server initialization process. nodize 16note 6

Wait a while for the Sequelize session store initialized string to appear and you are good to proceed.

Note: Remember the randomly generated admin user’s credentials within the list of output data (circled in the image above), as you’ll subsequently require them for logging into your CMS admin panel.

4. Finally, hit the Open in browser button next to your environment (an empty page should be opened, as you haven’t added anything to your site yet) and append /admin to the end of the URL within the tab address bar. nodize 17login

You’ll see a login frame opened, where you need to specify the admin user credentials you’ve got during the first initialization (within the preceding instruction step). Click the Login button.

Great! Now you can start creating, editing or deleting any content at your site with the help of a simple and powerful Nodize CMS, enjoy!

In case you experience any problems with Nodize CMS deployment or configuration, feel free to appeal to our technical experts’ assistance at Stackoverflow.

What’s next?