Currently, we have an application in production using firebase. We have a project per environment: develop and production.
I have seen that we can create multiple databases and we can have multiple hosting sites. Which makes it perfect to create multiple environments in the same project.
The issue is that in develop environment we have multiple people(DEVELOPERS) with editor access to the database. In production, we want that only one person have access.
If there a way to restrict permissions per database?
While it is possible to restrict what Firebase features a collaborator can access within a project, the level of granularity you want is not. There is no way to give a collaborator on a project different level of access to different database instances in that project, or to different hosting sites.
The common way to set up the multiple variants is by creating a separate project for each of your develop and production apps.
Related
We use our Firebase real-time database as a read-only database for our users using the firebase real-time database rules. We use the same databases for all our applications. These databases reside in the project "database-project". Our apps have individual projects, e.g., project X, project Y, and project Z. This seems to work now because anyone can attach to our real-time databases using a reference string e.g., https://our-realtime-database.firebaseio.com/. Would it be possible to restrict access so that only the projects mobility-inside, project Y, and project Z would be able to access these databases? Or, is there another way to structure our setup so that we have one database that is shared over multiple projects with access somewhat restricted?
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.
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.
How can we move our existing ASP .Net 2.0 application to the cloud platform ?
What all changes are required in existing application at code level as well as database level ?
Update: I have one ASP.Net 2.0 application with SQL 2008 database. I want to deploy it on the cloud environment with multi-tenancy support.
In that case what changes are required. Currently 'ConnectionString' is configured in web.config file. How to change the code/ database to achieve multitenancy support.
Basically I am looking for steps to move existing ASP.Net application to the cloud platform.
Please suggest resources for the same.
I am not sure what you mean by multitenancy suppport. Multitenancy usually means that you will need to work on your application and segregate the data for different organizations. Not sure what the cloud has to do with this. If you are expecting to just spin different instances for different organizations you will have to do work again with the API of the cloud provider in question. Some of them can manage applications and instances automatically.
Cloud provides scalability and elasticity (automatic scalability) it does not provide mutltitenancy by itself. To achieve maximum scalability you may need to use cloud data store (usually key/value) and let go of relational databases. This may require serious rearchitecturing of the application. Whether you need this scalability and elasticity is another topic and you may just use the cloud as infrastructure (i.e. they will manage the servers for you)