search

fractal-code / meteor-azure

Automate Meteor deployments on Azure App Service
MIT License
68 stars 20 forks source link

availability question: old version with config files (instead of command line)? #41

Closed arshbucks closed 7 years ago

arshbucks commented 7 years ago

Was wondering if you still happen to have the old version (with the bash deployment script + config file).

I like the ability to automatically deploy from source control directly, vs manually from command line.

If the command line is the only version available, we should delete the config file + deployment folder right?

Thank you!

ramijarrar commented 7 years ago

We no longer support 1.x, but you can download/view any version from the release history (though we do not recommend this).

If you want to hook up v2 deployments with source control, just configure an external CI tool (e.g CircleCI which is free) to run the command for you.

arshbucks commented 7 years ago

Gotcha, thanks. Trying to use the cmd line version, but getting the error below. Am I doing it wrong?

meteor-azure --settings ../privateDeploymentFiles/settingsDev.json --web-config ../privateDeploymentFiles/httpsMulticoreWeb.config --debug

I have tried wrapping the paths in " ", and the settings file hasthe exact same structure as your example (except there is an extra "MAIL_URL" in the envVariables.)

ramijarrar commented 7 years ago

What is the error?

arshbucks commented 7 years ago

Whoops - forgot to paste that in: error: Could not read settings file at '../privateDeploymentFiles/settingsDev.json'

ramijarrar commented 7 years ago

The path is based on the directory the command runs in, can you double-check it's pointing to the right file? (try running cat "../privateDeploymentFiles/settingsDev.json" to confirm)

arshbucks commented 7 years ago

On windows I did: type "..\privateDeploymentFiles\settingsDev.json" and it will output the file content to the console.

However, I also tried running meteor-azure with the path containing: backslashes, backslashes+quotations, and Fully-Qualified paths (with forward/back slashes and/or quotations) - same error for all.

Could you confirm this error only shows up when it cannot find the file, and not when it has trouble reading the file content?

ramijarrar commented 7 years ago

Can you try running meteor with the same settings file (that will confirm the file content is valid)?

arshbucks commented 7 years ago

good call - found an extra comma.

(copied the example settings here http://meteor-azure.readthedocs.io/en/latest/getting-started.html - there's a trailing comma after envVariables. Sometimes that doesn't present a problem..maybe it does in the settings JSON. My fault though for not thinking of that first).

ramijarrar commented 7 years ago

Good catch, I'll fix this in the documentation.

Let me know if you have any further issues.

arshbucks commented 7 years ago

Thanks - appreciate the hard work & prompt responses!

arshbucks commented 7 years ago

My deployment did finish properly according to the CLI - but I only see "The page cannot be displayed because an internal server error has occurred." on the site.

I tried accessing kudu logs via curl -u {username} https://{sitename}.scm.azurewebsites.net/api/logstream (and using the same FTP credentials used to deploy), but get exactly nothing after connecting...

Any ideas? (Lmk if you prefer to move to a separate issue...)

ramijarrar commented 7 years ago

Can you try refreshing after a few minutes? Still the same result?

arshbucks commented 7 years ago

Yup - same result. The logstream sent "No new traces" each of the past 5 minutes

ramijarrar commented 7 years ago

Can you open your site in the Azure portal and in "Diagnostics Logs" make sure "Application Logging (Filesystem)" is set to "On" and "Level" is set to "Information".

Once you've done that, restart the App and open the debug console (https://{your-site-name}.scm.azurewebsites.net/DebugConsole) then navigate to "LogFiles" > "Application" and check the contents of the latest *-stdout-*.txt

arshbucks commented 7 years ago

the LogFiles/application folder seems to be empty -- Don't see a -stdout-.txt.

And looking at Web Server logs, all the GET requests seem to show 200 status.

Quick check: In application settings - it says METEOR_AZURE_NODE_VERSION set to "v4.8.4". That ok? should there be a "v"?

ramijarrar commented 7 years ago

Yeah that's fine, Node/NPM format versions differently. Is "Application Logging (Filesystem)" enabled on the Azure portal?

arshbucks commented 7 years ago

Yeah, I set it to Information & restarted the app. Let me try it again - seems like it might have gotten re set to "error" somehow in the interim - just looked at it again

arshbucks commented 7 years ago

Nope - still nothing. No stdout file...

ramijarrar commented 7 years ago

Closing as per external discussion,

(For reference: issue was caused by a misconfigured web config)