-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verifying deployment always failing with mupx with meteor 1.3 & DigitalOcean #905
Comments
I think for Meteor 1.3 the only best way forward will be with the new port of the dev branch mupx over at kadirahq. My guess is it won't be properly supported until the official release. |
@MasterJames thank you for the quick reply, so do I have to stick with Meteor 1.2 if I want to deploy with mup/mupx ? |
I'm not 100% on that. I think so., but try that newer version at kadirahq and ask there about it? |
Hi there, it would be great if mupx could handle deploying 1.3 beta xx until the new version is ready for me it started breaking @ beta 12 any chance we can get help from kadira here ? p.s. I could not get the 'being refactored' version to work thanks ! |
update: I could actually deploy with beta 16 and current version of mupx extended have to admit I don't know if I had to take other steps since I kind of lost track of everything I tried hope this helps |
@thomasmery i can verify updating to -16 fixed the issue. |
Verification still does not work for me, even on meteor 1.3 release. Also, are you guys having issue with 1.3 redeployment? My meteor app fails to run on redeployment. Are these similar issue? #929 |
@walleXD have your tried @thomasmery solution? worked well for me |
I have constantly an error when trying to deploy an app with meteor 1.3-beta.12 on a Digital Ocean Ubuntu 14.04.4 x64 droplet.
here is the log:
`[server-ip] - Initializing start script: SUCCESS
[server-ip] - Invoking deployment process
[server-ip] - Invoking deployment process: SUCCESS
[server-ip] - Verifying deployment
[server-ip] x Verifying deployment: FAILED
The text was updated successfully, but these errors were encountered: