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
Related
Is there a way to access the Meteor server logs on a production server? All I needs is something that records what I'd see as the server console output on my dev machine, in a log file on the server. I would have expected Meteor to log them somewhere by default but I can't find anything.
I'm running Meteor 1.6 on a Digital Ocean droplet, Ubuntu 16.04.3. Deployed with Phusion Passenger.
I've hunted around and there are a bunch of logging packages for Meteor but I can't figure how to use any of them; there don't seem to be any basic examples or instructions.
This must be a really common requirement - anybody know how to do this? Thanks!
Remember that Meteor runs on Node.js. Therefore, many things valid for Node.js is also valid for Meteor like location of the default root folder of the built-in web server. You should check the path "/var/www/html", first for the server logs.
I created a new app repository in Github, built on the Meteor platform. I am having significant difficulty deploying the app to my DigitalOcean droplet, however. I am trying to connect my Github repository to the droplet and to deploy that to my domain. I am trying to do this in SSH using puTTy; however, after setting up a root account and password, I am unable to log in through SSH. I receive the following error: disconnected: no supported authentication methods available (server sent:publickey)
Does anyone know why this error is coming up? I have looked through more tutorials for deploying a meteor app on digitalocean than I care to admit, but they all seem to take different approaches and many are outdated. Any advice would be greatly appreciated!
Thank you
I reckon the easiest way is to use meteor up. It's a very simple process, and you don't need to be continually sshing into your target server, with all the hassles involving ssh keys.
In my experience, once you have it set up, it's a very painless process, and you can deploy with a simple command each time.
http://meteor-up.com/
It looks after the following:
Setting up your server with docker instances
Creating SSL certs using Let's encrypt
Building your app, bundling it, transferring it
Starting the app
Rolling back if it doesn't work
There is some trust involved, but it's worth it for a seamless deployment scenario
It appears mup setup can't run without a mup.json file. But, it appears the mup.json file is primarily used for mup deploy. Reason I ask is I'm trying to execute mup setup on the host server and it fails without the server credentials but considering that I'm already logged onto the server executing the setup I don't understand why the mup.json is being required in the first place? I'm not deploying an application so none of the application-specific settings would apply, right? If I don't have a mup.json on the server then mup setup throws an error that the mup.json file does not exist. It didn't seem really clear on the meteor up web site. Thanks!
You should run Meteor Up from your local machine as that's what it's designed for. I wrote about how to deploy with meteor up a while back and that should help you.
In a nutshell I believe you're thinking about this the wrong way. With mup, meteor deploy and soon galaxy deploy, you no longer need to "upload" your files and then go and manage them from the server. Instead your files stay local, you deploy (which will upload them) and deployment sets up your server and file structure.
Misunderstanding on my part. mup setup is something you run on your remote machine, not the host machine.
Running into a strange 'error' to do with routing when deploying a Meteor app, both on meteor.com and on heroku. When the application is running locally, everything works fine. However, when the app is deployed - and I've tried this both on meteor.com's simple hosting and on Heroku - I get the default Iron Router setup page with instructions on how to set up my first route, even though the routes are defined correctly and work locally (screenshot below). This happens on all pages in the app.
Here's a screenshot of the page: http://i.stack.imgur.com/GlNd9.png
I ran into this recently may be able to shed some light on the issue.
If you are working fine in development but not in production then the first thing to do is run your development/local version like so:
meteor --production
This runs the local development version in production mode, as it does when deployed to Modulus, Heroku etc.
If you now get the iron router splash page locally you can be sure the issue is due to running in production mode.
Open up your site in Chrome (or your favourite browser) and look in the browser javascript console for errors... I had one in my client events javascript which I had recently changed.
If you have an error fix it then see whether your Meteor app now runs with the --production flag without showing the Iron Router page.
The splash page in my case was a red herring, masking the real error under the hood.
I haven't looked in depth into the difference between the development and production modes but it obviously handles errors differently so you get different behavior in the two modes.
I've got a small WCF service I've created.
I can edit it and get it working great on the localhost, but my PC is not where this application is going to be run from. It is going to run on our Server.
However, every time I try making any kind of change to the project that points it to our server, the entire project goes to crap: I can no longer view the project in a browser and my test console application can not connect to it. I try changing it back to using the local IIS web server, but then the local machine does not start up IIS whenever the project is started so it doesn't work either.
I can debug and troubleshoot for a day or so to get it working again on the local machine, but then I'm back to Square 1 where I need to deploy my application onto our Server.
This is freakin' maddening!
My project works, but I can't seem to get it from Localhost to a real Server.
All the examples I find online show how to do this using Localhost. Does no one ever deploy their projects?
Where is the Guide for getting me from Development stage to Deploy?
Some nice tutorials here
http://www.dotnetspider.com/forum/193466-Deploy-Wcf-service-IIS.aspx
http://wcftutorial.net/WCF-IIS-Hosting.aspx
also on SO Deploy WCF Service to IIS when it only has an App.config
Also a video on youtube http://www.youtube.com/watch?v=mX8quq7MoeI