3 ms·
Firebase here as well. Why I like it: -CLI makes it easy to use. -Deploying to the internet is as easy as "firebase deploy" -Comes with HTTPS for free and w
by leon_sbt 9y ago
Firebase here as well.
Why I like it:
-CLI makes it easy to use.
-Deploying to the internet is as easy as "firebase deploy"
-Comes with HTTPS for free and with zero config
-Automatmagically uses Firebase's CDN
-Can serve with your custom domain name
-Low cost (for my needs/traffic levels)
-(Mostly)Straightforward documentation/references
Pain point(s):
-Slightly fragmented documentation. This was only one instance, so I might be blowing it out of proportion.
I wanted to have Clean URLs in my website, there was no mention of that capability in the Firebase docs -> "Customize hosting behavior".
But the only instance I found this feature was from a random Firebase blog post from 2 years ago.
https://firebase.googleblog.com/2015/12/a-host-of improvements_61.html
-I can't view the contents of what I'm hosting from the web based (At least I tried to, and can't figure it out.)
-Deploys can be slow(30 secs -2 min), but honestly I should setup a CD pipeline and stop staring at it while it's deploying.
I originally was going to use Google Cloud Storage, but they don't support HTTPS out of the box.