-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallabag: Update Wallabag to 2.3.8 and various fixes #4179
Conversation
@publicarray Thanks for contribution. In fact I understand it is important to keep MySQL support because of previous version installation upgrade, but I would find more resource-effective to deliver package with PostgreSQL support by default, connected to DSM embedded version like for nextcloud PR #3853 In fact, I dream about a generic wizard process (shell script based) where user may select its database from a list (generated from available services in DSM): embedded postgresql, mariadb, sqlite, own package postgresql 11... with backup/restore support when uninstall/install. It would make sense for many applications... |
INSTALL_DEP_SERVICES = apache-web mysql | ||
START_DEP_SERVICES = apache-web mysql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would not enforce mysql dependency for users expecting to connect to embedded postgresql
Yes that is a good idea, How about we merge this PR first to fix the package (currently it's broken) and later I can work postgresql in a separate PR? |
In fact my idea is to have a "generic database support" in framework (like for service) that a package may re-use to avoid copy/paste... and sqlite may be useful for other application like ffsync |
@ymartin59 I understand, but how about we do this one step at a time 😅
PS I did not know that PostgreSQL is already installed |
Yes I agree. I will do some testing on this PR and publish first. |
@publicarray I just discover GH action does not build non-arch package and package fails to build on my system... I still do not know why |
Found: ARCH should not be override in cross/wallabag |
@@ -1,34 +1,64 @@ | |||
parameters: | |||
database_driver: pdo_mysql | |||
database_driver_class: ~ | |||
database_host: 127.0.0.1 | |||
database_port: 3306 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bad luck. On my test system, I have installed both MariaDB 5 and 10... so port is 3307 now
I have published package |
I get following error when installing the package on my DS2018+ : Failed to install wallabag. See errors at /var/services/web/wallabag/install.log |
From the log you need to check your database configuration. Do you have MariaDB installed? Check the port number and maybe you need to reset the password and try again?
|
I'm running MariaDB10 on Synology (port 3307). Do I need to create user & database first or will it be created by the package ? |
Change your port to And the wallabag install script will create the database and user for you. |
I have now also installed MariaDB 5 on my NAS which uses by default port 3306. I also have MariaDB 10 running because already created several databases in there for other applications. If both are running and I install Wallabag package , he creates user wallabag and database name (not yet the structure) wallabag in MariaDB 10 (which runs on port 3307). If I stop MariaDB 10 and try to install the package again, I get error message "Failed to install Wallabag. Incorrect MySQL root password." I would have expected that in the second case he would try to create user and database in the MariaDB 5. |
I am having the same plain HTML issue described here: wallabag/wallabag#4061 . What do you guys have configured for SYMFONY__ENV__DOMAIN_NAME? |
Linked issues: #3113, #3400, #3054
Build: https://github.com/publicarray/spksrc/releases/tag/wallabag-2.3.8
Checklist
all-supported
completed successfully