WordPress is now 13 years old
wordpress.org
WordPress is now 13 years old
1–10 of 66 posts
Re: WordPress is now 13 years old
#213 years ago Movable Type and Blogger owned the space. MT was for folks who wanted to install software on their own server, Blogger for those who wanted a hosted option.
Blogger was bought by Google a few months before WP appeared.
Re: WordPress is now 13 years old
#3A 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 well block the "cron" as well.
- Limit the WordPress DB user to the usual crud operations; don't let it create or alter tables.
- If you feel like getting really into it, whitelist explicit URLs. Maintaining it isn't really too hard, and it reduces your attack surface significantly.
- Set up even a simple nginx cache in front of WordPress - even a 1-5 minute cache will let your site run on crappy hardware and handle HN or Reddit with a minimum of sweat.
Re: WordPress is now 13 years old
#413 years ago Movable Type and Blogger owned the space. MT was for folks who wanted to install software on their own server, Blogger for those who wanted a hosted option. Blogger was bought by Google a few months before WP appeared.
Fun note: you could let Blogger publish to your own FTP and host it that way and use the site only as the CMS.
Re: WordPress is now 13 years old
#5I'm not sure if it's me, but when ever I see WordPress in a news article, the first association is always with 'Mass Hacks'...
Re: WordPress is now 13 years old
#6A 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.
Re: WordPress is now 13 years old
#7A 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
Re: WordPress is now 13 years old
#8A 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.
Re: WordPress is now 13 years old
#9I'm not sure if it's me, but when ever I see WordPress in a news article, the first association is always with 'Mass Hacks'...
It's a much safer platform these days...
...most of the sites with really important data have long since migrated away. Haha
Re: WordPress is now 13 years old
#10I 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.