Permalink
Browse files

Merge branch 'dev' of https://github.com/SharePoint/sp-dev-gdpr-activ…

…ity-hub into dev
  • Loading branch information...
PaoloPia committed Jan 19, 2018
2 parents 0a82891 + 27d778c commit 1eb89c8b9cc50f91ff27e3b0415e33d0220519d5
Showing with 2 additions and 3 deletions.
  1. +2 −3 Documentation/Setup-Guide-Office-365-CDN.md
@@ -65,9 +65,10 @@ In the following Figure you can see the _write-manifest.json_ file in the UI of
* Save the _write-manifest.json_ file and go back to the PowerShell console, which should still be located under the solution's folder
* From within the console, execute the following commands:
* From within the console, execute the following commands in order to install the dependencies and generating the bundle:
```PowerShell
npm install
gulp bundle --ship
gulp package-solution --ship
```
@@ -87,7 +88,6 @@ Now, you can execute the following PowerShell command:
-ConfigureCDN `
-CDNSiteName "CDN" `
-CDNLibraryName "CDNFiles" `
-SPFxAssetsPath <path-of-assets>
```
The PowerShell script requires some input arguments, which are:
@@ -96,7 +96,6 @@ The PowerShell script requires some input arguments, which are:
* **ConfigureCDN**: an optional switch to instruct the script to create and configure an Office 365 CDN that will host the SPFx client-side web parts.
* **CDNSiteName**: the relative URL of a SharePoint site collection that will be create to host the CDN files, if you select to create and configure the Office 365 CDN.
* **CDNLibraryName**: the name of the document library that will be created to host the CDN files.
* **SPFxAssetsPath**: the file system path of the folder where your SPFx client-side web parts assets are stored. Usually it is the _temp/deploy_ subfolder of your SFPx solution.
> Notice that you can skip the configuration of the CDN in Microsoft Office 365, and you can instead use whatever else hosting solution of your choice.

0 comments on commit 1eb89c8

Please sign in to comment.