undefined | Better HN

0 pointsmacspoofing5y ago0 comments

>I think your response would be unfair.

I don't think so. The author actually gave themselves a weird goal - to use Wordpress as the text editor, and export/copy the static content to github. I'm not sure why they would do that, but OK! In the end, their problem wasn't with the workflow but with setting up local version of Wordpress (why? why not use a hosted version of Wordpress????), PHP, Apache, MySQL and FTP(!!).

WordPress isn't actually that hard to setup. It's a little harder on Windows, because setting up PHP on Windows just isn't as natural as on Linux but XAMPP makes it as easy as possible.

>Should 'blog writing' software really have such a greater barrier of entry?

But it doesn't. You have a plethora of (free) hosted blogging solutions. You could also get private hosting with the LAMP stack already pre-installed and configured.

0 pointsmacspoofing5y ago0 comments

>I think your response would be unfair.

WordPress isn't actually that hard to setup. It's a little harder on Windows, because setting up PHP on Windows just isn't as natural as on Linux but XAMPP makes it as easy as possible.

>Should 'blog writing' software really have such a greater barrier of entry?

But it doesn't. You have a plethora of (free) hosted blogging solutions. You could also get private hosting with the LAMP stack already pre-installed and configured.

0 comments

5 comments · 1 top-level

manigandham5y ago· 4 in thread

Why someone would do this: Wordpress has a solid editor, lots of plugins, and is used by millions so the workflow is well tested. The resulting pages are a perfect fit as static content.

You can accomplish this by using a CDN that caches everything, or use plugins that export static files like WP2Static, or use integrations with static site frameworks like Gatsby that treat WP as a CMS.

But yes, doing it all from scratch yourself is probably not worth it, especially if you're unfamiliar with the tech.

macspoofingOP5y ago

>Why someone would do this: Wordpress has a solid editor, lots of plugins, and is used by millions so the workflow is well tested.

Sure - why not. The question, why do you need to host it locally? You can just create a free account on wordpress.com, or get a private hosted solution for peanuts and with the LAMP stack already configured.

disgruntledphd25y ago

But to be fair, the authors core point is correct - running Wordpress locally and then deploying to the internet is an absolute tire-fire.

For context my wife uses wordpress to build various sites. I got lumped with the task of moving this online. It was super painful, as WP encodes the URL name (i.e. localhost) flipping everywhere.

I eventually resolved this by editing the tables which stored the URLS (fortunately, as a DS I know SQL) and doing some sed on various files that cached the URL.

I now refuse to do this, and set her up online with a website before she does any work, because moving it is so painful.

1 more reply

manigandham5y ago

Yes, that's what the last sentence is about.

forgotmypw175y ago

>why do you need to host it locally?

offline editing?

j / k navigate · click thread line to collapse