Package Details: ghost 0.11.10-1

Git Clone URL: (read-only)
Package Base: ghost
Description: Free, open, simple blogging platform
Upstream URL:
Keywords: nodejs
Licenses: MIT
Submitter: cyang
Maintainer: None
Last Packager: storrgie
Votes: 29
Popularity: 0.198107
First Submitted: 2013-10-15 06:07
Last Updated: 2017-06-20 20:35

Latest Comments

jollanza commented on 2017-12-13 14:18

this was a great pkg.

storrgie commented on 2017-11-02 14:39

Yeah... their ghost-cli thing is a pretty large departure for an install. This is why I orphaned it. I felt bad too... because it was a really nice way to consume their software. I wanted to leave this package in a working state. As far as I know it still currently gives you a working installation for ghost.

I think this package should be renamed to ghost-legacy and if someone wants to dig in to figure out why the most recent legacy builds are not working then they could get it updated... right now its a couple releases behind.

I finally took the time to read their documentation and try to re-create the type of install that this package, I documented that here:

I'm sure I'm breaking some rules for how to install node based applications, which is why I threw it inside a container to begin with. I couldn't get over how installing "ghost-cli sqlite" via npm resulted in this:

+ ghost-cli@1.1.3
+ sqlite3@3.1.13
added 627 packages in 19.334s

To me that means that almost always we'll basically have to have throwaway containers for where the node dependencies are being created. Seems like such a mess if you're trying to me "minimal" with your package base.

dmeijboom commented on 2017-11-02 12:12

I think this package shouldnt be updated. I'm going to package ghost-cli in a couple of days.

jollanza commented on 2017-11-02 11:57 any news?

storrgie commented on 2017-10-01 15:39

@Alad: done, sorry I didn't see that option. I'm thinking that this package should turn into ghost-legacy, and that someone should package ghost-cli. Either way, I'm not someone who does development in nodejs so I get frustrated easily with the ecosystem, I hope someone else with more experience picks this up.

Alad commented on 2017-09-30 16:05

@storrgie: you don't need to file a request to orphan a package you maintain. Just click "Disown Package" in the Package Actions box.

derintendant commented on 2017-09-30 11:42

I"m sorry, but I am afraid, I'll have to disown this package. With 1.0 the packaging will have to be completely overhauled, and as I am rathjer inexperienced with NodeJS, I dont"t think I will be able to do that dequately. Please feel free to go on. :)

RcrdBrt commented on 2017-09-28 14:53

it seems not @jollanza :(

jollanza commented on 2017-09-06 08:40

any news?

ToKrCZ commented on 2017-08-24 20:40

Just tried to make my own .pkg with `debtap`, but it fails to start. I am totally inexperienced with packaging, so maybe someone else may succeed. The package is built rather successfully, only with some minor warning, but the app doesn't start at all. There seem to be problems with main object init, as far as I can say (tested ghost-desktop-1.3.0-debian.deb as source).

tom-ntb% /usr/bin/Ghost
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Unable to find a valid app
at Object.<anonymous> (/usr/lib/Ghost/resources/electron.asar/browser/init.js:121:9)
at Object.<anonymous> (/usr/lib/Ghost/resources/electron.asar/browser/init.js:173:3)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:424:7)
at startup (bootstrap_node.js:147:9)

All comments