Re: [Exist-open] Tips for upgrading to eXist 5.3.0

[Joe W. <jo...@gm...>]

p.s. The version number for existdb-packageservice listed below was
incorrect. It should be "1.3.13 or higher," not "2.8.13 or higher."
Apologies for the error. The release notes on exist-db.org have been
updated accordingly.

On Sun, Aug 1, 2021 at 1:17 PM Joe Wicentowski <jo...@gm...> wrote:

> Greetings,
>
> In light of reports of some unexpected problems that users encountered
> when upgrading to eXist 5.3.0, we have added an advisory to the 5.3.0
> release notes: https://exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb530.
> For your convenience, the content of the advisory is reproduced below. Some
> of the items had been in the original announcement, but we moved them all
> up to the top of the release notes to make them more prominent.
>
> We hope this helps folks better prepare for this very worthwhile upgrade
> and makes the upgrade process smoother.
>
> Joe
>
>
> - Before upgrading an eXist 5.2.0 or earlier system to eXist 5.3.0 (or as
> soon as possible after upgrading), be sure to upgrade
> *existdb-packageservice* to the latest release, version 2.8.13 or higher.
> Since Dashboard relies on this library for all package-related operations,
> this upgrade must be performed outside Dashboard. To upgrade this package
> outside of Dashboard, either submit the following query to eXist via eXide
> or the Java Admin Client as an admin user:
>
> xquery version "3.1";
>> repo:remove("http://exist-db.org/apps/existdb-packageservice"),
>> repo:install-and-deploy("http://exist-db.org/apps/existdb-packageservice",
>> "http
>> ://exist-db.org/exist/apps/public-repo/find")
>
>
> - The *shared resources* and *markdown* packages are no longer bundled
> with eXist-db. If your application depends on those you can still declare
> dependencies on them in your package metadata and download them from the package
> repository <https://exist-db.org/exist/apps/public-repo/index.html>.
>
> - *eXide*’s app generator function has been removed from eXide v3.0.0, as
> part of important improvements to the application. For generating apps,
> please use the much better yeoman-based generator-exist
> <https://github.com/eXist-db/generator-exist> tool.
>
> - *Dashboard* v2.0.8 has a known issue
> <https://github.com/eXist-db/dashboard/issues/194> that can cause
> requests a 404 error to appear after logging in to the administrative
> section. Until a permanent fix has been discovered, you can clear the
> affected browser of this problem by logging out and back in via eXide or
> Monex.
> The default eXist-db configuration settings are not production ready. Make
> sure to consult our article on best practices before making your eXist-db
> instance publicly available. The new existdb-config project implements
> these "best practices" and can easily be used to harden your eXist-db(s)
> from version 5.1.1 till 5.3.0.
>
> - The default eXist-db configuration settings are not production ready.
> Make sure to consult our article on best practices
> <https://exist-db.org/exist/apps/doc/production_good_practice.xml> before
> making your eXist-db instance publicly available. The new existdb-config
> <https://github.com/eXistSolutions/existdb-config> project implements
> these "best practices" and can easily be used to harden your eXist-db(s)
> from version 5.1.1 till 5.3.0.
>
>