aaron at May 20th, 2016 08:38 — #1
I see that a new version of Firebase has been released. Will this affect how webhook sites work?
dkenzik at May 21st, 2016 15:32 — #2
For others who wander in and see this, here is of what @aaron is speaking.
I do not believe it will adversely impact Webhook. I see no mention of API breaking changes in the announcement article.
vibes at September 6th, 2016 19:22 — #3
Hello! I am running into an issue using the updated Firebase.
We're trying to get a self-hosted instance of Webhook going and are running into an issue.
After following the instructions, when we run
wh -f -s create www.yoursite.com
we're receiving the following error:
Projects created at console.firebase.google.com must use the new Firebase Authentication SDKs available from firebase.google.com/docs/auth/
Do you know how we could update the authentication method?
Thanks in advance.
dkenzik at September 12th, 2016 13:44 — #4
Webhook does not support the new Firebase. Not only are there authentication changes needed to the codebase, there are also some deprecated functions.
The old Firebase will be supported for a long time.
If you are setting up self-hosted Webhook, you should create your Firebase using the legacy console, which you can login to by visiting firebase.com.
adamdabrowski at October 10th, 2016 12:53 — #5
Unfortunately, new users can't access the legacy console.
ikaika at May 11th, 2017 01:16 — #6
Uh oh. Does this kill the ability to self-host?
ruben at May 30th, 2017 17:50 — #7
It does not kill the ability to self-host. You can still find a Web API Key under the project settings. You can find it by clicking on the gear next to the
Overview button, and going to
Project settings. Use this as the firebase secret in the Gruntfile that is used for configuration in the webhook-server-open repository.
nickittenpierre at July 15th, 2017 05:01 — #8
Flagged content temporarily hidden.