# supply-chain-office-integration

**Repository Path**: mirrors_Azure/supply-chain-office-integration

## Basic Information

- **Project Name**: supply-chain-office-integration
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-08-08
- **Last Updated**: 2026-04-18

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

## Running in localhost

Before running for the first time, generate a certificate and a key with the script borrowed from [here](https://github.com/OfficeDev/Office-Add-in-Nodejs-ServerAuth/blob/7d125dd2862c629ee10baddffe981e84f0ed3b2d/ss_certgen.sh).
Put the `server.crt` and the `server.key` file into the `.\cert` folder.

On Linux, Mac and Git Bash for Windows

```
$ bash ss_certgen.sh
```
On Cygwin for Windows

```
$ bash -o igncr ss_certgen.sh
```

To install dependencies:

```
$ npm install
```

To start the server:

```
$ npm start
```

Open Web browser https://localhost:8443/ and make the certificate trusted by adding it to the trusted root authorities. 
Also [enable localhost deguging on Edge](https://blogs.msdn.microsoft.com/msgulfcommunity/2015/07/01/how-to-debug-localhost-on-microsoft-edge/): 
```
CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"
```

To test that the REST API is accessible and working, you can issue a request to the ping endpoint and expect a hash to be returned:

``` 
$ curl https://localhost:8443/api/key
```


## Configuration 

To run locally, copy the file `dev.sample.json` in the `config` folder and create a new file called `dev.private.json`.

Fill in the following values:

`SUPPLY_CHAIN_SERVICES_ENDPOINT`: The URL for the supply chain services - the endpoint needs to support SSL
`OUTLOOK_SERVICE_ENDPOINT`: The URL for the Outlook Service - the endpoint needs to support SSL
`STORAGE_CONNECTION_STRING`: The storage connection string in Azure.


## Deployment

Run the gulp dist task and provide the URL behind which you are deploying, for example:

```
$ gulp dist --url https://supply-chain-web-app.azurewebsites.net/
```

Above command rewrites the manifest to point to the correct resources.

The result is a dist folder that you can push to your hosting environment, for example:

```
$ cd dist
# Below in case you want to build the dependencies locally
$ npm install --production
$ git init .
$ git add *
$ git commit -m "Deployment"
$ git push https://supply-chain-web-app.scm.azurewebsites.net:443/supply-chain-web-app.git master
```