Hi all, What is the best way to upgrade BaseX on a production server? My current version is 11.1 and I'd like to upgrade to the latest. My gut feeling is that all it takes to overwrite the following (and leave everything else):
*bin/etc/lib/BaseX.jar* ... and then restart the http server. Any thoughts? Thanks
On Sun, Mar 02, 2025 at 02:05:31PM +0100, Csaba Fekete scripsit:
My current version is 11.1 and I'd like to upgrade to the latest. My gut feeling is that all it takes to overwrite the following (and leave everything else):
*bin/etc/lib/BaseX.jar* ... and then restart the http server. Any thoughts?
As I have things set up (which is NOT in the context of a production server), the basex directory looks like:
BaseX.jar CHANGELOG* etc/ LICENSE* repo/ webapp/ bin/ data@ lib/ readme.txt src/
BaseX is completely fine with data/ being a symlink.
So I'd be installing full latest, customizing/testing full latest, and then doing stop-the-11.1-server, symlinking the production data dir into the latest install directory structure, and starting the lastest server.
My usual setup puts the actual data/ dir one level up from the full-install location, so a sibling of the BaseX versions. I've never tried anything clever like putting the data/ dir on a NAS or another file system so can't speak to those cases. (Though I would expect that symlinking from more than one running BaseX instance would be entirely unwise.)
("Fine with symlinks" works with lib/custom, too.)
-- Graydon
-- Graydon Saunders | graydonish@fastmail.com Þæs oferéode, ðisses swá mæg. -- Deor ("That passed, so may this.")
Right: BaseX.jar, bin/ and lib/ are essential. etc/, repo/ and webapp/ contain optional resources and examples.
If the files in webapp/WEB-INF/ are not copied, they are created automatically. If you encounter problems after an upgrade of a major version, you may need to delete those files before restarting basexhttp. This could occur with BaseX 12, which will be based on Jetty 12.
On Sun, Mar 2, 2025 at 2:05 PM Csaba Fekete feketecsaba@gmail.com wrote:
Hi all, What is the best way to upgrade BaseX on a production server? My current version is 11.1 and I'd like to upgrade to the latest. My gut feeling is that all it takes to overwrite the following (and leave everything else):
*bin/etc/lib/BaseX.jar* ... and then restart the http server. Any thoughts? Thanks
Thank you both! I successfully upgraded the production server with only a few seconds of downtime :-)
On Sun, 2 Mar 2025 at 15:38, Christian Grün christian.gruen@gmail.com wrote:
Right: BaseX.jar, bin/ and lib/ are essential. etc/, repo/ and webapp/ contain optional resources and examples.
If the files in webapp/WEB-INF/ are not copied, they are created automatically. If you encounter problems after an upgrade of a major version, you may need to delete those files before restarting basexhttp. This could occur with BaseX 12, which will be based on Jetty 12.
On Sun, Mar 2, 2025 at 2:05 PM Csaba Fekete feketecsaba@gmail.com wrote:
Hi all, What is the best way to upgrade BaseX on a production server? My current version is 11.1 and I'd like to upgrade to the latest. My gut feeling is that all it takes to overwrite the following (and leave everything else):
*bin/etc/lib/BaseX.jar* ... and then restart the http server. Any thoughts? Thanks
On Sun, 2025-03-02 at 14:05 +0100, Csaba Fekete wrote:
Hi all, What is the best way to upgrade BaseX on a production server? My current version is 11.1 and I'd like to upgrade to the latest. My gut feeling is that all it takes to overwrite the following (and leave everything else): bin/ etc/ lib/ BaseX.jar ... and then restart the http server. Any thoughts?
In the past i found that basex looked at ~/.basex and $serverdir/.basex files (Linux at least), and these need to be checked for any changes.
liam
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Csaba Fekete -
Graydon -
Liam R. E. Quin