I'm basically from react background where i have deployed my react app's on EC2 just by building with (npm run build) the project and using packages like Pm2 and serve.
Now when i tired to do the same thing with NextJs App it is not happening. So my question is it mandatory to use Nginix for NextJs App's while deploying them on ec2?
I'm new to Meteor and made a very simple meteor-based ios app for personal use and interest, which read data from MongoDB provided by Meteor. I have a quick question and I just want to make sure that I am not spending time on meaningless work.
What I have done is "meteor run ios-device", and it works pretty well that under the same network (wifi) the app on ios could read data from the localhost:3000 on laptop (Mac). Also, I have learned that it is easy to deploy a meteor app on my own server, just run "meteor build /path/to/buildFile --architecture..." and move the bundle to the server to set up; however, then I got confused about this: after the app is deployed to a server, is it possible that the app on ios also able to access to that server?
In short words, app ios works fine with localhost, so is there a way to make it works fine with web hosting so that the app does not need to connect to the same network as the host?
Note that I didn't purchase Apple developer account that could release app to AppStore, so I can only use "real machine debugging". Will this disallow me to make app on ios access the data from my own server?
Thanks for any advance!
Update:
I have successfully deployed my project on my own OpenShift server so that I could access it within any networks in browsers. So my point is how do I build an ios app for this project so that I can also access it in iPhone within any network. I have tired run "meteor run ios-device --mobile-server=[my own openshift server]:8000", and when I build the app for deploying I ran this "meteor build ~/some/path --server=[my own openshift server]:8000". This seems does not works. Still waiting for advance!
You are describing one of the main use case of Meteor.
Refer to:
Meteor Guide > Mobile > Configuring your server
Meteor Guide > Mobile > Building for production
To summarize:
When building your Meteor project, if you have ios and/or android platform(s), Meteor will require you to specify the --server option with the URL of the server where your Meteor server bundle will be deployed.
That way, your app will know where to connect to.
Note that you may not need to go through Apple App Store, as long as you do not need to distribute your app. You can simply use the Xcode project (generated by meteor build) to install your app directly on your iPhone.
I'm installing my SSL certificate and need to run mupx setup and mupx deploy to get it to work.
However, doing this and then deploying my app will wipe my MongoDB on my production server and users lose all of their accounts. It would be a nightmare.
I simply run mupx deploy after making fixed to my Meteor app to update my app. However, when installing my SSL certificate (according to the Mup documentation) I have to run mupx setup to get it to work.
Is there a way I can do this without wiping my user database on my deployment server?
I have production app running on Digital Ocean. I need to revise the code. It easy with meteor.com hosting:
meteor deploy xxx
How do I update production app with self hosting like Digital Ocean?
Thank You
You should re-deploy with mupx to update your app on prod.
I used Meteor Up (MUP) to deploy my meteor app to a Digital Ocean droplet. I had some problems with deploying it the first time but I solved all of them and I got it working. I then made some updates to my app but when I deployed it again the page says "This webpage is not available". I have tried re-deploying the app on new droplets with different IP addresses but the same happens. I have run mup setup on each new droplet. It always says success for the setup and for the deployment but nothing shows up.
Can anybody tell me what I have done wrong?
It's likely there is some kind of error with your app, probably not related to deployment if it the issue occurs in the way your describe it.
You'll have to check your app's server side logs for a bit more info:
mup logs -f