TOPIC:

Hi, all.

I've got an installation of Xerte that I set up about six years ago and have kept upgraded, and it's been working great. However, the Linux distribution it's on has been discontinued, and there's no clear upgrade path, so it looks like I'm going to have to build another machine and then cut over to it.

However, after six years there's quite a bit of content stored in the system, as you might imagine. Is there any way to move an existing installation wholesale to a new server? I imagine dumping and restoring the database will take care of (e.g.) configuration settings and such, but what about the content?

Also, could I theoretically switch from Apache to Nginx? Is Xerte pretty web server-agnostic?

Please let me know if I need to elaborate on or clarify anything, and thanks in advance.

Hi
basic principal is to move the files and database to the new server and ensure that the directory structure and permissions and database credentials/access is the same or update the database values and config files accordingly.
You'll need to make sure the PHP requirements are in place xot.xerte.org.uk/play.php?template_id=81#systemrequirements and also default upload limits etc.
If the current install is large I've used things like rsync to transfer the files server to server and it's usually a good idea to do a test run and check everything is working and then repeat or keep the initial test run as a test server.
Obviously that's the basic idea but you'll probably have authentication, dns and firewall stuff to deal with as well as any vle integration like LTI etc.
I think Xerte is server agnostic for the most part but most of the installs we run and test with are typically Apache.
HTH
Ron

I've never tried nginx, and thare are some .htaccess files in the installation (that are not realyy needed, but increase security). I have rubn Xerte on IIS, and also apache with fpm. So I would be surpsrised if nginx doesn't work.

After migrating the files and database, you can update the database settings in the file database.php, and you need to check and correct the paths in the sitedetails table (columns root_file_path and import_path)

Cheers,

Tom