-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Where is the file FirebaseBundle.php ? #5
Comments
Update: in fact I didn't see the fact that composer failed to install the bundle saying that there is no version 1.0. |
Hey @youngdreamer33, there is no 1.0 release yet, in the meantime you can install it with composer require kreait/firebase-bundle 1.0.x-dev or insert
in your |
Thanks, this is what I did. [LogicException] Do you know how and where I can override it by any chance ? :) |
Yes, this was a bug that I fixed a couple of minutes ago 🙈, please try a |
Thanks but now I got this error: |
No problem @youngdreamer33 :). The snippet in the README is just an example to show that you can define multiple projects. Here is a minimal example: kreait_firebase:
projects:
my_project: # <- you can name this whatever you want
database_uri: 'https://my_project.firebaseio.com'
api_key: '<api_key>' You just have to replace the values for |
Thanks !! I didn't think it was an issue in config.yml but with your explanation I understand better how the bundle works so thanks a lot for your help ! |
You're welcome! 🌺 |
Hello,
I've been learning PHP with Symfony for a few months and want to add Firebase to my project (which I'm learning !).
There are new issues with the last version of Symfony with bundles (https://stackoverflow.com/questions/44928982/appkernel-php-weird-behavior#comment76834486_44928982) and I cannot fix it for your bundle.
The installation of the bundle crashes my project and I cannot find the file FirebaseBundle.php which is referred to in the AppKernel.php.
I don't know if I'm clear enough but I'd love if you could help me out !
Thanks for your bundle and the sdk anyway ! :)
The text was updated successfully, but these errors were encountered: