Re: apps from launcher not working on new install
Hayim Lapin <[email protected]> Tue, 18 Feb 2025 12:36:46 -0500
| Newsgroups | gmane.text.xml.exist |
|---|---|
| Message-ID | <CAE=1_O8_vMVG84Vi-MpNYJ-WYpmzPivj69smiA7ps4WTTM3JEA@mail.gmail.com> |
Once again, thank you for this suggestion! Just to close this circle, unfortunately, editing the conf.xml file did not solve the problem. On Sun, Feb 16, 2025 at 4:14 AM Florian Schmitt < [email protected]> wrote: > Hayim, > > it seems that in certain cases, the default apps aren't deployed > correctly. If I remember correctly, I ran into a similar issue with a > headless setup. > > Please try the following (assuming eXist is installed in /opt/existdb - > adapt the paths according to your setup): > > First, check if there's a directory /opt/existdb/autodeploy containing the > .xar files for eXide and so on. > > If the autodeploy directory seems fine, stop exist-db, and open > /opt/existdb/etc/conf.xml in a text editor. > > Search for the following lines: > > <trigger class="org.exist.repo.AutoDeploymentTrigger"> > <!-- parameter name="ignore-autodeploy-system-property" value="true"/ --> > <!-- parameter name="dir" value="${project.build.outputDirectory}/autodeploy"/ --> > </trigger> > > Uncomment the second "parameter" element, and change the "value" > attribute, setting the full path to the autodeploy directory. With exist > installed in /opt/existdb, the third line should now be > > <parameter name="dir" value="/opt/existdb/autodeploy" /> > > Now, restart exist-db and check the logs for messages regarding > autodeployment. If the AutoDeploymentTrigger doesn't fire, you may have to > uncomment the first parameter element, too. > > HTH > Florian > > Am 14.02.25 um 16:42 schrieb Hayim Lapin: > > Hello, > I just installed eXist 6.3 on an aws linux machine running on port *8081*. > The database loads and I can log in as admin. > All the default apps that appear on the launcher yield errors like: > HTTP ERROR 404 Document /db/apps/eXide not found > > I have been able to use the package manager to load and run an app > (TEI-Publisher), but other apps created by me and working in a docker > instance generate the following again caused by being unable to access /db: > >> err:XPST0017 error found while loading .... for module: >> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line >> 84, column 13] > > > There is another version of exist (4.7.1) running on port *8080*. Could > this be the cause of the problem? > > Any suggestions about how to fix this? > Best, HL > > > _______________________________________________ > Exist-open mailing [email protected]://lists.sourceforge.net/lists/listinfo/exist-open > > > _______________________________________________ > Exist-open mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/exist-open > _______________________________________________ Exist-open mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/exist-open