Bazsalanszky/destreamer
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Merge pull request #368 from TomasHubelbauer/patch-1

Browse source 
Mention TokenCache in the own browser usage section
This commit is contained in:
lukaarma 2021-04-15 14:50:18 +02:00 committed by GitHub
commit cb689336d8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -57,19 +57,13 @@ Note that destreamer won't run in an elevated (Administrator/root) shell. Runnin
## Can i plug in my own browser? ## Can i plug in my own browser?
Yes, yes you can. This may be useful if your main browser has some authentication plugins that are required for you to logon to your Microsoft Stream tenant. Yes, yes you can. This may be useful if your main browser has some authentication plugins that are required for you to logon to your Microsoft Stream tenant.
To use your own browser for the authentication part, locate the following snippet in `src/destreamer.ts`: To use your own browser for the authentication part, locate the following snippet in `src/destreamer.ts` and `src/TokenCache.ts`:
```typescript ```typescript
const browser: puppeteer.Browser = await puppeteer.launch({ const browser: puppeteer.Browser = await puppeteer.launch({
executablePath: getPuppeteerChromiumPath(), executablePath: getPuppeteerChromiumPath(),
headless: false, // …
userDataDir: (argv.keepLoginCookies) ? chromeCacheFolder : undefined, });
args: [
'--disable-dev-shm-usage',
'--fast-start',
'--no-sandbox'
]
});
``` ```
Now, change `executablePath` to reflect the path to your browser and profile (i.e. to use Microsoft Edge on Windows): Now, change `executablePath` to reflect the path to your browser and profile (i.e. to use Microsoft Edge on Windows):