I want to clone an existing Firebase project, lets name it ProjectA that previously exists on Firebase console with some Remote Config data to another new project(without any Remote Config data), lets name it ProjectB.
The idea behind my question is that currently I have developed an Android app that is using the google-service.json(Firebase configuration file) file from the ProjectA, so I want to create/clone a new Firebase project ProjectB(NOTE: I don't want a new Firebase app on the same project) that starts with exactly the same Remote Config data from ProjectA and then add the google-service.json from the new ProjectB to my new Android app.
I have read the firebase-cli documentation but looks like it's out of its scope.
Has someone accomplished something similar like this or has an idea how can I accomplish this? Thanks in advance!
I just created this ruby gem to automate the manual process that I needed to do from a web browser for cloning my remote config data from ProjectA to a my new ProjectB.
NOTE: The gem is really an alpha version and just consider remote config without any rules. If some of you want to fork it and improved please feel free to do that.
There is currently no way (neither through the Console or through an API) to create a project that is a clone of another project. At the moment you will have to re-create the config data in the new project manually.
Firebase documents a flow to move data between projects here:
https://firebase.google.com/docs/firestore/manage-data/move-data
Though the method they outline requires a billed account.
Related
Most of our client projects have a very similar starting point:
Pristine AWS account used only for a single environment for this application
GraphQL API and a basic model to start with
A REST API with an OAuth handler endpoint and a generic webhook listener endpoint, each with a corresponding Lambda function (with code for each)
I've created this basic amplify app and I want to create a repo with this general structure as a starting point for future projects. The idea being that I'd copy the contents of the repo when starting a project and build from there.
So I've copied the entire amplify directory over to a new location, removing everything that is in the amplify section of the .gitignore file, and I have a folder structure like this:
My steps to start a new project are:
Create a new directory
Copy the template repo files into this directory
run amplify init
Once I do that, it creates two additional files:
amplify/.config/project-config.json
amplify/team-provider-info.json
Then, I try to do amplify push -- but I get No changes detected.
I'm not even sure if what I'm doing is possible -- I was wondering if anyone else has tried this?
i am trying to deploy my project on firebase hosting. And whenever i am using firebase init it is showing error in terminal as "firebaserc already has a default project " and it exit with that error
i have tried firebase logout and firebase login again . And used "firebase use" command also to change the project but it is still performing the firebase init action on the default project
i want to remove that default project
If you look very carefully at the messaging, it's saying that the name of the file is ".firebaserc" with a leading dot. This file indicates that firebase init was already run in this folder, and the contents of that file describe which project it's connected to (flairboat-48f7b). If you no longer want that file, delete it and start over. Since it starts with a dot, it might be hidden from normal view, but you can be sure that it exists.
you should write:
firebase use --add
and it work! You get the option to choose the preject from firebase.
I ran into the same issue.
Due to a small mistake in setting up the project in firebase, I had to delete it.
But later, I realized that my application NEEDS the default project to be hosted from firebase.
Since I found no shortcuts and running out of time, I did "this" to fix the issue in 10 minutes...with a 5-Step-Process. This is not a "Clever tip". But if you want things up and running soon, you can try this...
Create a new project (in my case, it's React project in VS Code IDE) using - npx create-react-app newprojectname to create a new react project with a different file name.(Don't delete or replace your previous project yet... )
While the new project is being created, create a new project in firebase to host your project.
Copy the folder from your old project that has all your work (it's "src" folder in case of React) and replace the "src" folder in the new project you created in your local machine.
Install all dependencies...Don't forget to add any dependencies you added to you old project. Look at the package.json file of the old project and import all dependencies.
Hit the start command (npm start in my case) and see your project running.
*I'll update if I found some firebase secret to resolve this issue. You can look for the same.
Ensure your firebase project support email and firebase initialize login email are same. If different? It won't be worked. so you must ensure it that two email (firebase project support email and firebase initialize email) are same.
I developped an alfresco share module that allows user to create and save a new workflow. The new workflow files (model.xml, workflow.xml) are stored in a specific folder in alfresco repository. All works fine. Now to finalize my module, i want add a button in my share module to allows users to hot deploying the new workflow and run it on alfresco without restarting alfresco.
Is there a possibility to achieve this?
I thought to call a java webscript from my module to hot deploying the workflow. Is this possible?
If you have an example to how achieve this, it'll be very helpful for me.
I resolved my issue.
So to hot deploy workflow into Alfresco, i used Alfresco Java Api services that allowed me to hot deploy the workflow definition. There is a small code t how achieve this.
InputStream input = contentService.getReader(new NodeRef("YOUR_WORKFLOW_DEFINITION_FILE_NODEREF"),ContentModel.TYPE_CONTENT).getContentInputStream();
workflowDeployment = workflowService.deployDefinition("activiti",input,MimetypeMap.MIMETYPE_XML);
I have a predefined SQLite database and want to ship it with my App, so I can access it at runtime.
How do I achieve this?
Moreover, I want to Unit Test my app. So far the database file is referenced with the Unit Test Project as basis. Hence, my paths get broken.
How do I test a app like described above?
I've answered to the similar question at MSDN forum. It may help you.
I'm creating UWP app with SQLite.Net-PCL I already have a SQLite db
that I want to use (I do not want to create a new one in the app).
I've copied it to the root of my project folder. How do I access it?
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/b6d7a970-0088-4bd4-aaa8-c86bca4387df/
I want to clone an existing Firebase project, lets name it ProjectA that previously exists on Firebase console with some Remote Config data to another new project(without any Remote Config data), lets name it ProjectB.
The idea behind my question is that currently I have developed an Android app that is using the google-service.json(Firebase configuration file) file from the ProjectA, so I want to create/clone a new Firebase project ProjectB(NOTE: I don't want a new Firebase app on the same project) that starts with exactly the same Remote Config data from ProjectA and then add the google-service.json from the new ProjectB to my new Android app.
I have read the firebase-cli documentation but looks like it's out of its scope.
Has someone accomplished something similar like this or has an idea how can I accomplish this? Thanks in advance!
I just created this ruby gem to automate the manual process that I needed to do from a web browser for cloning my remote config data from ProjectA to a my new ProjectB.
NOTE: The gem is really an alpha version and just consider remote config without any rules. If some of you want to fork it and improved please feel free to do that.
There is currently no way (neither through the Console or through an API) to create a project that is a clone of another project. At the moment you will have to re-create the config data in the new project manually.
Firebase documents a flow to move data between projects here:
https://firebase.google.com/docs/firestore/manage-data/move-data
Though the method they outline requires a billed account.