Skip to content
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

Please improve/expand installation instructions #7121

Open
joenepraat opened this issue Dec 14, 2023 · 0 comments
Open

Please improve/expand installation instructions #7121

joenepraat opened this issue Dec 14, 2023 · 0 comments
Labels

Comments

@joenepraat
Copy link

joenepraat commented Dec 14, 2023

Thank you for this great piece of software. I think it's the best of its kind. I couldn't find a better alternative. I was eventually able to install it on Debian with Nginx and Postgres. Unfortunaly it took more than 5 hours, because the installation instructions are incomplete and the make install installation script didn't work as it should. This had especially to do with Postgres and Nginx. The installation script couldn't create a database and the Nginx example is not complete. Somehow the installation script wasn't able to create the wallabag database. I had to manually create the wallabag user and database in postgres with enough permissions to create tables. Only after that, it said 'you already have a database, do you want to reset it?' and when I clicked yes, it created the tables. This had probably to do with that the installation script was written for MySQL. Note that I'd run it as the www-data user from root like this sudo -u www-data make install in the /var/www/wallabag directory.

There was also an issue with the installation script not putting single quotes (') around the domain name if I remember correctly (the script added https://domain.tld, but it had to be 'https://domain.tld' of course). And after it worked Wallabag complained about my import file being to large, despite I added 'client_max_body_size 99M' to the virtual host config. I also had to change post_max_size = 99M and upload_max_filesize = 99M in /etc/php/.../fpm/php.ini. Note that this 99M is an arbitrary number.

All this could have been avoided by a complete installation documentation and a working installation script that understands Postgresql. Hopefully someone has the time to improve this. Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant