I'm trying for several days to deploy my site with Firebase. I'm using Ubuntu 16.10, but still no change. Everything worked with me fine, deploy completed successfully, but I don't know why I can't see my site on!
Any suggestions!
I had a similar problem and it turned out that I was deploying to a different alias of the same project. You can have many aliases within a project (i.e. versions of the same project) , but only one alias will be visible to people visiting your site.
Entering firebase use <alias_or_project_id> in terminal will let you set the alias name you'd like to use.
To deploy that specific alias, run firebase deploy --project <alias_or_project_id>.
I had the same problem and it turned out my browser (chrome) was just caching the old site. Clearing the cache and hard reloading fixed the problem. Hope this helps someone.
Related
Hello my dear developers. Help me plz with that question.
I have Laravel api application and nuxt 3 as a frontend application.
With Laravel i had no problems with deploing but with nuxt...
So as documention says i need to run nxp nuxi generate command. But its creates fully static site, and its working but api calls not really works.
I want to deploy on my server that has linux and other required thinks also installed (..etc node)
I want to deploy it via ftp. That some pages are static but some pages are requests data from api when we update the page.
How can i do it plz.
I tryed npx nuxi generate.Also with ssr false in nuxt config file.
I tryed npm run build. But its says just error.
Thank you for reviewing my question and comments to it.
So i used npx nuxi generate and also i putted ssr false in nuxtconfig
The i pushed .output/public to my server via ftp.
And everything works great.
In future i want to add some pages in nuxtconfig to preload them. So they will be fully static. Hope i can do it. (i`m still learning...)
The problem that confused me, is that when i did it first time, its loaded with fetched data, and when i tryed to change data. I could see any errors. And when i made my database fully emty it still showed data. But when i tryed to do it now, it works. I dont really understood why. Hope maybe it will help someone. Becouse its not really enought info in interner. Or im just a bad googler xD
Peace to everyone
Since you seem quite new, I recommend that you stick to:
vanilla Vue3 app
hosting on Netlify
When you'll be more comfortable with those, then you could proceed hosting a Nuxt3 app on your own VPS.
I hosted my web application through Firebase using Flutter. Initially, it was absolutely fine but I realised there was a small error so changed it an redeployed it. However, when I ran flutter deploy it didn't change on the website. I thought that I might have to wait a while for the change to happen but I waited 5 hours and it still hasn't updated. I then tried a few more times, deleting different cache files but nothing worked. I then deleted the Firebase project all together and made a completely new one. I deleted the .firebaserc and firebase.json files. However, on the new website, it is still showing the old version of the website. I don't understand how that could be possible but any help would be really appreciated!
Visit your site from an incognito tab and validate. Also make sure you didn't forget to run flutter build web before firebase deploy.
I followed the instructions, and deployed a simple web yesterday. At first, it kept showing the default website, saying " you've deployed successfully...", not my web.
Also, the 'firebase open' command + "Hosting: Deployed Site" leads to a undefined site:' undefined.firebaseapp.com '.
But, magically, about an hour later when I open the link from 'firebase console' again, the web showed up... I am not sure whether 'firebase open' command worked cause I didn't try.
Today, I added some features, and deployed again. In the firebase CLI, it said deployed. But, the link still showed the old version.
I'll catch up an hours later to see whether it works, but even it works, it takes too long.
has anyone had the same experience? what's wrong with my web?
Thanks.
This is how I solved this issue for my angular 7 app deployment on Firebase hosting:
ng build --prod
go to dist/myproject and run command Firebase init and...
I went to dist/myproject that now contain build files along with Firebase related files. Copy all files except Firebase related files to dist folder in side dist/myproject.
there you will get overwrite warning just select overwrite option.
after copy process completes, run command Firebase deploy.
after completion of process go to shown URL and there you will find your running app.
To deploy a meteor app, you enter meteor deploy my_first_meteor_app.meteor.com
To update the deployment, is there a faster way than typing the above command again? It's quite tedious if you have a long domain name like the one in this example.
Yes. You can user aliases (nothing to do with Meteor). This is how you do it on a Mac:
alias new_name='command to be performed'
After which you must store the changes permanently in the file:
~/.bash_profile
See a full explanation here: http://www.maclife.com/article/columns/terminal_101_creating_aliases_commands
Also, you can try running meteor deploy without the site name. I don't remember if that works or not though. meteor deploy does remember old settings files that were used, but I'm not sure if it remembers the site name you used too.
I have been using meteor for quite awhile and have been deploying apps to .meteor.com. However recently after updating my app to meteor v0.8 and new collectionFS, the terminal states that the app has been deployed to whatever.meteor.com but when I go to the site, I see Meteor's Site is down.Try again later. I have narrowed it down to the new collectionFS package causing the problem, since my old app with the old collectionFS deploys fine. Any thoughts?
EDIT
The problem was due to the long startup time caused by my collectionFS path: definition.
There are several reasons why your site may not load when being deployed.
Site Inactivity
The meteor deploy service shuts down if your site hasn't been accessed in a while, and takes a while to start up again if it is requested, during which time you'll see that message.
In a few minutes after the first request, you should see the site come back up.
For more information, see this answer: https://stackoverflow.com/a/19072230/586086
Excessive Resource Use
Another reason your site can refuse to deploy is if your app takes more than 4 minutes to start or uses an excessive amount of CPU - it will get killed. Is it doing anything resource-intensive like that? For initializing really big databases, do the initialization locally and copy the contents using the url from meteor mongo -U yoursite.meteor.com.
I had to do this for the demo app for meteor-autocomplete. See the file upload-db.sh.
I had the same error.
But the following solution works deploying the app successfully.
meteor login
meteor deploy < available meteor sub domain name >
I know this is old but I was just having the same issue and removing the collectionFS package solved my problem immediately...in case that helps anyone.