I'm developing a project where I need two PWA apps defined on the same Firebase project, sharing the same database. One of this app is the 'producer' and the other one is the 'consumer' of the data.
So far I developed the 'producer' side and everything is ok - it writes in the database. Now I'm starting with the 'consumer' side.
Defined like now I'm not able to deploy the second one, cause it shares the same hosting so it overwrites the first app.
How can I structure the project to have two PWA apps sharing the same DB but not the same hosting (and URL)?
It sounds like you want to create a second Firebase Hosting site in the project, which you can then deploy to separately.
Related
Im currently working with Mobile app with firebase back end. I wonder how to build another admin Web app which should be hosted on the Web and pass data to the Mobile app. Should i open another project to build the Web app？Or build the both app within one project which should share with one firebase back end. Someone please guide me as Im clueless. Would appreciated for the sharing.
Since the application admin app is managing the same set of data, it will typically be part of the same Firebase project too. This is actually a quite common scenario, and I regularly add an admin web app to my Firebase project precisely for that purpose.
Pretty simple Use-case, clients buy our app and pay 20$/month.
We want to implement push notifications on both iOS and Android and are thinking of a scalable solution.
We thought of simply grouping all Apps inside one Firebase project, as we only need Push Notifications.
Google Firebase FAQ says:
A project is a container for apps across iOS, Android and web. While there is no restriction on number of apps within a project, adding an app can create one or more underlying OAuth 2.0 client IDs. There is a limit of around 30 client IDs that can be created within a single project.
You should ensure that all apps within a project are platform variants of the same application from an end user perspective. For example, if you develop a white label application, each independently labelled app should have its own Firebase project.
Would this limit us?
Do I need a client ID for each and every App inside my project?
firebaser here
What you're trying to do is known as whitelisting, and is not an intended use-case of having multiple apps in a project. To not run into the limitation you've found, you will need to create a separate project for each client.
If you create multiple technical applications for a single client that are logically the same, those can exist in a single project. For example: the Android, iOS and Web versions of an app are typically using the same Firebase project, as may be specific app you build for the application administrators of your client. By having those apps be part of the same project, they can share backend resources.
I am having an app with firebase as database. And i am creating a website with the same data as in app. can i use same database for both app and website. when data update take place in app should also be resembled in website and vice versa
Yes, that is definitely possible. For example, the FriendlyPix sample app is available for iOS, Android, and Web, and all these talks to the same back-end services. So photos posted in one platform show up in all other platforms too.
This is more of a general question about the future of AppMaker I guess... I have a few ideas that I would like to try out - mostly some tools that could help my clients - and I was wondering if there will be a way to deploy an app made with AppMaker to multiple domaine.
A (dumb) example would be to create a Task management app that you can centrally develop and deploy as a Saas service to multiple clients.
I would be interested to hear some insights before investing too much time in this.
Currently, App Maker applications are restricted to the domain of their owner. However, you can export an App Maker application and import it in multiple domains and possibly share the same Google Cloud SQL backend. Keep in mind that sharing the same database will be challenging when it comes to changing the schema since you will have to synchronize updating the applications in the different domains.
I am trying to find the proper way of having two asp projects in one hosting space.
Project 1 The first project deals with the website front end, shopping cart, and creating orders. It uses EF6 Code First from Database.
Project 2 The second project is a scaffolding one using EF5, to connect to the backend and display the database entries, and CRUD operations for the manager.
Both of the projects are working fine individually on the local machine. I have also tested them individually on the actual hosting server, and both are working there individually. Both connect to the same database.
Problem Now I am wondering how I can deploy these two projects together on the same hosting space. I am not sure what it is called technically, but what I want to achieve is to have the website available for the end users, and the scaffolding be available for the manager. Both the projects are not using any kind of authentication, and I am interested in putting these to work before having an authentication mechanism for only authorised access to the scaffolding part.