pud at February 14th, 2018 20:35 — #1
Just so everyone's aware, Firebase is going to stop supporting legacy databases such as what webhook is built on. They're entirely dropping support for them on April 17th, and deleting all of them come May 15th.
I hope that as a paying customer, I'd get some sort of notice from the team, but I doubt that's going to happen, so this is I suppose the swan song so you're all in the loop.
@davesnider @LtSquigs @gpbmike
Against all odds, I don't suppose you have a migration strategy to Firebase? Knowing that the CMS itself has a legacy component that doesn't support Firebase 2 or greater, and that updating that legacy component would effectively require a rewrite of the CMS.
If any if you guys could kindly comment on this, I think it would be a good show of faith to let your customers know that this is shutting down, or if not - what is the migration strategy.
pdkn at February 15th, 2018 09:38 — #2
Do you know what the 'legacy component that doesn't support Firebase 2' is in reference to?
pud at February 15th, 2018 10:09 — #3
Last I looked at this, CMS is using an older version of EmberJS, and using emberfire as the framework to do all firebase communication. The version of emberfire being used only supports Firebase 1.2;
To upgrade emberfire to support new Firebase, EmberJS would have to be upgraded as well, to a breaking version upgrade.
I found another comment where I mentioned this a few months ago: http://forums.webhook.com/t/self-hosting-problem-firebase-is-saying-that-my-webhook-json-has-problems/1160/5?u=pud
pdkn at February 16th, 2018 06:02 — #4
Alas, I don't hold out much hope for the founders to fix this as it sounds like, A) they don't have the time and B) The effort involved may be greater than the return ;( Auspiciously I just had netlify.com in the building yesterday talking about JAMStack and Static Site Management. They also have a CMS netlifycms.com. I was very impressed. My plan would be to re-platform to netlify.com and contentful.com. However I too don't have the time to do this for the webhook project I manage within the next month ;( I'd be happy to limp along with current setup if there was any hope of fixing it. It would be a disaster if the service just gets shutdown without any warning. The founders might not be doing any active development but they have responsibly to explain what their plans are and either fix it or help people migrate off the platform. I expect they are talking amongst themselves to decide what to do at the moment. We're eagerly awaiting your response @davesnider @LtSquigs @gpbmike
davesnider at February 16th, 2018 10:22 — #5
I sent over an email to Google. As far as I can see from their messaging (please correct me if you have other information) this shutdown is strictly for accounts that have not moved over to the GCP platform (of which Webhook did last year). I don't see anything on their site or docs that say they are dropping support for the API. I'm following up with them to be more clear.
To answer the more direct question. You are correct in assuming that we don't have the time to dedicate to a major software rewrite. Webhook has not been actively developed for a very long time now, and there aren't very many sites running on it.
Off-hand if they did shut down the actual APIs we'd likely do something along the following.
- Stop subscriptions so that people don't get billed.
- Put up some sort of warning on the CMS / login page.
- Shut down the webhook.com site
- Continue to allow the static sites to be online for a bit. That way people would have a longer grace period.
I'll update when I hear more from Google, but in the meantime I'd love to see where you got that information, because all I got was an email about moving accounts off of Firebase to Google (a bunch of my old accounts triggered this, not Webhook). This was the email response I got.
Your project " is already associated with new Firebase Console, that's why it's not listed to the email that you have received about migrating Firebase Legacy project. The project " should continue its services associated with Firebase and it's not affected by the service disruption for Firebase Legacy project.
I wouldn't take that as gospel though. As you know this project doesn't have much future in it, so your most prudent action would be to make backups and move your sites. As long as there's a low-friction way to keep the lights on I'll continue to do so to make that easier on you. That's the best I can do.
postscapes at February 16th, 2018 12:31 — #6
Thanks for the response Dave.
I added the email I got from Firebase below for reference. So it looks like the project might be OK if Dave has moved to GCP.
Since joining the Google family 3 years ago, we've made many updates and significantly expanded the Firebase platform on Google's global infrastructure. As such, we're sunsetting the final bits of our legacy infrastructure, and will require you to import your Firebase apps into Google Cloud Platform so that they can be supported as projects on GCP.
Our records indicate that you have legacy firebase.com apps that require action to prevent service disruption and deletion.
The affected projects are: .
To prevent service disruption, please do the following:
Log in with your legacy firebase.com account at https://www.firebase.com/login, where you’ll be prompted to link a Google account
After being redirected to the Firebase Console at https://console.firebase.google.com, scroll to the section titled ‘Your projects currently at Firebase.com’
For each project, click to launch import confirmation. This flow will link each app with a Google Cloud Platform project
This action does not require any code change or change to your application, and will have no impact on the uptime or performance of your application.
If you take no action, these apps will be disabled on Tuesday, April 17th, 2018, and permanently deleted on Tuesday, May 15th, 2018.
If you have any questions or need any assistance, feel free to reach out to our support team for more assistance.
Rob DiMarco on behalf of Firebase
Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043
tracy_tra at February 16th, 2018 17:18 — #7
Thank you @davesnider
I have five websites running on Webhook. Granted, two of them are wanting more than static sites, so I've been in discussion with those two clients as to what they want to do, but this should give me time (hopefully lots of it, as I also work full-time for another company), to migrate everything to a new system.
I have loved the ease of using Webhook and how, for some of my sites, it's been a perfect and inexpensive solution. I'm investigating a few other systems, but I wish there was something like Webhook that was kept up... something that uses something similar to swig.js as that method of templating seems to work well with how my mind works for doing basic development in a system of this type. IF you have any suggestions for something similar, please let me know. Thanks!
Best to you and yours!
ë design studio
pud at February 16th, 2018 20:45 — #8
Thanks @davesnider for taking the time to respond. Hopefully we are okay here for a little while longer still.
pdkn at February 20th, 2018 05:54 — #9
Thanks for the sound advice @davesnider. I'm going to see how easy it is to write a generic script to migrate the cms json to contentful.com. Once done, if it feels like it might be useful, I'll share with other.
davesnider at February 20th, 2018 11:50 — #10
Just a follow up. But Google verified that there shouldn't be a service disruption as long as we're on Google console. Webhook will continue to run in its current form as long as that's the case.
postscapes at February 23rd, 2018 15:57 — #11
Tracy, I did some digging around and am similar position to you and feeling like I need to bite the bullet sooner than later given Dave's comments and never knowing with the next issue is going to pop up.
A few options I have found that are decent paths forward and each with their own set of tradeoffs.
1) Contentful, Prismic and their ilk
4) Timber with Wordpress https://www.upstatement.com/timber/
As far as I am concerned R.I.P Webhook. Unfortunate since it had the potential to be such a great ecosystem.They really should take down new sign-ups at this point...
stevesunderland at February 23rd, 2018 16:02 — #12
Also check out Netlify CMS. It's free, open source, and static.
pud at February 23rd, 2018 19:33 — #13
Anyone have any migration scripts?
My site's got ~5000+ pages and images and all kinds of things, spread across half a dozen content types, all related in various directions.
I can't imagine that's going to be an easy migration...
Not to mention the complex templates
pud at February 23rd, 2018 21:42 — #14
Actually, better yet, anyone willing to resurrect webhook with me? Roll up our sleeves and build some stuff?
I've got a ton already built - happy to get into details if any if you guys are interested
pdkn at February 28th, 2018 13:44 — #15
If anyone's interested I'm now using contentful.com for CMS, gatsbyjs.org for static site generation and netlify.com for hosting (as well as running AWS functions and handling form input). I'm really happy with this set up at the moment.
1: export webhook.com JSON Data
2: set up contentful.com space
3: use Contentful's Migration cli to recreate structure (https://www.contentful.com/blog/2017/09/18/using-the-contentful-migration-cli/). (I don't have a generic version to share yet)
4: usng contentful-migration-cli to load webhook JSON, parse it and mutate it to fit contentfuls scheme then import data into the Contentful space
5: setup a gatsbyjs-contentful project (https://www.gatsbyjs.org/packages/gatsby-source-contentful/)
6: migrate your pages over to gatsby (this could take some work but there's plenty of other static site generators that might be more aligned to webhook if you want to swap out gatsby)
7: set up a netlify.com account
8: just drag a local build folder onto netlify to deploy ( or setup Git for CI )
Example - my webhook site (http://www.inishbeg.com/) is now running on netlify https://hardcore-tereshkova-765686.netlify.com (need to setup DNS)
eduardo at March 1st, 2018 22:54 — #16
I would also recommend Bolt CMS
- Runs on PHP / Sqlite (or MySQL if you prefer), so hosting is dirt cheap and simple
- Open source and very well maintained
- Templating with Twig (similar to the now defunct Swig)
- Highly customizable (like Webhook) to make tailored sites
- Custom fields, repeaters, etc etc
- Active Slack channel with friendly devs