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

Problems on fresh install 2.4.0 on shared hosting #4809

Closed
Meuschke23 opened this issue Dec 10, 2020 · 7 comments
Closed

Problems on fresh install 2.4.0 on shared hosting #4809

Meuschke23 opened this issue Dec 10, 2020 · 7 comments
Assignees

Comments

@Meuschke23
Copy link

Meuschke23 commented Dec 10, 2020

Issue details

The download: https://static.wallabag.org/releases/wallabag-release-2.4.0.tar.gz doesn't contain the vendor directory.
That leads to

Fatal error: require(): Failed opening required '/*****/Wallabag/bin/../vendor/autoload.php'...

if i call

php bin/console wallabag:install -e=prod

like recommended on https://doc.wallabag.org/en/admin/installation/installation.html#on-shared-hosting

Environment

  • wallabag version (or git revision) that exhibits the issue: 2.4.0
  • How did you install wallabag? Via git clone or by downloading the package?: Package
  • Last wallabag version that did not exhibit the issue (if applicable):2.3.8
  • php version:7.4
  • OS:debian
  • type of hosting (shared or dedicated):shared hosting
  • which storage system you choose at install (SQLite, MySQL/MariaDB or PostgreSQL):MySQL
@j0k3r
Copy link
Member

j0k3r commented Dec 10, 2020

Try php bin/console wallabag:install --env=prod

@Meuschke23
Copy link
Author

hi,
thx for the help, but that gives me the same error, because autoload.php is missing in https://static.wallabag.org/releases/wallabag-release-2.4.0.tar.gz

@Meuschke23
Copy link
Author

Update: in https://github.com/wallabag/wallabag/releases/download/2.4.0/wallabag-2.4.0.tar.gz the vendor directory exists. That worked for me.

@j0k3r
Copy link
Member

j0k3r commented Dec 10, 2020

It should be the same archive 🤔

@di72nn
Copy link
Member

di72nn commented Dec 10, 2020

The archives are still different, why is this closed?

@di72nn di72nn reopened this Dec 10, 2020
@j0k3r
Copy link
Member

j0k3r commented Dec 10, 2020

Yes they are different, the one on static is the repo without deps. @nicosomb is going to fix that

@nicosomb nicosomb self-assigned this Dec 10, 2020
@nicosomb
Copy link
Member

Fixed.

@j0k3r j0k3r closed this as completed Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants