Quiet out there.

[Michael Abele]

Notice it's been kind of quiet in the Firebase world lately... The blog use to be quite active but haven't seen anything since late May. 

Plus whatever happen to Firebase triggers? 

Just curious...

[Douglas Correa]

There are some good tweets on https://twitter.com/firebase, but I'm also missing news about Firebase Triggers.

Douglas

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/d8f8f8ab-38d9-4b15-9377-c0bf08f48e53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kato Richardson]

Gents,

There is nothing to report, other than a triggers-like enhancement has been under development for several months. It's a cross-team effort at Google with a lot of muscle and talent behind it, and I think you're going to be very happy with the outcome.

No public release date has been announced and none of the specifications have been published, so I can't share more yet. Hang in there; great stuff is coming.

We did a slew of blog posts at the end of May, and we've been posting lots of news on Twitter. We'll have some more blog posts out this month.

Cheers,

Kato

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAPUi1p0AtC5iXZtjEt6773VuBh-VwUMm7ZFQ7VYnVd1zHMg-1Q%40mail.gmail.com.

[Michael Abele]

Cool! Glad to hear triggers are still a priority. Thanks for the update. 

[Hardeep Singh]

Kato - we are also waiting to hear about server-side code hosting within FB (cloud code in the world of Parse).  Can you shed any light on this? 

[Kato Richardson]

Hardeep, in Firebase vernacular, that's the same as Triggers--both of these describe a server-side scripting functionality that would be invoked based on changes to data.

☃, Kato

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/78bd4668-3982-4845-9f34-e0591a07a0b6%40googlegroups.com.

[Hardeep Singh]

Okay cool!  The way you are describing it makes it sound like Triggers would process FB Queue Tasks as well.

[Kato Richardson]

I don't have a specification I could share, but I think it's safe to assume that taking an action when data changes occur is a given. So in that regard, it makes sense that you'd be able to process, alter, or otherwise interact with a queue.

☃, Kato

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/b4f7608c-a6c1-4ea7-ad7f-5c2107df59d8%40googlegroups.com.

[Douglas Correa]

Right now, I'm using a node box for doing "server code" using a modified version of Firework (https://github.com/mjackson/firework) (the firebase queue was not there when I started).

But it is very painful to scale and control which node will process that server code.

I'm glad to hear that Triggers are coming, it will transform Firebase in my perfect fullstack :)

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/b4f7608c-a6c1-4ea7-ad7f-5c2107df59d8%40googlegroups.com.

[Kaue Machado]

I was thinking exactly the same thing, but its great to hear that a major feature is coming

[Kathryn Cullen]

Hi all,

 

Plus whatever happen to Firebase triggers? 

See my post from Friday about signing up to come talk to us about your needs regarding triggers. I'd love to hear from you!

Kat.