Published: Sat, 21 May 2011 / Last Updated: Sat, 18 Jun 2011
First things first, you need to get your basic environment right, the pre-requisites are:
Ok - good to go?
Go to where you want to run calipso from (e.g. /var/www).
$ git clone git://github.com/cliftonc/calipso.git Initialized empty Git repository in /var/www/tmp/calipso/.git/ remote: Counting objects: 724, done. remote: Compressing objects: 100% (440/440), done. remote: Total 724 (delta 298), reused 520 (delta 216) Receiving objects: 100% (724/724), 640.07 KiB | 476 KiB/s, done. Resolving deltas: 100% (298/298), done. $ cd calipso/ $ ls app-cluster.js conf lib media package.json README test utils app.js docs.html Makefile modules pids support themes
Calipso depends on a number of other libraries that are available through NPM (the Node Package Manager). If all of these dependencies aren't installed, you will get lots of errors when attempting to run Calipso
$ npm install npm info it worked if it ends with ok npm info using email@example.com npm info using firstname.lastname@example.org npm info link /var/www/tmp/calipso ... <
> ... npm ok
On Ubuntu, if you have installed mongodb (sudo apt-get install mongodb), you can make sure it is running by:
$ status mongodb mongodb start/running, process 2588
If mongo is not running and won't start (sudo start mongodb), some times if it doesn't shut down gracefully you can get a lock left open, and you need to delete the lock file (sudo rm /var/lib/mongod/mongodb.lock) before starting it.
Now the first test, try to run it!
$ node app _ _ ___ __ _| (_)_ __ ___ ___ / __|/ _` | | | '_ \/ __|/ _ \ | (__| (_| | | | |_) \__ \ (_) | \___|\__,_|_|_| .__/|___/\___/ |_| Logging enabled: Console Calipso server listening on port: 3000
Now, if you browse to:
You should see the home screen, along with a message that the site has been configured with a default Administrative user and password. You should login with this, and then change it immediately (you can do this from the Admin users profile page).
Ok - you're now up and running, you should be able to login, and once logged in begin to navigate the content creation and administration screens.
There is now an install script that you can try, simply run:
This should install the dependencies via NPM, and do a few quick checks to see if you are up and running.