blogging with ghost

i decided that i wanted to start blogging again. and wordpress just seems like overkill nowadays. they've added so much junk to it it's no longer "just another wordpress blog" being made, everyone uses it as a boilerplate for making entire websites. it's just a hassle.

so begins my frustration.

i'm using ghost. it's fast, dead-simple to use, and lets me do what i want to do in seconds: blog. i decided after hearing everyone rant and rave about how great it is, and the kickstarter really helped too. posts are written in markdown, and the two-column layout lets you see your output in real time. if you're feeling frisky, you can write html directly into your post.

the biggest issue i have with ghost is the fact that it runs in its own "container," aka npm. you have to proxy through your web server unless this is your only web-serving app in which case set it to run on port 80. so serving any content on this domain aside from ghost is basically a crap-shoot. there's methods to muck with the code and let nodejs serve static files but that's a waste of resources. your web server should be serving it.

the work-around is to add a subdirectory to your nginx config to service that content specifically:

  location /static {
  alias /var/www/html/static;

just replace the 'alias' dir with the directory you want to serve out. of course this means for every subdirectory you want to have, back into the nginx config you gotta go.

subdomains you can serve content via nginx just fine, since it's an entirely different server{} entry.

node.js, you're useless.

all you're doing is re-inventing the wheel with a new language. if you want to serve files, properly act as an extension of the web server, not replace it entirely.

still, i'm keeping you around.

honestly, once i set up ghost and started using it, i fell in love. needing shell access to a box to install it is a pain point that will push a lot of inexperienced users away, but if you're not afraid of getting your hands dirty in the command line it's worth using.

comments powered by Disqus