Reputation: 1875
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.
Upvotes: 0
Views: 1525
Reputation: 57
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.
Upvotes: 0
Reputation: 4744
I had the same error. But the following solution works deploying the app successfully.
meteor login
meteor deploy < available meteor sub domain name >
Upvotes: 1
Reputation: 36900
There are several reasons why your site may not load when being deployed.
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
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
.
Upvotes: 2