What is Reddit's opinion of Octopress?

From 3.5 billion Reddit comments

Sourceforge is indeed older, but the Github workflow (pull requests, group management, permissions) and the tooling they've built around git are much better. There's also Github pages for documentation and static sites like octopress blogs...

So many useful things, it's free for open source, and great for companies as well.

Sourceforge is a great thing, but it had its heyday.

If I may just throw this out there, have you considered a website to host/advertise this on? Something like a hub for the podcasts, where you could download it easily or have a link to it. Even just to have an RSS feed to tell people there's a new podcast.

Edit: If money is an issue, may I suggest something like Jekyll or Octopress. They can be hosted for free, are mostly simple (Unless you dig into the code) and are very fast and stable.

Edit 2: Could also be used as a linkdump.

I'd like to suggest a different approach. I consider t2.micros useless for just about anything expect learning some new feature in AWS or demos.

You should certainly experiment with beanstalk to learn how all that works, but it would be cheaper for your long term blog to get one of those WordPress plugins that deploys to S3/Cloudfront and just keep slumming it on the one t2.micro. Throw the backups in S3 too.

My blog (with a CDN!) costs a whopping .23 cents last month + .51 cents in route53 DNS charges. That's just too awesome to ignore.

I don't use WordPress though so I am not sure which "publish to static HTML/S3" plugin is the one people prefer so you'll need to dig around there. Eventually I dropped having to need a running instance entirely and just generated my blog locally and pushed to S3. This may be opposite of how you want to do things though, especially if your goal is to learn all about scaling, so I'm just tossing this out there.

Plus, it's an easy excuse to learn all about S3 and CloudFront!

EDIT: I use http://octopress.org/ And followed these instructions: http://blog.jacobelder.com/2012/03/deploying-octopress-to-amazon-s3/

If you are just interested in making static blogs, I would also recommend either:

• Octopress: http://octopress.org/
• Frog: https://github.com/greghendershott/frog

Personally, I like frog more than octopress because it has significantly few components (and is thus easier for my tiny brain to understand), but the tradeoff is that it does less for you out of the box then octopress does. But I like both of them more than something like wordpress because I find it a lot easier to manage a static website then having to manage something dynamic like wordpress.

In either case, you can write your posts in markdown, and it generates a blog for you, which you can then put onto github pages https://pages.github.com/, or any other site willing to serve static content.

If you want to establish a simple web presence, GoDaddy is fine. Alternatively, there are some other free services you can use:

• Github Pages - This is a free service from Github where you get a username.github.io domain (can also use a custom domain if you have one). You basically maintain a github repo that contains your site, and this is loaded by Github into a webpage.

A popular front-end to this service is Octopress, which comes with themes. A lot of developers like GithubPages because they get to write Markdown (like is used here on Reddit) for it and treat it like code.

• Google Sites - A free service from Google that also has templates.

• Wordpress or Blogger - complete remove any concerns other than writing.

Octopress is a simple blogging platform built on ruby. There's a simple rake task for generating new posts and it's flexible enough to use markdown or haml depending on your preferences.

To take this further, using Markdown for the text files, run a static blog generator like Octopress or Pelican. More here. Blogging software has solved the organizational problems like time stamping, folder structure, pictures, etc. Use git or mercurial for document control and replication.

Or you can make a blog on blogspot or wordpress private. Thus multiplatorm and accessible from anywhere.

>Easy to install

You said that jekyll wasn't easy to install, but Lanyon is? Lanyon requires nodejs, npm, ruby, and bundler to be installed, whereas Jekyll it is just ruby and bundler. Not sure if I follow the logic there...

Not to mention with Jekyll, I just need to know ruby if I need to investigate internals or write plugins. Lanyon requires an understanding of es6 / node / npm. I agree that those tools are much better at assets and file management, but is Lanyon easier? thats a hard sell.

And after building my blog with Octopress and being bit in the butt with a lack of updates, I would be very nervous to use something that builds on jekyll.

It's a static site generator built with on the NodeJS JavaScript platform. Source files go in, website comes out. The advantages of the site being static are it loading much faster and being more secure, both as a result of not having to do any server-side calculations.

If you're looking into Wordpress, take a look at Octopress. It's "similar" (a blogging platform), but in the same vein as Metalsmith, Wintersmith, Docpad, etc, in being static content. I've heard it's rather good, though it does take more effort to set up if you don't have a hosting service that can quickly deploy a Wordpress installation. Another benefit is being able to host your blog on GitHub Pages, which utilises Fastly, one of the fastest Content Delivery Networks in the world (they seriously need to fix their caching rules, though; 10 minutes is a bit ridiculously short).

Sorry if it sounds like I'm trying to sell you something; just pointing out that there are options other than Wordpress that may be checking out.

Another recommendation of Jekyll and it's "easier" derivatives Jekyll Bootstrap and Octopress. Ruhoh looks interesting but I've not tried it.

> A Pi's got 256 megs.

And that's my point. If you are trying to host a WordPress blog off of the pi, it's not going to end well no matter what the solution. Websites that run off of the pi must themselves be as lean and resource efficient as possible in an effort to decrease overall requests, memory consumption, and disk i/o.

Choosing between apache, nginx, lighttpd, monkey, barracuda or any other web server is not ultimately the answer for hosting sites on the pi. Sites have to be smarter to run on the pi. Look at solutions like this that are popping up everywhere. You have your blog content in a db, run the program to regenerate the site/pages when you update. The program spits out static content which as we know gets served rather quickly.

Say you need dynamic content solutions like PHP. Well you can't use Symfony, it takes a minimum of .5 seconds just to bootstrap on a full server. That's cause it loads 400 files for each request with the autoloader. How is that smart, lean or efficient is that? If your argument is nginx is faster than apache but you are using Symfony or WordPress, the issue lies elsewhere. Micro-frameworks like this PHP MVC framework that runs from one file are the kinds of solutions that work on a pi.

In world where full stack applications have gotten so huge and memory consuming, you cannot rightly blame the hosting processes for taking so long to serve requests. What's in the world does a 24% versus 21% memory consumption difference mean between apache and nginx when you have issues like this?

Aye, right now it's still a bit more of a developer's tool for those willing to dig a bit. At some point mynt will have a built in octopress so-to-speak with an init command and a default theme.

In the nearer future though, I'll be adding a powered by section to the docs site listing existing sites and their sources to give people some working examples to look at.

For now, you can check out the source to my blog that uses mynt if you think that might help in the meantime.

Something to note: there is also the popular Octopress which is a "fork" of Jekyll but with way more features out of the box
I don't like it myself since I have more fun modding my own Jekyll instead of a tailored solution but wanted to point it out anyway

I'm afraid I'm not going to be able to help with this one, I don't know much of anything about Wordpress. For my blog I've used both MovableType and now Octopress.

My suggestion would be to get Wordpress running locally on your own machine. Then you could play around with your categories and sub-categories before making any changes on your actual blog. There's lots of other side-benefits to being able to test out changes locally before pushing it to the Internet.

If you can't find a good guide for you changing categories, sub-categories, and redirecting old links. It might be an excellent topic for a blog of your own some day!

Thanks! I'm using octopress with greyshade theme. There are a few customizations, but theme's defaults are also good out of the box.

I'm fond of octopress for this sort of thing. I can run my updates client-side, preview them, and rsync the results to my server when I'm good and ready.

OTOH, I run a VPS so I have rsync (and ssh) access. It won't run in a random php+mysql hosting setup.

I like octopress. Could be just what you are looking for. I like it because I can write my markdown on the go with ease and then just drop it in octopress when I get back to my dev machine to publish. You can deploy to heroku and get free hosting too.