Call for install/setup stories from users
Wednesday, 17 March 2021 · 7 messages · last reply 15 Apr 2021
IL
Just like you, I usually download the Zip package on Windows and Linux. Then I put a Saxon Jar and maybe a Saxon license file in the lib/custom directory and adjust Xmx in the startup scripts for the given platform.
So I don’t use package managers for BaseX.
For some projects, I add BaseX and Saxon to the project’s (svn) code repo. I populate the webapp directory with project-specific code. If a new BaseX release arrives, I unzip it over the existing files, inspect the changes to the scripts in bin/ and to
webapp/WEB-INF/web.xml, reverting the changes to these files most of the time so that my project-specific changes are preserved.
I don’t do this for each and every new release. One project that I’m working on is still on 9.3.2 beta.
Another (public) repo version that I use as an XSLT service when deployed (instead of a Saxon servlet) currently runs 9.4.6:
https://subversion.le-tex.de/common/basex
It is bundled with Saxon PE 10.3 (not with a license file though), with a sample XSLT that transforms factbook.xml
(https://subversion.le-tex.de/common/basex/etc/factbook.xsl) and with additional documentation
(https://subversion.le-tex.de/common/basex/readme_modifications.txt)
Gerrit
Quoted text · Bridger Dyson-Smith · 52 lines
On 17.03.2021 20:05, Bridger Dyson-Smith wrote: > Hi all - > > Per the recent thread about installing, I was hoping to convince some of > you to share your experiences installing and running BaseX. Whether you > use Mac OS, Windows, a Linux, or something else: how are you installing > and running BaseX? > > I'm asking as there could be some possible improvements to the wiki that > might help new users (or even less-new users!) get up and running. > > Thanks in advance for your time and trouble! If I can hear about number > of approaches, I'm happy to attempt writing up some details for the wiki. > Best, > Bridger > > PS Here's mine: > > Operating systems: I'm typically using BaseX on either a FreeBSD or a > Void Linux system (rarely on other Linuxes, and only once or twice on > Windows). > > Install process: my OS' don't have a pre-packaged download for BaseX, so > I do something like: > 1. cd ~/bin > 2. mkdir basex-src basex-data > 3. fetch|wget https://files.basex.org/releases/BaseX.zip > <https://files.basex.org/releases/BaseX.zip> > 4. unzip BaseX.zip > 5. rm -rf basex/src basex/data > 6. ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data > ~/bin/basex/data > ... > 7. enjoy basex! > > Upgrade process: something like > 1. cd ~/bin > 2. fetch|wget https://files.basex.org/releases/BaseX.zip > <https://files.basex.org/releases/BaseX.zip> > 3. mv basex basex-old > 4. unzip BaseX.zip > 5. rm -rf basex/src basex/data > 6. ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data > ~/bin/basex/data > ... > > Usage note: I have a line in my shell RC file (~/.zshrc) that helps my > shell/command line know where to find the various basex executables: > `export PATH="$PATH:$HOME/bin/basex/bin"` > > >
BD
Bridger Dyson-Smith17 Mar 2021 21:06 #
Hi all -
Per the recent thread about installing, I was hoping to convince some of you to share your experiences installing and running BaseX. Whether you use Mac OS, Windows, a Linux, or something else: how are you installing and running BaseX?
I'm asking as there could be some possible improvements to the wiki that might help new users (or even less-new users!) get up and running.
Thanks in advance for your time and trouble! If I can hear about number of approaches, I'm happy to attempt writing up some details for the wiki.
Best,
Bridger
PS Here's mine:
Operating systems: I'm typically using BaseX on either a FreeBSD or a Void Linux system (rarely on other Linuxes, and only once or twice on Windows).
Install process: my OS' don't have a pre-packaged download for BaseX, so I do something like:
1. cd ~/bin
2. mkdir basex-src basex-data
3. fetch|wget https://files.basex.org/releases/BaseX.zip
4. unzip BaseX.zip
5. rm -rf basex/src basex/data
6. ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex/data
...
7. enjoy basex!
Upgrade process: something like
1. cd ~/bin
2. fetch|wget https://files.basex.org/releases/BaseX.zip
3. mv basex basex-old
4. unzip BaseX.zip
5. rm -rf basex/src basex/data
6. ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex/data
...
Usage note: I have a line in my shell RC file (~/.zshrc) that helps my shell/command line know where to find the various basex executables:
export PATH="$PATH:$HOME/bin/basex/bin"G
Graydon17 Mar 2021 21:26 #
Quoted text · Bridger Dyson-Smith · 5 lines
On Wed, Mar 17, 2021 at 03:05:58PM -0400, Bridger Dyson-Smith scripsit: > Per the recent thread about installing, I was hoping to convince some of > you to share your experiences installing and running BaseX. Whether you use > Mac OS, Windows, a Linux, or something else: how are you installing and > running BaseX?
This is on Fedora; it's pretty much strictly an update process by now, though the install process only skips step 3.
1. Download BaseX.zip from the website into ~/bin/basex
2. cd ~/bin/basex
3. mv basex BaseX$VERSION
4. unzip BaseX$VERSION.zip
5. cd basex
6. rmdir data
7. ln -s ../data .
Because the executables are always on the same path --
~/bin/basex/basex/bin -- I don't have to update the shortcut icons when I update versions.
Every now and again I'll go through and prune old versions from bin/basex.
It would be _better_ if there was a Fedora package and I didn't have to think about performing the update, but, well, BaseX is on a very short list of software that's useful enough to use even if it's not available as a Fedora RPM via dnf.
--
Graydon Saunders | graydonish at gmail.com
Þæs oferéode, ðisses swá mæg.
-- Deor ("That passed, so may this.")
LQ
Quoted text · Bridger Dyson-Smith · 10 lines
On Wed, 2021-03-17 at 15:05 -0400, Bridger Dyson-Smith wrote: > Hi all - > > Per the recent thread about installing, I was hoping to convince some > of > you to share your experiences installing and running BaseX. Whether > you use > Mac OS, Windows, a Linux, or something else: how are you installing > and > running BaseX?
Here, i download the latest zip, unzip it, rename basex to e.g. BaseX95-20210227
and make a symbolic link "basex" to point to it, so that any scripts i have on the server always use the newest (or, if i roll back, which ever one i want, but i don't think i've ever had to roll back).
I have to avoid using the config file in the distribution, but use ~/.basex instead, so that configuration is maintained.
So i think this is very similar to your approach; ~/packages/basex has half a dozen distributions under it, including "github".
Linux: CentOS 7 (server) and Mageia 8 (desktop)
--
Liam Quin - https://www.fromoldbooks.org/
Also https://www.delightfulcomputing.com/
Full-time slave in voluntary servitude
BE
Since I never had the need to keep older versions alive, apart from step 1 my install and upgrade procedure are the same:
1: mkdir ~/Programs/basex
2: Download BaseX.zip
3: Unzip to ~/Programs
I never needed to (re)create the data directory or the symbolic link After adding ~/Programs/basex/bin: to my path, I can start basexgui or basexserver & from the coammandline.
Ben
Quoted text · Graydon · 31 lines
Op 17-03-2021 om 20:26 schreef Graydon: > On Wed, Mar 17, 2021 at 03:05:58PM -0400, Bridger Dyson-Smith scripsit: >> Per the recent thread about installing, I was hoping to convince some of >> you to share your experiences installing and running BaseX. Whether you use >> Mac OS, Windows, a Linux, or something else: how are you installing and >> running BaseX? > > This is on Fedora; it's pretty much strictly an update process by now, > though the install process only skips step 3. > > 1. Download BaseX.zip from the website into ~/bin/basex > 2. cd ~/bin/basex > 3. mv basex BaseX$VERSION > 4. unzip BaseX$VERSION.zip > 5. cd basex > 6. rmdir data > 7. ln -s ../data . > > Because the executables are always on the same path -- > ~/bin/basex/basex/bin -- I don't have to update the shortcut icons when > I update versions. > > Every now and again I'll go through and prune old versions from > bin/basex. > > It would be _better_ if there was a Fedora package and I didn't have to > think about performing the update, but, well, BaseX is on a very > short list of software that's useful enough to use even if it's not > available as a Fedora RPM via dnf. > >
G
Graydon18 Mar 2021 04:36 #
Quoted text · Ben Engbers · 3 lines
On Wed, Mar 17, 2021 at 10:43:07PM +0100, Ben Engbers scripsit: > To my knowledge there is no need to remove the data directory. I have never > done this and have never had any problems
Well, data/ is in the archive empty and I need to retain the existing data from the incumbent basex when I update BaseX.
I find it's simpler to promote data/ to being a sibling of basex/ and use a symbolic link from inside basex/ to find it so I don't have to argue with the defaults. (I am far from sure you can argue with the defaults to the extent of putting the data directory outside of basex/.)
So, if you have no need to retain data = no need to do anything with data/. But if you do need to retain data/, giving whatever archive tool a chance to drop an empty data/ over it on upgrade is maybe not the best plan.
--
Graydon Saunders | graydonish at gmail.com
Þæs oferéode, ðisses swá mæg.
-- Deor ("That passed, so may this.")
AM
Quoted text · Bridger Dyson-Smith · 10 lines
Am 17.03.2021 um 20:05 schrieb Bridger Dyson-Smith: > > Per the recent thread about installing, I was hoping to > convince some of you to share your experiences installing and > running BaseX. Whether you use Mac OS, Windows, a Linux, or > something else: how are you installing and running BaseX? > > > >
Late to the party, but as a Windows user, who always used the installer from day one,
I couldn't be happier. One click install. Same for updates. Except a minor issue:
I start BaseX with my own Javascript frontend (replacing the batch script), and it gets
simply erased when updating. But now, that I know this, I keep a copy of it somewhere
else and copy that over.
I also use the WAR with Jetty, but that is totally custom, running on a separate,
local Jetty instance with some other WARs side-by-side. I download the WAR and
extract it. When updating, I carefully manage all config files, etc. manually.
--
Goody Bye, Minden jót, Mit freundlichen Grüßen,
Andreas Mixich
Written for BaseX 9.5. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery