After running the command (signal-event nethserver-wordpress-update) the contents of the file “/etc/httpd/conf.d/wordpress.conf” back to its original state.
I tried replacing the directory / wordpress by “/” and “.” the settings (config SetProp wordpress URL.), but also did not work, Apache continues to show the default page, both http and https.
since you don’t add a new template ‘service httpd restart’ is enough but you can also use ‘signal-event nethserver-httpd-update’ because it restarts also httpd
So I guess I’m ready to try this… but my question is, will this repository stay up to date with Wordpress?
My other vps wp installs are constantly being updated by Wordpress, never mind the hot mess the plugins are for vulnerabilities, so I definitely don’t want to fall behind on one of the biggest targets on the Internet, well other than Joomla, you should see my ids logs, lol.
Normally epel tries to be up to date with this rpm, simply update from it. Alternatively I developed for SME Server an option to auto update wordpress with the internal core feature. I didn’t recall if I did it here. In fact nethserver-wordpress was a study case for me to learn how NS works… If my opinion could interest you, I do install my web application manually when I want to fit all my needs.
Any way, I’m looking in this direction to use the root directory for wordpress (it could be reused for dokuwiki and tt-rss) but it is not ready, stay tuned.