I am using the spark plan for firebase, meaning that I have a limited number of apps allowed. I decided to delete the majority of them, but accidentally clicked "delete project" before I clicked "delete app". Now I have a bunch of apps counting toward my limit but no place to delete them from.
I have already tried going into different projects, general settings, and whatnot, as well as googling the problem and checking stack overflow. There doesn't seem to be an easy way to deal with the issue.
You could restore your Firebase project, delete the app from it, then delete the project again. If you have problems with this, you can also reach out to Firebase support directly for assistance.
Related
I have a Firestore collection that I need to rename.
To do that I'll have to do two things. One, rename the collection, two, update my app (only web right now) to use the new collection name.
My problem is that if I just go ahead and do that, any user that has not refreshed the app won't be able to find the renamed collection.
So, my question is: Is there any best practice to handle this scenario?
I can think of a couple of options:
Somehow forcing a reload of the web apps immediately after renaming the collection.
Set a feature flag so that the web apps enter into maintenance mode while I update everything and then reload the web apps once the change is finished. Unfortunately the currently deployed web app doesn't have a maintenance mode to enable so this doesn't seem to be a valid solution.
However, I'd like to hear about other options. There might be some best practice that I'm missing. Moreover, I'm aware this is a problem that might be more general than just related to Firestore. For example when changing a REST API endpoint, so I guess there must be some tried and tested solutions out there.
I tried searching for best practices regarding this and couldn't find any.
Also, if I was consuming a REST API it would be easier to solve because I could change the DB and keep the DB unchanged. But given that Firestore gets consumed directly from the web app I don't have this benefit.
Locking out outdated clients is a common practice, but leads to a lesser user experience. It also requires that you have a mechanism for the clients to detect that they're outdated, which you don't seem to have.
The most common practice I know of is to perform dual writes to both the old and the new collection while clients are updating.
Is this perhaps some firebase demo project or is my account being hacked? Could it be that someone have given me access to their project? If so, shouldn’t I have gotten an email at least? I have never given anybody access to my account.
Went to my Firebase today and there is a project name Alfatawa with 14 users. What is worse, I can not delete it. I goggle searched that name and nothing came up. I asked Firebase support for help just now but I was wondering if any of you have experienced anything like it.
This is the response I received from Firebase Support:
"You are seeing the project Alfatawa because the Google Group 'firebase-talk#googlegroups.com' was previously listed as a project member. Project Owners are allowed to add Google Groups to their projects, and anyone who is in the group will be able to access the project. You should no longer be able to access it because the project owner was able to remove the group as project member.
In case this happens in the future, the fastest way to be certain the project is removed from your console is to leave that group.
Do know that while this project shows up on your console, you are not responsible for it, and it will not charge you. There is no impact from having this project on your console. You could simply ignore it, and not looking at any data it may contain."
This means that somebody added you to the project, typically by adding a group that you're a member of.
The only ways to remove the project are:
to be removed from the group.
to get a project owner to remove the group from the project.
This project is no security risk for you, as nobody in the new project can see any of your existing projects.
I'm really keen to use the 2sxc environment on my website for a number of applications.
I'm currently looking at the Mobius forms.
What I'm wanting to do is create a ticket in ConnectWise rather than send an email, using the ConnectWise REST API.
Some of these questions might have obvious answers to someone who has been taught in these technologies, but I'm self-taught. When I went to school I learnt COBOL!
There is c# code in the application, but I can't see how you build and incorporate into the application. I forked the code and it seems to just code with no build.
There are live and staging folders with the same cshtml files. However, it seems a bit random when the live or staging is actually used. For example, I did a quick fix to the _Contact Form.cshtml so to fix the type that meant it always displayed the ReCaptcha warning, and I changed the live version, which didn't do anything, so I had to change the staging version.
I need to update the settings so that configure the ConnectWise API settings, I haven't been able to find where I can do this? I am still looking though.
I also need to store a private key in the settings. Is there a secure way I can do this?
PS. When I get my head around all this I'm happy to be a contributor
welcome to StackOverflow.
I'll try to give you some guidance to help you figure it out
Live and staging are folders meant to let you make changes while the users see the unmodified output. So a host-user sees the files from staging, others see what's in live. When you're done and all is tested, you copy from staging to live. This we call Polymorphism.
Polymorphism applies to both the cshtml as well as the api. So as a host-user, you'll be using staging/api/FormController to save/send.
There is no build process, everything is hot-compiled. That's one of the things that makes 2sxc so amazing. No Visual Studio, DLL or restarting the application ;) You'll love it.
Secure keys: there is no special secure key storage. We usually put it in the App-Settings, just like the MailChimp key you'll see there. We split it into two fields for very technical reasons, because we publish our code on github and that causes trouble when our code has API keys. But you can just use one field, assuming you don't plan on publishing the code on github.
Firebase has very annoying interface to work with issues. There is no option to move to specific issue in cluster etc.
Is there any way to export crash reports from Firebase Crash Reporting section? Or may be you can give me a hint how to move to specific issue in cluster instead of clicking all issues one by one :).
I've got a Meteor app hosted on Modulus. The app is an in-house app used by a few higher-ups in the company. We're giving it a first trial run. After deploying the app and the db to Modulus, I'm finding the data is reloading about every 10 seconds. It's like the data is reloading into minimongo, so same data appears to flash on and off. It doesn't do this running the app locally.
Insecure has been removed, but I left auto-publish in Meteor because the app needs the whole database to work with. I figured I could remove it and then publish and subscribe the whole database, but I thought that would be redundant. Could this be the problem?
I'm in contact the the Modulus folks about it, but I think they're scratching their heads. I've tried hosting the db on Compose as well with the same result. Something in the app is causing it. Was wondering if anyone might have a suggestion.
Autopublish is the culprit here. Try removing autopublish and convert your data access to publish and subscribe.
If you have already built the entire app, you will have to refactor the entire app as Thai Tran mentioned in the comments.
Also, even if you have every security in place where users are locked up, autopublish still messes your app's security up. Your entire database is on the browser. Even if you have users or not. (Not a best practice in a production app).
Meteor gives autopublish only for prototypes, not production apps.
Anyways, explanation here is with autopublish on there will be lot of Tracker incomputations which might cause these errors.
Remove it and your app should be fine (Of course after you refractor your app to use publish + subscribe).
Good Luck!