Re:Introducing Cloud Functions for Firebase
by inlined on Thursday March 09, 2017 @02:00PM
(#13831973)
If you need more than 400 concurrent invocations please reach out to support (not promising whether or not we'll be able to satisfy arbitrary scale just yet). We're on day one of a Beta product and it'll keep getting better.
[ Parent
| on HN ]
Re:Introducing Cloud Functions for Firebase
by phpencil on Thursday March 09, 2017 @02:05PM
(#13832042)
And just to clarify, Cloud Functions for Firebase is covered under the Firebase free support, who you can reach here: https://firebase.google.com/support/contact/troubleshooting/
Re:Introducing Cloud Functions for Firebase
by dorianm on Thursday March 09, 2017 @03:27PM
(#13833195)
"You have 5 questions remaining"
Limit is 5 per year, that's brutal
Re:Introducing Cloud Functions for Firebase
by ealexhudson on Thursday March 09, 2017 @04:22PM
(#13833814)
The support comes from a genii. Make sure not to ask "Is the limit really 5?" with your first question.
Re:Introducing Cloud Functions for Firebase
by joshschreuder on Thursday March 09, 2017 @05:27PM
(#13834418)
Just ask for an infinite number of support questions
Re:Introducing Cloud Functions for Firebase
by CamelCaseName on Thursday March 09, 2017 @07:12PM
(#13835126)
Support: No.
4 questions remaining
Re:Introducing Cloud Functions for Firebase
by brillyfresh on Thursday March 16, 2017 @12:58AM
(#13882641)
What is the airspeed velocity of an unladen swallow?
Re:Introducing Cloud Functions for Firebase
by phpencil on Thursday March 09, 2017 @04:35PM
(#13833948)
5 troubleshooting, unlimited bugs and feature requests -> https://firebase.google.com/support/contact/bugs-features/ there. We're on Stack Overflow/the firebase-talk google group/slack etc. as well for general questions of course!
Re:Introducing Cloud Functions for Firebase
by pier25 on Thursday March 09, 2017 @05:05PM
(#13834225)
Can confirm. The Firebase team is monitoring StackOverflow constantly. I've had answers in as short as a few minutes.
Ooh, I like that phrase for the front line of triage. "Is this troubleshooting, a bug report, or a feature request?" I kind of wish GitHub issues separated things that way, too.