Open jasonkuhrt opened 8 years ago
Thanks for these, I'll go check them out. Any preferences off the bat?
I wonder if they all serve our pushstate requirement out of the box.
Any preferences off the bat?
Surge / Firebase / Netlify all appear solid. I suggest we try each of these, even in parallel. Firebase might have an edge if the hosting service dovetails into its realtime DB and user accounts system nicely. For what its worth to us, assume Firebase is the most performant given it is Google powered.
I wonder if they all serve our pushstate requirement out of the box.
All the tailored services cover this and much more (TLS, CORS, etc.), but S3/GAE will need a few configuration steps.
It looks like we won't be able to do clean pushState routing with GCS actually but S3 is still an option. Google App Engine (GAE) is also an option. Using a Cloud Provider is a good learning experience but given our limited time its fat we can cut out of our process at least for now, meaning, lets try with the boutique services first, I think.
Surge / Firebase / Netlify all appear solid. I suggest we try each of these, even in parallel.
Great. Sounds like a fun way to start. parallel tire kick.
I'm interested to see how they feel in comparison to the Heroku w/ a server.
After trying Surge, Firebase, and Netlify, here are some observations.
ping
... TBD investigate?Some time has passed and we now have more notes.
Custom Domains are now free!
For Hosting, custom domain support is now free for all developers, and the Database has a completely rebuilt UI. We’re working hard on other great Realtime Database features, stay tuned for those.
We should have a good system for deploying static sites. Known candidates for this are:
Google Cloud Storage