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.
Related
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.
This is my first post here and I have to say, Stack Overflow is such an amazing community for devs. I have visited many times over the years and would like to say a big thank you to everyone for joining together and sharing your knowledge!
So... I love web development and am experimenting with Polymer.
I use the Poylmer CLI and have developed a basic boilerplate for polymer which works perfectly when I run locally on the polyserve / polymer cli.
When I deploy to firebase or open with a native browser (rather than launching polyserve or polymer serve) the app shows as blank. I can't see any console errors either?
Could someone please explain why my web app is not working?
Here is the link to the firebase deployment: https://vapoursnake-91c13.firebaseapp.com/
It turns out that using the cli to run
Polymer Build
did not include the directories for /src and /bower_components
I simply copied them from the root folder.
I would like to make changes for my meteor site, but my local copy of the meteor site folder has been deleted, Is there any way to get back the copy?
It would be great help if anyone could suggest a solution.
Here is my meteor site, http://techtrends.meteor.com
Is there any way to get back the copy? YES
How?
Contacting the Meteor Team
I think you can get the client code inspecting the console (hard work) running the --debug option (im not sure never do that) but also you wont get the server code since that isn't published to the client.
So Contacting the Meteor Team would be the best option here
I learned the hard way that plugins can and will disappear if I add them via the UI. According to the help: "Bluemix, like other cloud platforms, has an ephemeral filesystem. Every time you push or restart your app, the container that stores the files for your app is destroyed and recreated. If you update the WordPress Core from the UI, then the update is rolled back when your app is restarted."
So I'm now trying to add them via the Cloud Foundry command line interface as suggested in the help docs.
I downloaded the application starter code, extracted it to a New_folder, downloaded the plugin I wanted, extracted that to the New_folder/wp-content/plugins/ and then tried to do a cf push. I got no errors but the plugin is not showing up in the wp-admin page.
Total Wordpress newbie here... Can anyone provide me any clues on what I'm doing wrong or steps I'm missing? Has anyone else tried this?
Ok got it working. I figured it out with help from the Bluemix dev team, here is what they said:
We are still waiting for our updated documentation to land. We should have synchronized the updated deployment with the corresponding documentation updates, sorry for the trouble.
Until the docs at https://www.ng.bluemix.net/docs/#starters/wordpress/index.html#wordpress are updated, please follow the steps posted at https://developer.ibm.com/answers/questions/181148/wordpress-changed-wordpress-file-not-uploaded/#answer-181784 and report back if you have any trouble.
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.