arunoda
commented
9 years ago First of all,
mup can't be use with Windows at the moment. Sorry for that issue.
On Thu Jan 08 2015 at 4:11:12 AM politicratic notifications@github.com wrote:
New to Linux. New to Meteor. So far, not too painful, but meteor deployment has been a major sticking point. This is the content of my
mup.json (a few things changed for security/obfuscation):
{ // Server authentication info "servers": [ { "host": "xxxxxxxxxx.com", "username": "root", //"password": "XXXXXXXXXXXXXXX" // or pem file (ssh based authentication) "pem": "XXXXXXXXXXXX" } ],
// Install MongoDB in the server, does not destroy local MongoDB on future setup "setupMongo": false,
// WARNING: Node.js is required! Only skip if you already have Node.js installed on server. "setupNode": false,
// WARNING: If nodeVersion omitted will setup 0.10.33 by default. Do not use v, only version number. "nodeVersion": "0.10.33",
// Install PhantomJS in the server "setupPhantom": false,
// Application name (No spaces) "appName": "xxxxxxxapp",
// Location of app (local directory) "app": "C:/Users/XXXXX/xxxxxxWeb",
// Configure environment "env": { "ROOT_URL": "http://xxxxxxx.com", "MONGO_URL": "mongodb://XXXXX", "MONGO_OPLOG_URL": "mongodb://XXXXX", "PORT": 8080, "MAILGUN_API_KEY": "XXXXXX", "MAILGUN_DOMAIN": "XXXXX", "MAILGUN_API_URL": "XXXXXXX" },
// Meteor Up checks if the app comes online just after the deployment // before mup checks that, it will wait for no. of seconds configured below "deployCheckWaitTime": 15
}
The result is (running command prompt as Administrator): Meteor Up: Production Quality Meteor Deployments
Started TaskList: Updating configurations (linux) [xxxxxxx.com] - Setting up Environment Variables [xxxxxxx.com] Setting up Environment Variables: FAILED spawn ENOENT Completed TaskList: Updating configurations (linux)
I've run mup logs -n 400 and get: Meteor Up: Production Quality Meteor Deployments
In the command window. Should I be seeing more? I couldn't find any log files.
Given I'm not even attempting to deploy, and I was running previously into issues accessing C:\tmp\xXxXxXXxXxXXXXXXxxxXX style folders, I set Node/Phantom to false for setup.
I've run through the half dozen tutorials I can find and all of them seem to assume development on a Linux box or at worst Mac. Really would rather not have to work out byzantine methods of transferring work to and from Photoshop when it's time to go live if I can avoid it, and the "joy" of running Linux in a VM box with attempts to share files/folders has burnt me out completely.
Hoping someone can point to something obvious I'm doing wrong.
— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/216.
benjick
jazoom
dotnetwise
New to Linux. New to Meteor. So far, not too painful, but meteor deployment has been a major sticking point. This is the content of my mup.json (a few things changed for security/obfuscation):
{ // Server authentication info "servers": [ { "host": "xxxxxxxxxx.com", "username": "root", //"password": "XXXXXXXXXXXXXXX" // or pem file (ssh based authentication) "pem": "XXXXXXXXXXXX" } ],
// Install MongoDB in the server, does not destroy local MongoDB on future setup "setupMongo": false,
// WARNING: Node.js is required! Only skip if you already have Node.js installed on server. "setupNode": false,
// WARNING: If nodeVersion omitted will setup 0.10.33 by default. Do not use v, only version number. "nodeVersion": "0.10.33",
// Install PhantomJS in the server "setupPhantom": false,
// Application name (No spaces) "appName": "xxxxxxxapp",
// Location of app (local directory) "app": "C:/Users/XXXXX/xxxxxxWeb",
// Configure environment "env": { "ROOT_URL": "http://xxxxxxx.com", "MONGO_URL": "mongodb://XXXXX", "MONGO_OPLOG_URL": "mongodb://XXXXX", "PORT": 8080, "MAILGUN_API_KEY": "XXXXXX", "MAILGUN_DOMAIN": "XXXXX", "MAILGUN_API_URL": "XXXXXXX" },
// Meteor Up checks if the app comes online just after the deployment // before mup checks that, it will wait for no. of seconds configured below "deployCheckWaitTime": 15 }
The result is (running command prompt as Administrator):
Meteor Up: Production Quality Meteor Deployments
Started TaskList: Updating configurations (linux) [xxxxxxx.com] - Setting up Environment Variables [xxxxxxx.com] Setting up Environment Variables: FAILED spawn ENOENT Completed TaskList: Updating configurations (linux)
I've run mup logs -n 400 and get:
Meteor Up: Production Quality Meteor Deployments
In the command window. Should I be seeing more? I couldn't find any log files.
Given I'm not even attempting to deploy, and I was running previously into issues accessing C:\tmp\xXxXxXXxXxXXXXXXxxxXX style folders, I set Node/Phantom to false for setup.
I've run through the half dozen tutorials I can find and all of them seem to assume development on a Linux box or at worst Mac. Really would rather not have to work out byzantine methods of transferring work to and from Photoshop when it's time to go live if I can avoid it, and the "joy" of running Linux in a VM box with attempts to share files/folders has burnt me out completely.
Hoping someone can point to something obvious I'm doing wrong.