Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WordPress is now 13 years old

wordpress.org

Post reply on HN
Print view View original

11–20 of 66 posts

Re: WordPress is now 13 years old

#11

Post by AdmiralAsshat »

INTPenis wrote: post #8
falcolas wrote: post #3

A few free safety and performance tips when dealing with wordpress: - Whitelist IPs for access to your wp_admin and wp_login. - If you have the skills to automate WordPress updates yourself, remove all write access (except for the uploads folder) from the user WordPress is running as (i.e. www-data). It's all just unzip and untar over the structure of the directory anyways. - If you remove write access, you might as…

May I add a very general tip for web servers? Mount /tmp on its own volume and set the noexec mount flag. I've seen too many old php apps fall due to files uploaded and executed from /tmp. Bulletin boards, blogs, but this was all 8 years ago.

Never occurred to me to do this. That's actually a great idea.

Re: WordPress is now 13 years old

#12

Post by Cthulhu_ »

falcolas wrote: post #3

A few free safety and performance tips when dealing with wordpress: - Whitelist IPs for access to your wp_admin and wp_login. - If you have the skills to automate WordPress updates yourself, remove all write access (except for the uploads folder) from the user WordPress is running as (i.e. www-data). It's all just unzip and untar over the structure of the directory anyways. - If you remove write access, you might as…

Re: caching, wp-supercache works pretty good too.

Re: WordPress is now 13 years old

#13

Post by legitster »

Wordpress's success has to be down to it's ecosystem. There are other CMSs that are better targeted to more specific uses, but the amount of options and choices to a web designer with Wordpress are unreal.

Re: WordPress is now 13 years old

#14

Post by Cthulhu_ »

The problem I have with wordpress - and any php project for that matter - is that I'm afraid of the code. I've done some template editing for WP and it already scarred me enough.

But maybe I just prefer writing and working in my own familiar codebases instead of spending a small amount of time in that of others, a curse that a lot of PHP developers have (the "I'll write my own framework / cms" curse)

Re: WordPress is now 13 years old

#15

Post by jordanlev »

projectramo wrote: post #10

I alternate between thinking how great Wordpress is, and how it isn't so great. If you hit its (admittedly broad) use case, you are great, but if you go even a little off, its a pain.

To me, what's great about WordPress is how they've fostered and managed their community and maintained backwards compatibility to an impressive extent. The code itself on the other hand... oy vey.

Re: WordPress is now 13 years old

#16

Post by falcolas »

Cthulhu_ wrote: post #12
falcolas wrote: post #3

A few free safety and performance tips when dealing with wordpress: - Whitelist IPs for access to your wp_admin and wp_login. - If you have the skills to automate WordPress updates yourself, remove all write access (except for the uploads folder) from the user WordPress is running as (i.e. www-data). It's all just unzip and untar over the structure of the directory anyways. - If you remove write access, you might as…

Re: caching, wp-supercache works pretty good too.

My only concern there is that `wp-supercache` is a plugin, so you're still having to spin up php and work through the WordPress core just to get to the point where you can serve the files out of that cache.

It's likely better than no cache, but an external cache will be much more efficient under load.

Re: WordPress is now 13 years old

#17

Post by falcolas »

hyeomans wrote: post #7
falcolas wrote: post #3

A few free safety and performance tips when dealing with wordpress: - Whitelist IPs for access to your wp_admin and wp_login. - If you have the skills to automate WordPress updates yourself, remove all write access (except for the uploads folder) from the user WordPress is running as (i.e. www-data). It's all just unzip and untar over the structure of the directory anyways. - If you remove write access, you might as…

Do you have a more in depth tutorial about this? Thanks

Afraid not - company secrets and all that.

That said, the steps above are the broad painting of exactly what we've done, and a few Google searches will help nail down the specifics.

Re: WordPress is now 13 years old

#18

Post by falcolas »

cmdrfred wrote: post #6
falcolas wrote: post #3

A few free safety and performance tips when dealing with wordpress: - Whitelist IPs for access to your wp_admin and wp_login. - If you have the skills to automate WordPress updates yourself, remove all write access (except for the uploads folder) from the user WordPress is running as (i.e. www-data). It's all just unzip and untar over the structure of the directory anyways. - If you remove write access, you might as…

As for the cache Cloudflare's free tier as allowed me to handle pretty large traffic loads in the past, much more then my $5 droplet should be able to handle. This was for a blog platform I wrote in Flask though(and optimized for cloud flare) so it might not be comparable.

Yup - it's the same concept, different application. Anything that reduces the need to run code will help with the performance of your blog.

Re: WordPress is now 13 years old

#19

Post by falcolas »

INTPenis wrote: post #8
falcolas wrote: post #3

A few free safety and performance tips when dealing with wordpress: - Whitelist IPs for access to your wp_admin and wp_login. - If you have the skills to automate WordPress updates yourself, remove all write access (except for the uploads folder) from the user WordPress is running as (i.e. www-data). It's all just unzip and untar over the structure of the directory anyways. - If you remove write access, you might as…

May I add a very general tip for web servers? Mount /tmp on its own volume and set the noexec mount flag. I've seen too many old php apps fall due to files uploaded and executed from /tmp. Bulletin boards, blogs, but this was all 8 years ago.

Good tip. If you'll excuse me, I'm going to go make a Jira ticket now...

Re: WordPress is now 13 years old

#20

Post by scotchio »

Say what you will about WordPress - its codebase, security, speed, architecture, DB schema, whatever. Haters are going to hate.

It's a pretty amazing accomplishment what Automattic has done by staying so popular and relevant for so long.

Looking at it from a non-hardcore programmer's perspective:

* Quick to learn backend

* Easy to use plugins for non-devs

* Painfully maintaining backwards compatibility overtime

* It just works. Built to run from basically a potato of a server. E.g.: HTTP/transport check [1]

[1]: https://github.com/WordPress/WordPress/blob/master/wp-includ...

Post reply on HN