Skip to main content

Setting up Ghost-Blogger platform

Ghost blogger platform is very user friendly for creation blogs. Here are the basic steps i used to set it up

Download the ghost blog code for a stable release or clone a github repo.

https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager

ubuntu 13.04 comes shipped with old verion of node.js, so u just need to run
$sudo apt-get install nodejs



update it to be compatible with ghost.

For older version of ubuntu execute the below commands.

sudo apt-get install python g++ make checkinstall
mkdir ~/src && cd $_
wget -N http://nodejs.org/dist/node-latest.tar.gz
tar xzvf node-latest.tar.gz && cd node-v*
./configure
checkinstall #(remove the "v" in front of the version number in the dialog)  --MAKE SURE TO PRESS 3 AND REMOVE V
sudo dpkg -i node_*

installation in progress..after installation..
cd ghost
and then npm start

--npm start was giving errors .

following commands helps to fix some issues.

cd app
#app here is the ghost directory which is downloaded .
rm -rf node_modules
npm cache clean
npm install

Now when i run
$npm install
it works...

> ghost@0.3.2 start /home/bijendra/Documents/ghost-0.3.2
> node index

Ghost is running...
Listening on 127.0.0.1:2368
Url configured as: http://my-ghost-blog.com
Ctrl+C to shut down

application is available at 127.0.0.1:2368,
signup at 127.0.0.1:2368/admin for the new user.

I wanted to setup ghot-blog locally and it should be running in background whenever system is on..

Refer: http://docs.ghost.org/installation/deploy/

To install forever type $ npm install forever -g

i had some issues with directory access so i added sudo before the above command.

The above link can be used to configure the system to run the application as a service.

Comments

Popular posts from this blog

Cannot allocate memory error while computing files - Setup Swap space

ActionView::Template::Error (Cannot allocate memory - nodejs /tmp/execjs20131021-26716-fckzo3.js 2>&1
Nodejs is used to compile javascript at runtime. In RoR applications, this error comes when server is started in production mode which compiles the assets or while running rake assets:precompile.
check for swap space and allocate

Fresh server start after instance degraded

So the issue was, amazon issued an warning regarding the server to be terminated, before i could think of making an backup the instance stopped.

The troubleshoot operations like reboot, stop and start didn't worked.
Simple Steps to start a fresh instance with the previous content on server.