Ghost is an open source, professional publishing platform built on a modern Node.js technology stack — designed for teams who need power, flexibility and performance. Every day Ghost powers some of the most-read stories on the internet, serving hundreds of millions of requests across tens of thousands of sites.

Architecture

At its core Ghost is a self-consuming, RESTful JSON API with decoupled admin client and front-end. Ghost comes with a default Handlebars.js frontend for getting a site running as quickly as possible, as well as detailed documentation for working with the API directly or using provided SDKs and headless front-end framework integrations.For editors, Ghost has the rich editor which every writer wants, but under the hood it delivers far more power than you would expect. All content is stored in a standardised JSON-based document storage format called MobileDoc, which includes support for extensible rich media objects called Cards.

Because Ghost is completely open source, built as a JSON API, has webhooks, and gives you full control over the front-end: It essentially integrates with absolutely everything. Browse a large directory of integrations with instructions, or build any manner of custom integration yourself by writing a little JavaScript and Markup to do whatever you want.

Data & Storage

Ghost ships with the Bookshelf.js ORM layer by default allowing for a range of databases to be used. Currently SQLite3 is the supported default in development while MySQL is recommended for production. Other databases are available, and compatible, but not supported by the core team.

Additionally, while Ghost uses local file storage by default it’s also possible to use custom storage adapters to make your filesystem completely external. There are fairly wide range of pre-made storage adapters for Ghost already available for use.

Example Customers

Hitting the right balance of needs has led Ghost to be used in production by organisations including Apple, Sky News, DuckDuckGo, Mozilla, OpenAI, Square, CloudFlare, Tinder, the Bitcoin Foundation and many more.

Try Ghost

Ghost is completely free an open source, released under the MIT license, stewarded by a non-profit foundation. It can be downloaded and self-hosted just about anywhere, or spun up in a few moments using the Ghost(Pro) managed PaaS, which comes with a 14 day free trial.

marketplace.ghost.org

cd /var/www/ghost/content/themes/

apt-get update && apt-get install git-core -y

git clone https://github.com/polygonix/N-Coded.git

chown -R ghost:ghost N-Coded

service ghost restart

your_domain_name/ghost/settings/general

your_domain_name/ghost/settings

sudo service ghost start

sudo service ghost stop

sudo service ghost restart

sudo service nginx restart

sudo service ghost stop

scp root@your_ghost_IP_address:/var/www/ghost/content/data/ghost.db .

ssh -n root@your_ghost_IP_address 'tar zcvf - -C /var/www/ghost/content/themes .' | cat - > ghost_themes.tar.gz

ssh -n root@your_ghost_IP_address 'tar zcvf - -C /var/www/ghost/content/images .' | cat - > ghost_images.tar.gz

sudo service ghost start

domain_name/ghost/debug

http://ghost.org/zip/ghost-latest.zip

sudo apt-get update
sudo apt-get install build-essential

service ghost stop

cd /var/www/

wget url_to_ghost_download

rm -rf ghost/core

unzip -uo ghost*.zip -d ghost

chown -R ghost:ghost ghost/*

cd /var/www/ghost
npm install --production

service ghost start

nano /var/www/ghost/config.js

var path = require('path'),
    config;

config = {
    development: {
        . . .
        . . .
    },

    production: {
        . . .
        . . .
    },

    otherEnvironments: {
        . . .
        . . .
    }
}

production: {

},

production: {
    . . .
    . . .
},
production: {
    . . .
    . . .
},

production: {
    . . .
    . . .
},
temporary: {
    . . .
    . . .
},

nano /etc/init.d/ghost

export NODE_ENV=production

export NODE_ENV=temporary

service ghost restart

service nginx restart

nano /etc/init.d/ghost

export NODE_ENV=production

service ghost restart

your email choice SMTP

nano /var/www/ghost/config.js

. . .
production: {
    url: 'http://example.com',
    mail: {},
    database: {
    . . .

mail: {
    transport: 'SMTP',
    options: {
        service: '',
        auth: {
            user: '',
            pass: ''
        }
    }
},

mail: {
    transport: 'SMTP',
    options: {
        service: 'service_name',
        auth: {
            user: 'SMTP_login_name',
            pass: 'SMTP_password'
        }
    }
},

service ghost restart

How To Install and Configure Ghost on CentOS 7

Prerequisites

To complete this tutorial, you will need:

• One 1GB CentOS 7 server set up by following the Initial Server Setup with CentOS 7 guide, including a sudo non-root user.
• Node.js installed using the EPEL repository method explained in the tutorial: How To Install Node.js on a CentOS 7 server.
• Nginx installed on your server, as shown in How To Install Nginx on CentOS 7.

Step 1 — Installing Ghost

First, we need to install Ghost. We’ll place Ghost in the /var/www/ghost directory, which is the recommended installation location.

Download the latest version of Ghost from Ghost’s GitHub repository using wget:wget https://ghost.org/zip/ghost-latest.zip

wget https://ghost.org/zip/ghost-latest.zip:

• sudo yum update -y
• sudo yum install unzip -y

The -y flag in the preceding commands updates and installs packages automatically without asking for a confirmation from the user.

Once unzip is installed, unzip the downloaded package to the /var/www/ghost directory. First, create the /var/www folder, then unzip the file:

• sudo mkdir /var/www
• sudo unzip -d /var/www/ghost ghost-latest.zip

Switch to the /var/www/ghost/ directory:

• cd /var/www/ghost/

Then install the Ghost dependencies, but only the ones needed for production. This skips any dependencies which are only needed by people who develop Ghost.

• sudo npm install –production

Ghost is installed once this process completes, but we need to set up Ghost before we can start it.

Step 2 — Configuring Ghost

Ghost uses a configuration file located at /var/www/ghost/config.js. This file doesn’t exist out of the box, but the Ghost installation includes the file config.example.js, which we’ll use as a starting point.

Copy the example configuration file to /var/www/ghost/config.js. We’ll copy the file instead of moving it so that we have a copy of the original configuration file in case we need to revert your changes.

• sudo cp config.example.js config.js

Open the file for editing:

• sudo vi config.js

We have to change the URL that Ghost uses. If we don’t, the links on the blog will take visitors to my-ghost-blog.com. Change the value of the url field to your domain name, or to your server’s IP address if you don’t want to use a domain right now.

...

config = {
    // ### Production
    // When running Ghost in the wild, use the production environment
    // Configure your URL and mail settings here
    production: {
        url: 'http://your_domain_or_ip_address',
        mail: {},
...

The url value must be in the form of a URL, like http://example.com or http://11.11.11.11. If this value is not formatted correctly, Ghost will not start.

Ghost can function without the mail settings; they’re only necessary if you need to support password recovery for Ghost users. We’ll skip configuring this setting in this tutorial.

You can customize Ghost further by following the configuration details at the official site.

Save the file and exit the editor.

While still in the /var/www/ghost directory, start Ghost with the following command:

• sudo npm start –production

The output should be similar to the following:

> ghost@0.11.7 start /var/www/ghost
> node index

WARNING: Ghost is attempting to use a direct method to send email.
It is recommended that you explicitly configure an email service.
Help and documentation can be found at http://support.ghost.org/mail.

Migrations: Creating tables...
...

Ghost is running in production...
Your blog is now available on http://your_domain_or_ip_address
Ctrl+C to shut down

Ghost is listening on port 2368, and it’s not listening on the public network interface, so you won’t be able to access it directly. Let’s set up Nginx in front of Ghost.

Step 3 — Configuring Nginx to Proxy Requests to Ghost

The next step is to set up Nginx to serve our Ghost blog. This will allow connections on port 80 to connect through to the port that Ghost is running on, so people can access your Ghost blog without adding the :2368 to the end of the address. It also adds a layer of indirection and sets you up to scale out your blog if it grows.

If Ghost is still running in your terminal, press CTRL+C to shut down the Ghost instance before you continue.

Now let’s configure Nginx. Change to the /etc/nginx directory first:

• cd /etc/nginx/

If you installed Nginx from the CentOS EPEL repository as shown in the prerequisite tutorial, you will not have the sites-available and sites-enabled directories, which are used to manage web site configurations. Let’s create them:

• sudo mkdir sites-available
• sudo mkdir sites-enabled

Next, create a new file in /etc/nginx/sites-available/ called ghost:

• sudo vi /etc/nginx/sites-available/ghost

Place the following configuration in the file and change your_domain_or_ip_address to your domain name, or your servers IP address if you don’t have a domain:

server {
    listen 80;
    server_name your_domain_or_ip_address;
    location / {
    proxy_set_header HOST $host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass         http://127.0.0.1:2368;
    }
}

This basic configuration sends all requests for this server to the Ghost blog running on port 2368, and it sets the appropriate HTTP headers so that when you look at your Ghost logs, you’ll see the original IP address of your visitors. You can learn more about this configuration in Understanding Nginx HTTP Proxying, Load Balancing, Buffering, and Caching.

Save the file, exit the editor, and enable this configuration by creating a symlink for this file in the /etc/nginx/sites-enabled directory:

• sudo ln -s /etc/nginx/sites-available/ghost /etc/nginx/sites-enabled/ghost

Nginx won’t use this new configuration until we modify the default Nginx configuration file and tell it to include the configuration files in the sites-enabled folder. In addition, we have to disable the default site. Open up the nginx.conf file in your editor:

• sudo vi nginx.conf

Include the following line inside the http block to include the configuration files in the sites-enabled folder:

http {
...
    # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
    # for more information.
    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;

Then completely comment out the server block found inside the http block:

...

    # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
    # for more information.
    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;


#    server {
#       listen       80 default_server;
#       listen       [::]:80 default_server;
#       server_name  _;
#       root         /usr/share/nginx/html;
#
#       # Load configuration files for the default server block.
#       include /etc/nginx/default.d/*.conf;
#
#       location / {
#       }
#
#       error_page 404 /404.html;
#           location = /40x.html {
#       }
#
#       error_page 500 502 503 504 /50x.html;
#           location = /50x.html {
#       }
...
...

Save the file and exit the editor. Test the configuration to ensure there are no issues:

• sudo nginx -t

You’ll see the following output if everything is correct:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

If you see any errors, fix them and retest the configuration.

With a working configuration file, restart Nginx to apply the changes:

• sudo systemctl restart nginx

Before we start Ghost again, let’s create a new user account to run Ghost.

Step 4 – Running Ghost as a Separate User

To improve security, we’ll run Ghost under a separate user account. This user will only have access to the /var/www/ghost directory and its home folder. This way, if Ghost gets compromised, you minimize the potential damage to your system.

Create a new ghost user with the following command:

• sudo adduser –shell /bin/bash ghost

Then make this new user the owner of the /var/www/ghost directory:

• sudo chown -R ghost:ghost /var/www/ghost/

Now let’s make sure this user can run Ghost. Log in as the ghost user:

• sudo su – ghost

Now start Ghost under this user and ensure it runs:

• cd /var/www/ghost
• npm start –production

You should be able to access your blog at http://your_domain_or_ip_address. Nginx will send requests to your Ghost instance.Things are working great, but let’s make sure Ghost continues to run well into the future.

Step 5 — Running Ghost as a System Service

Currently, Ghost is running in our terminal. If we log off, our blog will shut down. Let’s get Ghost running in the background and make sure it restarts when the system restarts. To do this, we’ll create a systemd unit file that specifies how systemd should manage Ghost. Press CTRL+C to stop Ghost, and log out of the ghost user account by pressing CTRL+D.

Create a new file to hold the definition of the systemd unit file:

• sudo vi /etc/systemd/system/ghost.service

Add the following configuration to the file, which defines the service’s name, the group and user for the service, and information on how it should start:

[Unit]
Description=Ghost
After=network.target

[Service]
Type=simple

WorkingDirectory=/var/www/ghost
User=ghost
Group=ghost

ExecStart=/usr/bin/npm start --production
ExecStop=/usr/bin/npm stop --production
Restart=always
SyslogIdentifier=Ghost

[Install]
WantedBy=multi-user.target

Save the file and exit the editor. Then enable and start the service:

• sudo systemctl enable ghost.service
• sudo sytemctl start ghost.service

Once again, visit http://your_domain_or_ip_address and you’ll see your blog.

your_domain_name/ghost

DD MMM YY
[08 Oct 13]

-Ghost is an Open Source application which allows you to write and publish your own blog, giving you the tools to make it easy and even fun to do. It’s simple, elegant and designed so that you can spend less time making your blog work and more time blogging.Ghost is owned by Ghost (https://ghost.org/) and they own all related trademarks and IP rights for this software.

Ghost on Cloud runs on Amazon Web Services (AWS) and Azure and Ghost on Cloud is designed to cater to the needs of small and large taxi, limo and ground transportation companies and everything in between.Cognosys provides hardened images of Ghost on all public cloud i.e. AWS marketplace and Azure.

Secured Ghost on CentOS 7.3

Ghost Features

 A familiar editing environment enables a seamless authoring experience that allows you to focus on creating content. Paragraph

Robust tagging functionality gives you fine-grained control over any type of category, section, format or flow to adapt to your needs – including custom homepages, URL structures, and multi-language content.

Multiples roles for authors, editors, and administrators. Invite your whole team to collaborate, with dedicated public user profiles for everyone.

Queue up your full editorial calendar ahead of time and set your posts to go live like clockwork. Ghost remembers to publish at the right time so you don’t have to.

Proper SEO built in directly, with semantic markup, permalinks, XML sitemaps, canonical tags and automatic metadata with manual overrides.

With integrated AMP support, your site will rank higher and load in a fraction of a second from Google mobile search results.

Every post published renders beautifully all over the web, with rich meta tags for Facebook Open Graph, Twitter Cards and Schema.org.

 A straightforward JSON importer and exporter keeps your data infinitely portable, while our CLI tool makes configuring, running and updating Ghost a breeze.

 Self-consuming JSON API for all your data.

 Environment, install, updates, backups, optimizations, all taken care of on your behalf!

Isolated applications, SSL by default, firewalls and spam protection. All threats mitigated by Ghost team whenever needed.

 All customer data is continuously backed up to an off-site location, ensuring that you never need to worry about losing content.

Ghost’s native apps provide all the beauty and power of Ghost, right on your device. It also means that you can easily switch between multiple sites on the fly. Available for Mac, PC, Linux, and Android.

-Major Features Of Ghost

Customize it Completely. It’s Yours : You can write themes for it so your blog can have its own design. You can write plugins for it to add your own functionality. You can host it on your laptop, or you can host it on a public server. The code is open and so is the MIT license. No restrictions.

It Works Where You Work : We know that inspiration can strike anywhere, not just when you’re sitting behind a computer. So, Ghost works where you work. Ghost is a fully responsive web application that works on all devices. Not just moderating comments or token functionality. The whole thing.

An editor for writers : A Markdown based editing environment allows for fast formatting and a seamless authoring experience which places the focus entirely on the content being created. A live side-by-side allows you to always see how the post will render.

Simple content management : All your content is available in an easily searchable archive which can be scanned through at speed.

• Installation Instructions For Ubuntu

Installation Instructions For  Ubuntu

Note: How to find PublicDNS in AWS

Step 1) SSH Connection: To connect to the deployed instance, Please follow Instructions to Connect to Ubuntu instance on AWS Cloud

1) Download Putty.

2) Connect to virtual machine using following SSH credentials :

• Hostname: PublicDNS  / IP of machine
• Port : 22

Username: To connect to the operating system, use SSH and the username is ubuntu.
Password: Please Click here to know how to get password .

Step 2) Database Login Details:

• MYSQL Username : root
• MYSQL Password : Passw@rd123

Note: Please change the password immediately after the first login.

Step 3) Application URL: Access the application via a browser at http://PublicDNS/Ghost

Step 4) Other Information:

1. Default installation path: will be in your web root folder “opt/Ghost”

2. Default ports:

• Linux Machines:  SSH Port – 22
• Http: 80 or 8080
• Https: 443
• Mysql ports: By default these are not open on Public Endpoints. Internally Mysql server: 3306

Configure custom inbound and outbound rules using this link

AWS Step by Step Screenshots

Stack Name-This will be your Current stack.

Choose Software Pricing

Choose your Version

Choose your EC2 Instance Type

Choose Your Key Pair

Choose your Region

Choose your Security Group

Change VPC Settings

Installation Instructions For Ubuntu

Installation Instructions for Ubuntu

Step 1) VM Creation:

1. Click the Launch on Compute Engine button to choose the hardware and network settings.
2. You can see at this page, an overview of Cognosys Image as well as estimated cost of running the instance.
3. In the settings page, you can choose the number of CPUs and amount of RAM, the disk size and type etc.

Step 2) SSH Connection:To initialize the DB Server connect to the deployed instance, Please follow Instructions to Connect to Ubuntu instance on Google Cloud

Step 3) Database Login Details:

The below screen appears after successful deployment of the image.

For local MySQL root password, please use the temporary password generated automatically during image creation as shown above.

i) Please connect to Remote Desktop as given in step 2 to ensure stack is properly configured and DB is initialized.
ii) You can use MySQL server instance as localhost, username root and password as shown above.

If you have closed the deployment page you can also get the MySQL root password from VM Details  “Custom metadata” Section.

Step 3) Application URL: Access the application via a browser at http://PublicDNS/Ghost

Note: –Ghost is running on port 2368. A proxy has been used to divert from 80 to 2368. Open http://YourIP to access Ghost site

Use below commands to manage the service

• service ghost stop
• service ghost start
• service ghost status

Step 4) Other Information:

1. Default installation path: will be in your web root folder “opt/Ghost”

2. Default ports:

• Linux Machines:  SSH Port – 22
• Http: 80 or 8080
• Https: 443
• Mysql ports: By default these are not open on Public Endpoints. Internally Mysql server: 3306

Secured Ghost on CentOS 7.3