PWA Tutorial for Beginners #29 - Deploying to Firebase

Hosting on Firebase – PWA Tutorial for Beginners #29 – Deploying to Firebase


PWA Tutorial for Beginners #29 – Deploying to Firebase

Hosting on Firebase

Hey gang, in this PWA tutorial we’ll finally deploy our app to Firebase hosting.

—————————————-

🐱‍💻 🐱‍💻 Course Links:

+ Course files –

+ Modern JavaScript Tutorial –

🐱‍💻 🐱‍💻 Other Related Courses:

+ Firebase Firestore Playlist –

Firebase Authentication Tutorial –

you search:

Hosting on Firebase

PWA Tutorial for Beginners #29 – Deploying to Firebase

21 thoughts on “Hosting on Firebase – PWA Tutorial for Beginners #29 – Deploying to Firebase

  1. Great tutorials but while following your steps to publish, github hijacked the deployment:
    "For which GitHub repository would you like to set up a GitHub workflow?" I opened a github account, entered my repository name: 404 error. How do I deploy the app (with or without Github)?
    Thanks

  2. First of all, thanks so much for sharing your knowledge.
    Second, I have a question. Once the web app is hosted, how can I update the files when making changes?
    I'm changing the service worker file version, but when refreshing the browser, it keeps showing the previous service worker version

  3. i downloaded your files from 29 lesson and i deployed them and i have Failed to load resource: the server responded with a status of 404 (), what should i do?

    in mozilla I have :
    @firebase/firestore: Firestore (5.11.0): Could not reach Cloud Firestore backend. Connection failed 1 times. Most recent error: FirebaseError: [code=not-found]: The project net-ninja-pwa does not exist or it does not contain an active Cloud Datastore or Cloud Firestore database. Please visit http://console.cloud.google.com to create a project or https://console.cloud.google.com/datastore/setup?project=net-ninja-pwa to add a Cloud Datastore or Cloud Firestore database. Note that Cloud Datastore or Cloud Firestore always have an associated App Engine app and this app must not be disabled.
    This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.

Leave a Reply

Your email address will not be published. Required fields are marked *