Closed bomshteyn closed 3 years ago
Hello there! Thanks for opening your first issue on this repo!
Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.
Backpack communication channels:
backpack-for-laravel
tag;Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.
Thank you!
-- Justin Case The Backpack Robot
Of course figured out the issue right after opening the report... :-)
The server was using composer v1
while the dev environment was composer v2
ran composer self-update --2
The issue disappeared. 🤷
Bug report
What I did
Pushed a change in code to the forge server
What I expected to happen
Succesfull Deployment
What happened
I have got an error:
What I've already tried to fix it
Composer Install, Vendor folder delete and rebuild
Backpack, Laravel, PHP, DB version
PHP VERSION:
PHP 7.4.18 (cli) (built: May 3 2021 11:27:06) ( NTS ) Copyright (c) The PHP Group Zend Engine v3.4.0, Copyright (c) Zend Technologies with Zend OPcache v7.4.18, Copyright (c), by Zend Technologies
LARAVEL VERSION:
v8.42.1@41ec4897a70eb8729cf0ff34a8354413c54e42a6
BACKPACK VERSION:
4.1.44@42b837deb11870399e63310817b7e50b82570ed4