search

ix-plugin-hub / iocage-plugin-index

Community created JSON files for plugins.
153 stars 110 forks source link

gitea 13.2release install fail! #388

Open yaoyutian opened 8 months ago

yaoyutian commented 8 months ago

error: gitea had a failure exception: runtimeerror message: pkg error: - postgresql11-server :,postgresql11-contrib : refusing to fetch artifact and run post_install.sh! partial plugin destroyed

seems postresql11 not esixt? image

pmhausen commented 8 months ago

Nope. PostgreSQL 11 was EOL upstream in November 2023 and now removed from the FreeBSD package repos. 13 and 15 are available with 15 being the new default version as of this quarter.

yaoyutian commented 8 months ago

could we just change postgresql to 15 in this repo's gitea json ? i have viewed the plugin postinstall sh, it seems it's not pg version releated.

pmhausen commented 8 months ago

could we just change postgresql to 15 in this repo's gitea json ? i have viewed the plugin postinstall sh, it seems it's not pg version releated.

For new installations this will probably just work. Unfortunately for updates PostgreSQL does not perform in-place upgrades of the database like MySQL and MariaDB do. One must perform a manual database export and reimport. Also I do not know if you can skip a version or if you must go 11 > 13 > 15.

There should at least be a large warning sign.

yaoyutian commented 8 months ago

i sovled by manual install pkg(gitea,postgresql15-server,postgresql15-contrib) then postinstall.sh; thank god, all goes well.

lowlander commented 7 months ago

could we just change postgresql to 15 in this repo's gitea json ? i have viewed the plugin postinstall sh, it seems it's not pg version releated.

For new installations this will probably just work. Unfortunately for updates PostgreSQL does not perform in-place upgrades of the database like MySQL and MariaDB do. One must perform a manual database export and reimport. Also I do not know if you can skip a version or if you must go 11 > 13 > 15.

Umm does that mean it will simply stay broken from now on? Or how should I install gitea on a fresh Core install ?

pmhausen commented 7 months ago

Umm does that mean it will simply stay broken from now on? Or how should I install gitea on a fresh Core install ?

I don't know. The maintainer of this plugin who decided to use PotsgreSQL instead of the more common and operationally simpler MySQL or MariaDB should.

I have gitea running like this for a couple of years now. Plugins as created are unfortunately just shortcuts for initial installation. Nobody thought of continuing maintenance and updates. Wich is difficult given that many plugins are supposed to manage valuable data.

If you have an existing plugin jail, then create a standard jail like above but install PostgreSQL 15 instead of MariaDB, do a pg_dumpall on your old plugin, re-import in the new jail.

lowlander commented 7 months ago

Umm does that mean it will simply stay broken from now on? Or how should I install gitea on a fresh Core install ?

I don't know. The maintainer of this plugin who decided to use PotsgreSQL instead of the more common and operationally simpler MySQL or MariaDB should.

Pesky volunteer maintainers always doing something wrong ;-)

pmhausen commented 7 months ago

My general recommendation is: learn jails and their tooling, packages, services, ... in FreeBSD and move away from plugins. If you know me from the TrueNAS forum you know I am a strong proponent and advocate of jails. They are rock solid great container technology.

It's only the plugin framework that neglects production operation and ongoing maintenance. This is not any of the volunteer maintainers' fault but an architecture problem.

Jails can be created with a single "iocage" command on the command line and then an automation like Ansible used to deploy any application.

NikeLaosClericus commented 1 month ago

I lost all of my data due to a failed update... Never using plugins for anything more than "ephemeral services" again.