Git Product home page Git Product logo

Comments (5)

jeromegamez avatar jeromegamez commented on July 22, 2024 1

You're right, at the moment you can only use one Firebase project with the package - it's on my bucket list, but unfortunately, I can't give you an ETA on when I will be able to get to it, and there are a couple of challenges to make it work with Facades and multiple aliases. Thank you for taking the time to tell me that there's an actual need for this!

from laravel-firebase.

jeromegamez avatar jeromegamez commented on July 22, 2024 1

The package is indeed just a wrapper, but with helpers that make dependency injection and working "the Laravel way" easier (Facades, Aliases).

It's a general purpose package that is enough for the majority of projects - if you have special requirements (like, at the moment, access to multiple Firebase projects inside one backend application) you're far better off implementing this specifically for your application yourself. The advantage of the current package is that it's easy to set up: one environment variable and you're basically set. This structure would not be well-maintainable with multiple projects.

My recommendation: look at the ServiceProvider of this package to see how it configured the underlying SDK and re-implement it - dynamic configuration with different credentials is far in the future of this package - if it comes at all 🙈

from laravel-firebase.

Hillcow avatar Hillcow commented on July 22, 2024

I see. So for the moment I have to fallback to the standard Firebase admin SDK for PHP with my Laravel app, right?

Actually I don't even need this feature right now, but I will need it in like 2 months time. Just to let you know, some motiviation 😄 Thank you!

from laravel-firebase.

sooxt98 avatar sooxt98 commented on July 22, 2024

Same here, is there any workaround for this issue? What's the diff using laravel's one v.s. the php one, for me i think the laravel one is just a wrapper but it seems to be more complex when i look into the code. i tried to google but still not sure how to deal with dynamic firebase json config in service provider; I'm planning to store the json into the database, i just need some guide :3

Bonus question: why there's a need to add an extra resolveCredentials func in service provider

from laravel-firebase.

github-actions avatar github-actions commented on July 22, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from laravel-firebase.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.