Hannah Wolfe ErisDS

Most linux distros have a package manager, see the Node.js guide for details on installing node via various package managers or alternatively it is possible to download the .tar.gz archive from http://nodejs.org
Double check that you have Node and npm installed and that you have the right version, by typing node -v and npm -v into a terminal window and comparing with the blue box above.

Install Ghost

Grab the latest version of Ghost from Ghost.org:

$ curl -L https://github.com/TryGhost/Ghost/releases/download/0.11.12/Ghost-0.11.12.zip -o ghost.zip
Unzip Ghost into the folder /var/www/ghost (recommended install location):

Demo of generating a JWT and authenticating with Ghost's Admin API.

Demo of generating a JWT and authenticating with Ghost's Admin API.

To set it up:

copy gulp-config.json.example to gulp-config.json
enter the blog admin url, no trailing slash, e.g. https://myblog.ghost.io
grab the client secret for the frontend from the source of any page of the blog
enter the email address & password you use to login to the blog (must be administrator-level)

To deploy:

Highlights

[New] A brand new editor based on Mobiledoc, using SimpleMDE & Markdown-it to recreate full markdown support
[New] Casper 2.0 - an overhaul that makes use of all of Ghost's best theme features
[New] Improved default posts, explaning more features and a welcome tour to guide users around
[New] Nightshift mode light text on a dark background for editing at night, available in labs
[New] Config with nconf, logging with bunyan, and debug output using debug.
[Improved] Publish menu which brings scheduling front and centre, instead of it being an after thought
[Improved] Simplified content screen with filtering makes it easier to find
[Improved] The importer has had a complete overhaul, is now more robust and outputs much, much better error & warning messages when things do go awry

This assumes that you have already installed:

After that, running install-ghost.yml will:

	# NOTE on remote naming:
	# I clone the original (upstream) repo first, which means that's set to "origin"
	# and then if I want to use my own fork, I clone it using `git remote add fork [email protected]:ErisDS/...
	# which means my fork is called... "fork".
	# I always found origin and fork made more sense as names...
	# this is why we have support for a GHOST_UPSTREAM env var in all of our older tooling like gstenv,
	# as it's personal taste between that and upstream & origin,


	[alias]

	<html>

	<head>
	<script src="https://unpkg.com/@tryghost/content-api@latest/umd/content-api.min.js"></script>
	<script src="https://unpkg.com/@tryghost/[email protected]/umd/helpers.min.js"></script>
	<script>
	const api = new GhostContentAPI({
	url: 'https://demo.ghost.io',
	key: '22444f78447824223cefc48062',
	version: "v3"

	<html>

	<head>
	<script src="https://unpkg.com/@tryghost/content-api@latest/umd/content-api.min.js"></script>
	<script>
	const api = new GhostContentAPI({
	url: 'https://demo.ghost.io',
	key: '22444f78447824223cefc48062',
	version: "v3"
	});

	#!/usr/bin/env node
	const prettyCLI = require('@tryghost/pretty-cli');
	const slimer = require('@tryghost/slimer');
	const extensions = require('../extensions');

	// Require internal commands
	prettyCLI.commandDirectory('../commands');

	slimer
	.loadCommands()