Ask HN: How to set up WordPress server with a read only file system
What I would like to achieve is WordPress running on a read-only file system, probably with a ram disk to handle things that does not to be done when the computer is running.
Reboot it and I would be back to the proper configuration. I would schedule one reboot every 12 hours I figure.
Does anyone know of any good documentation on handling the read only / ram drive configuration.
I had a great link from a long time ago but I just cant find it.
(Yes WordPress is bad. I should use a static site generator with nearly free hosting anyways)
I know but I have not found one I like yet.
(Yes hosting in your own home is a bad idea. you are not not setup for power failure, disk failure, scaling, etc)
All true, but I would like to try it. I think performance wise I will easily reach parity with cheaper end WordPress hosts) Plus if it goes down, well it wont be a big deal, I am not enterprisy.
I will have a dedicated hardware firewall in front of it.
2 comments
[ 0.24 ms ] story [ 17.8 ms ] threadI operate a few blogs running Bludit[0]. I do this since WP is highly complex. I like to keep it simple. But Wordpress is handy if you're a control freak and love to tinker.
Why do you want a read-only filesystem for WP? I have several WP installs running under XAMPP, and if I want to, I could have a hundred, or...a thousand for testing purposes.
[0] https://www.bludit.com/
I wish to "bring home" my WordPress blogs. That is, to house them, inside my house. I figure the best way to avoid getting it hacked, or recovering from it, would be a read only file system, that loads up a ram disk for WordPress to run on.
I would almost reverse what you said. If I let my control monster get out, I would not use WordPress because I can never get -exactly- what i want.
If I was hands on, static generator, or my own CMS (done that before) or just hand coding it I could get it just so. Except I would never write any posts. Id be too busy getting it "just so". :)
If something goes wrong, well a reboot should fix it.