Base-Project | Basic Project Borealis UE4 project files

You don't need to implement the communities solution that is described in that link anymore.

According to this:

Sometimes you need to access different projects using the same APIs - for example, accessing multiple database instances. In most cases there is a central Firebase application object that manages the configuration for all the Firebase APIs. This object is initialized as part of your normal setup. However, when you want to access multiple projects from a single application, you’ll need a distinct Firebase application object to reference each one individually. It’s up to you to initialize these other instances.

you need to first create a Firebase options object to hold the configuration data for the Firebase application, like this:

Just run docker run --help in your shell.

-w, --workdir string Working directory inside the container

https://docs.docker.com/engine/reference/run/#workdir

The issue looks to be inside your getAllUsersOnFirebaseAuthentication Cloud Functions code.

The way to make sure you are referencing the first or second Firebase app is to provide the specific FirebaseApp instance as a parameter to:

FireDatabase.getInstance().setPersistenceEnabled().

If you use FirebaseDatabase.getInstance() you will receive the default instance, the first database app. So just provide the second instance as a parameter and you'll be good to go.

In order to create a Google Task you have to add the correct permissions on IAM, in this case as the error message is showing, you have to add the cloudtasks.tasks.create permission to the service account that is invoking the Cloud Function.

This can be done by going inside the Cloud Console and then into IAM, search for the service account usually is something like service-project-number@gcf-admin-robot.iam.gserviceaccount.com (update: it was my-project-id@appspot.gserviceaccount.com) and add the required permission, if you have a role based permissions Cloud Tasks Enqueuer should be enough to create the tasks.

You have to add the role at the cluster level using oadm policy add-cluster-role-to-user cluster-reader system:serviceaccount:myproject:default

According to this comment in GitHub it cannot be done without a "hacky" method like swapping the firebase.json programmatically during deploying.

Right now the Firebase CLI is built to treat projects as anonymous environments that are functionally identical. This is important to be able to deploy the same assets to multiple projects without having to alter the code (including in firebase.json).

To achieve what you want, you'll need to set up a dev and prod folder, each with their own firebase.json and each with a target only for that specific project. Deploying different assets to different projects is not supported now and is unlikely to be supported in the future (however, we may allow configuring the location of firebase.json via a flag at some point).

In reference to @Doug Stevenson's post here, req.headers['x-original-url'] works!

Console output:

You can use the Firebase REST API to generate an id token, server side. https://firebase.google.com/docs/reference/rest/auth