A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
There are a couple options. You could present some storage and mount it over nfs. Move the whole server, as you mentioned. Set up a little http server and only put the media over there.
Or, why not take this opportunity to move away from a platform whose CEO is hostile and abusive to the community? https://techcrunch.com/2025/01/12/wordpress-vs-wp-engine-drama-explained/
NFS works great for media files and stuff but be careful and know what you are doing before you go put database storage on it.
Is WordPress running in docker or on the host is?
What you could do is set up and NFS or smb share on the ote other server, move all the media to that share on the file server and then mount the NFS/b share to the folder on the WordPress server.
Set up the NFS/smb share to mount at boot. WordPress shoudnt wvwn notice the difference.
It's been a long time, but... wordpress is all sql isn't it? Shouldn't it just be, make a backup of the mysql database on the old server, install mysql and restore the database to the new server, and then point the word press servers configuration to the new database?
Not all sql. A lot is files on disk too, but you should be able to do a backup and restore of all of Wordpress.
A hacky solution would be to copy all images into a directory on the other server and sshfs-mount that to where WordPress expects it on the current server.
It depends on what kind of server this is. If it's cloud-y, then you can just mount another volume and move everything there.
If it's a amatatic VPS where you can't uograde or change it at all, you're not going to find a performance solution without using a CDN or manually mapping to something S3 compatible.