radoslavgatev/ghost-azure

Production ready Ghost for Azure :ghost:

ghost-azure's Issues

Error when upgrading from 1.x to 2x

Hi, when I hit the 'sync' button in Azure, the upgrade process kicks off, but then fails after a few minutes. I am getting the following error(s):

Error: SQLITE_ERROR: table posts has no column named comment_id
Command 'starter.cmd deploy.cmd' was aborted due to no output nor CPU activity for 60 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd deploy.cmd
One or more errors occurred.
Command 'starter.cmd deploy.cmd' was aborted due to no output nor CPU activity for 60 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd deploy.cmd

Cannot create application insight

If I create application insight, the service goes down.

Important Security Update 4.16.0

Hi Radoslav,

Can you please update the repo with the latest changes, it seems like there is a major security update here: https://github.com/TryGhost/Ghost

Thank you so much ❤️😊

Deploy through "Portal" link also failed with a "Resource Deployment Failure"

Tried using the "Deploy via Portal" link, which resulted in failure, detail below:

{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "Conflict",
      "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\"\r\n  }\r\n}"
    }
  ]
}

*Note, this was in a brand new Azure setup with no pre-existing resources defined

Deployment Center Sync Failing

Site has been running great for about a year - this is just my second time syncing and this time it failed. Log attached, not sure where to start troubleshooting. There's an error for migratorconfig.js missing but I've verified from console that the file exists and has content.

Any Suggestions?

deploymenterror.txt

I updated Applications Insights - no response anymore

I updated Applications Insights. Now I can't get no response at all.
If I go to my url, nothing happens. There is no source file to read. Nothing.
I can't see any error message in the server end.

Any ideas?

Value for RepoURL

Might be a dumb question, but what value do we need for Repo Url? Would it be this repo pointing to azure branch (or our fork?)

I'm getting the following error for Microsoft.Web/sites/sourcecontrols when provisioning

{
    "status": "Failed",
    "error": {
        "code": "BadRequest",
        "message": "There was a conflict. Conflict with existing ScmType: ExternalGit",
        "details": [
            {
                "message": "There was a conflict. Conflict with existing ScmType: ExternalGit"
            },
            {
                "code": "BadRequest"
            },
            {}
        ]
    }
}

Is there a way to use ghost CLI to run locally for debugging/customization?

I'd like to be able to make changes directly in my branch that I use to deploy to Azure. But ghost start at the command line in the root folder doesn't work. So for now I have a separate instance of ghost in a separate repo and have to move the changes between the two branches manually (using my diff tool).

trying to install the 1.19 version fails in Azure

Deploying the develop branch (2) works fine.
When trying to deploy the version 1.19 gives me an error:

first run>>

Submitting Deployment
Deployment Started
Creating Web Hosting Plan
Creating Website
Setting up Source Control
Deployment Failed (View Error) >> The resource operation completed with terminal provisioning state 'Failed'.

second run (after retry):

Submitting Deployment
Deployment Started
Creating Web Hosting Plan
Creating Website
Setting up Source Control
Deployment Failed (View Error) >> Could not find any source control deployments

Any idea why this happens?

deploy.azure.com is not responding. ERROR: DNS_PROBE_FINISHED_NXDOMAIN

Well
I know this issue is with Azure itself but is there any other way of direct deployment?

Obvious answer is via portal BUT while deploying through Azure portal, this repo and major branch (azure) is giving errors.

Upgrade from 17.2 to 18.0 failed.

Hi there,

Thanks for your effort and support to Azure platform.
My issue is related to upgrading (17.2 to 18.0).

I have a Ghost 17.2 on the Azure Web App and working well.
But, I initiating staging deployment slot with your repository will fail.

How can I do for my web app upgrade from your repository?

Unable to deploy - issue with getsiteSourceContol

Just a small snippet of the issue

Add error as a zip file

ghostFullError.zip

Demo Website (https://ghost-azure-demo.azurewebsites.net/) not accessible

Exactly as it says in the title

AzureDeploy not working

Tried clicking on the Azure Deploy option and it simply reports a 404 error

from scratch deployment error

Keep getting hung up on the following error. Thoughts?

Deployment template validation failed: 'The template resource 'Microsoft.Web/sites/NoMiddleGround/config/appsettings' reference to 'Microsoft.Insights/components/NoMiddleGround-insights' requires an API version. Please see https://aka.ms/arm-template for usage details.'. (Code: InvalidTemplate)

(Question) How to update deployed site/blog

I've been playing with ghost and found this repo awesome for getting ghost running on my azure.

I have now tweaked some of my css and want to upload these amendments to azure. However the deploy button tries to create a new site, if I specify my current site it errors that the site already exists.

Thanks Ash.

Question: How to change default url?

I installed my site on Azure as per this project. The installation has worked well, but picked up the azure url ghost-azure5ed4.azurewebsites.net1. I have added a custom url to the project, whihc is working, but the meta data e.g. canonical links and home buttons still route to the azure url.

Is there any way I can change this properly?

Deploy without creating App Service Plan

First, thanks so much for making this!

I'm a little overwhelmed by the deploymentTemplate JSON. Is there an easy way to either:

• Edit the deployment JSON to add to an existing App Service Plan, instead of creating a new one, or,
• Deploy it myself by adding the repo as a "Deployment option"? And if so, are there any settings (siteName, email settings) that I need to add manually?

Thanks!

One Click deploy fails with "invalid repository url"

... looking to set up a one click installation for a privacy protected blogging site and discovered that the following error appears when I deploy

"One Click deploy fails with "invalid repository url""

Any assistance would be helpful.

Getting an HTTP ERROR 500

Hi, as the title said, I'm getting an HTTP ERROR 505 for a brand new deployment after one click deployment to Azure.

Rewrite rule causing too many redirects

I've deployed recently to Azure and I was getting the error "Too many redirects" and accessed via HTTPS configured outside Azure (through CloudFlare).

Removing the lines below from the web.config solved the issue

<rule name="HTTP to HTTPS redirect" stopProcessing="true">
	<match url="(.*)" />
	<conditions>
		<add input="{HTTPS}" pattern="off" ignoreCase="true" />
	</conditions>
	<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
</rule>

URL miss match with Ghost site when using a custom domain

Putting this here for reference as it took me a while to track down.

If you add a custom domain to your Ghost Azure deployment and switch over to the new URL, the site will still hold the original AzureWebsites URL by default, which affects base links and referrals.

To fix this, you need to change the Azure configuration property "URL" in the App Service configuration.

Build and deployment fails while deploying via Continuous deployment to Azure App Service

While deploying this Ghost Blog app via Continuous deployment to Azure App Service am getting error.

Link to the yml file being used, for deployment.

Any help is much appreciated. Thank you.

---

Log extract from Pipeline is below:

Run npm install
npm install
npm run build --if-present
shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated [email protected]: [email protected] drops support for the browser, Node <12.11.0, and removes bthreads entirely. Either upgrade to v7.0.0 or lock your bree version to v6.5.0.
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: request-promise has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated [email protected]: We've written a new parser that's 6x faster and is backwards compatible. Please use @formatjs/icu-messageformat-parser
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated

[email protected] install D:\a\Ghost-Azure\Ghost-Azure\node_modules\dtrace-provider
node-gyp rebuild || node suppress-error.js

D:\a\Ghost-Azure\Ghost-Azure\node_modules\dtrace-provider>if not defined npm_config_node_gyp (node "C:\hostedtoolcache\windows\node\12.13.0\x64\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\hostedtoolcache\windows\node\12.13.0\x64\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.

[email protected] install D:\a\Ghost-Azure\Ghost-Azure\node_modules\re2
install-from-cache --artifact build/Release/re2.node --host-var RE2_DOWNLOAD_MIRROR || npm run rebuild

Trying https://github.com/uhop/node-re2/releases/download/1.16.0/win32-x64-72.br ...
Writing to build/Release/re2.node ...
Done.

[email protected] install D:\a\Ghost-Azure\Ghost-Azure\node_modules\sharp
(node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.11.3/libvips-8.11.3-win32-x64.tar.br
sharp: Creating D:\a\Ghost-Azure\Ghost-Azure\node_modules\sharp\build\Release
sharp: Copying DLLs from D:\a\Ghost-Azure\Ghost-Azure\node_modules\sharp\vendor\8.11.3\win32-x64\lib to D:\a\Ghost-Azure\Ghost-Azure\node_modules\sharp\build\Release

[email protected] install D:\a\Ghost-Azure\Ghost-Azure\node_modules\sqlite3
node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
[sqlite3] Success: "D:\a\Ghost-Azure\Ghost-Azure\node_modules\sqlite3\lib\binding\napi-v3-win32-x64\node_sqlite3.node" is installed via remote
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for @tryghost/[email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: @tryghost/[email protected]
npm WARN notsup Unsupported engine for @tryghost/[email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: @tryghost/[email protected]
npm WARN notsup Unsupported engine for @tryghost/[email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: @tryghost/[email protected]
npm WARN notsup Unsupported engine for @tryghost/[email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: @tryghost/[email protected]
npm WARN notsup Unsupported engine for @tryghost/[email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: @tryghost/[email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^12.22.1 || ^14.17.0 || ^16.13.0"} (current: {"node":"12.13.0","npm":"6.12.0"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN [email protected] requires a peer of mssql@^6.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of mysql2@^2.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of pg@^7.18.2 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of sqlite3@^4.1.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of mssql@^6.2.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of mysql2@^2.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of pg@^8.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of mssql@^6.2.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of mysql2@^2.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of pg@^8.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of canvas@^2.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of canvas@^2.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.

added 1936 packages from 1475 contributors and audited 1976 packages in 149.37s
found 35 vulnerabilities (16 moderate, 17 high, 2 critical)
run npm audit fix to fix them, or npm audit for details

[email protected] build D:\a\Ghost-Azure\Ghost-Azure
grunt build

Running "subgrunt:init" (subgrunt) task
Warning: The "core/client" directory is not valid, or does not contain a Gruntfile.� Use --force to continue.

Aborted due to warnings.
npm ERR! code ELIFECYCLE
npm ERR! errno 6
npm ERR! [email protected] build: grunt build
npm ERR! Exit status 6
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\npm\cache_logs\2021-11-17T18_41_45_295Z-debug.log
Error: Process completed with exit code 1.

Deploy to Azure button creating new App Service Plans

Hello,

Is it possible to configure the deploy to Azure button to not create a new App Service Plan? I would want to deploy to existing App service plans.

Thanks for your work.

Demo Ghost link not working

When I deployed my ghost on Azure. Getting HTTP 5XX response same as getting in demo.

Also while deploying I got some azure http 403 errors. Which is completely strange.

Please 🥺🙏 fix them.

Question (not a issue)

We have a static website and blog site. We want to combine them. How to combine this repo(ghost-azure) with website repo we maintain.
Both our sites are hosted on azure. Please advise (steps).

Thanks to the team who created this repo. We tried setting up ghost manually on azure portal and spent hours without success. This was one click.

Sync in Azure deployment center completely broke site

I'm trying to troubleshoot why my first sync after my initial deploy last October has taken the site down completely. The deployment center log does not help. Node version changes do not help. I wonder if it's because I added a custom them when I set it up in October.
Any hints on troubleshooting further? I have looked at the downloaded SQLite database.
I'll only be losing a few articles I posted if I start over...

How to build?

Hey there, I have a question about building the ghost blog itself. I did some minor adjustments to my branch and probably need to update the assets so they are actually getting effective on my web app.

I found this guide: https://docs.ghost.org/docs/working-with-ghost

Do I need to setup more, or is this all to build the assets? I have to admit, I don't have much experience when it comes to building node apps ;-)

Azure Deploy Not working for me.

Getting this error when it tries to deploy:
`Command: deploy.cmd
Handling node.js deployment.
Creating app_offline.htm
KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
Copying file: 'iisnode.yml'
Deleting app_offline.htm
Using start-up script index.js from package.json.
Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 4.5.0, 4.6.0, 4.6.1, 4.8.4, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0, 6.5.0, 6.6.0, 6.7.0, 6.9.0, 6.9.1, 6.9.2, 6.9.4, 6.9.5, 6.10.0, 6.10.3, 6.11.1, 6.11.2, 6.11.5, 6.12.2, 6.12.3, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.4, 7.10.0, 7.10.1, 8.0.0, 8.1.4, 8.4.0, 8.5.0, 8.7.0, 8.8.0, 8.8.1, 8.9.0, 8.9.3, 8.9.4, 8.10.0, 8.11.1, 10.0.0, 10.6.0, 10.14.1, 10.15.2.
Selected node.js version 10.15.2. Use package.json file to choose a different version.
Selected npm version 6.4.1
Updating iisnode.yml at D:\home\site\wwwroot\iisnode.yml
npm WARN deprecated [email protected]: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once it is released.
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN [email protected] requires a peer of knex@>=0.6.10 <0.15.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.5.4 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^15.5.4 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm ERR! path D:\home\site\wwwroot\core\shared\nql-map-key-values
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall symlink
npm ERR! Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values'
npm ERR! { [Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values']
npm ERR! cause:
npm ERR! { Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values'
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'symlink',
npm ERR! path: 'D:\home\site\wwwroot\core\shared\nql-map-key-values',
npm ERR! dest: 'D:\home\site\wwwroot\node_modules\nql-map-key-values' },
npm ERR! stack:
npm ERR! 'Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values'',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'symlink',
npm ERR! path: 'D:\home\site\wwwroot\core\shared\nql-map-key-values',
npm ERR! dest: 'D:\home\site\wwwroot\node_modules\nql-map-key-values',
npm ERR! parent: 'ghost' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
Failed exitCode=-4048, command="D:\Program Files (x86)\nodejs\10.15.2\node.exe" "D:\Program Files (x86)\npm\6.4.1\node_modules\npm\bin\npm-cli.js" install --production
npm ERR! the command again as root/Administrator (though this is not recommended).
An error has occurred during web site deployment.

npm ERR! A complete log of this run can be found in:
npm ERR! D:\local\AppData\npm-cache_logs\2019-08-14T16_46_21_838Z-debug.log
npm WARN deprecated [email protected]: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once it is released.\r\nnpm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.\r\nnpm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.\r\nnpm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.\r\nnpm WARN [email protected] requires a peer of knex@>=0.6.10 <0.15.0 but none is installed. You must install peer dependencies yourself.\r\nnpm WARN [email protected] requires a peer of react@^15.5.4 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.\r\nnpm WARN [email protected] requires a peer of react-dom@^15.5.4 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.\r\nnpm WARN [email protected] requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.\r\n\r\nnpm ERR! path D:\home\site\wwwroot\core\shared\nql-map-key-values\r\nnpm ERR! code EPERM\r\nnpm ERR! errno -4048\r\nnpm ERR! syscall symlink\r\nnpm ERR! Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values'\r\nnpm ERR! { [Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values']\r\nnpm ERR! cause:\r\nnpm ERR! { Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values'\r\nnpm ERR! errno: -4048,\r\nnpm ERR! code: 'EPERM',\r\nnpm ERR! syscall: 'symlink',\r\nnpm ERR! path: 'D:\home\site\wwwroot\core\shared\nql-map-key-values',\r\nnpm ERR! dest: 'D:\home\site\wwwroot\node_modules\nql-map-key-values' },\r\nnpm ERR! stack:\r\nnpm ERR! 'Error: EPERM: operation not permitted, symlink 'D:\home\site\wwwroot\core\shared\nql-map-key-values' -> 'D:\home\site\wwwroot\node_modules\nql-map-key-values'',\r\nnpm ERR! errno: -4048,\r\nnpm ERR! code: 'EPERM',\r\nnpm ERR! syscall: 'symlink',\r\nnpm ERR! path: 'D:\home\site\wwwroot\core\shared\nql-map-key-values',\r\nnpm ERR! dest: 'D:\home\site\wwwroot\node_modules\nql-map-key-values',\r\nnpm ERR! parent: 'ghost' }\r\nnpm ERR! \r\nnpm ERR! The operation was rejected by your operating system.\r\nnpm ERR! It's possible that the file was already in use (by a text editor or antivirus),\r\nnpm ERR! or that you lack permissions to access it.\r\nnpm ERR! \r\nnpm ERR! If you believe this might be a permissions issue, please double-check the\r\nnpm ERR! permissions of the file and its containing directories, or try running\r\nnpm ERR! the command again as root/Administrator (though this is not recommended).\r\n\r\nnpm ERR! A complete log of this run can be found in:\r\nnpm ERR! D:\local\AppData\npm-cache_logs\2019-08-14T16_46_21_838Z-debug.log\r\nD:\Program Files (x86)\SiteExtensions\Kudu\82.10503.3890\bin\Scripts\starter.cmd deploy.cmd`

Deploy to Azure

Hello, could you check if the deployment to Azure still works for you? It doesn't for me. I first contacted Microsoft, but they tell me to post an issue in this repo. They also point me to the Ghost product in the Azure marketplace, but that isn't the up-to-date version.

The license file is not a license file.

I might be missing something, but the license file is a bunch of information that has nothing to do with licensing.

Switch from npm to Yarn