build: strip trailing whitespace in docs (#17488)
This commit is contained in:
parent
1c7b3026a6
commit
a82bbd010e
12 changed files with 86 additions and 32 deletions
|
@ -48,21 +48,21 @@ the result of the overall security of the framework foundation
|
|||
your code. As such, it is your responsibility to follow a few important best
|
||||
practices:
|
||||
|
||||
* **Keep your application up-to-date with the latest Electron framework release.**
|
||||
When releasing your product, you’re also shipping a bundle composed of Electron,
|
||||
Chromium shared library and Node.js. Vulnerabilities affecting these components
|
||||
may impact the security of your application. By updating Electron to the latest
|
||||
version, you ensure that critical vulnerabilities (such as *nodeIntegration bypasses*)
|
||||
* **Keep your application up-to-date with the latest Electron framework release.**
|
||||
When releasing your product, you’re also shipping a bundle composed of Electron,
|
||||
Chromium shared library and Node.js. Vulnerabilities affecting these components
|
||||
may impact the security of your application. By updating Electron to the latest
|
||||
version, you ensure that critical vulnerabilities (such as *nodeIntegration bypasses*)
|
||||
are already patched and cannot be exploited in your application.
|
||||
|
||||
* **Evaluate your dependencies.** While NPM provides half a million reusable packages,
|
||||
it is your responsibility to choose trusted 3rd-party libraries. If you use outdated
|
||||
libraries affected by known vulnerabilities or rely on poorly maintained code,
|
||||
* **Evaluate your dependencies.** While NPM provides half a million reusable packages,
|
||||
it is your responsibility to choose trusted 3rd-party libraries. If you use outdated
|
||||
libraries affected by known vulnerabilities or rely on poorly maintained code,
|
||||
your application security could be in jeopardy.
|
||||
|
||||
* **Adopt secure coding practices.** The first line of defense for your application
|
||||
is your own code. Common web vulnerabilities, such as Cross-Site Scripting (XSS),
|
||||
have a higher security impact on Electron applications hence it is highly recommended
|
||||
* **Adopt secure coding practices.** The first line of defense for your application
|
||||
is your own code. Common web vulnerabilities, such as Cross-Site Scripting (XSS),
|
||||
have a higher security impact on Electron applications hence it is highly recommended
|
||||
to adopt secure software development best practices and perform security testing.
|
||||
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ Electron's [autoUpdater](../api/auto-updater.md) module.
|
|||
## Using `update.electronjs.org`
|
||||
|
||||
GitHub's Electron team maintains [update.electronjs.org], a free and open-source
|
||||
webservice that Electron apps can use to self-update. The service is designed
|
||||
webservice that Electron apps can use to self-update. The service is designed
|
||||
for Electron apps that meet the following criteria:
|
||||
|
||||
- App runs on macOS or Windows
|
||||
|
@ -31,13 +31,13 @@ Invoke the updater from your app's main process file:
|
|||
require('update-electron-app')()
|
||||
```
|
||||
|
||||
By default, this module will check for updates at app startup, then every ten
|
||||
minutes. When an update is found, it will automatically be downloaded in the background. When the download completes, a dialog is displayed allowing the user
|
||||
By default, this module will check for updates at app startup, then every ten
|
||||
minutes. When an update is found, it will automatically be downloaded in the background. When the download completes, a dialog is displayed allowing the user
|
||||
to restart the app.
|
||||
|
||||
If you need to customize your configuration, you can
|
||||
If you need to customize your configuration, you can
|
||||
[pass options to `update-electron-app`][update-electron-app]
|
||||
or
|
||||
or
|
||||
[use the update service directly][update.electronjs.org].
|
||||
|
||||
## Using `electron-builder`
|
||||
|
@ -51,7 +51,7 @@ update mechanism, meaning that the rest of this documentation will not apply to
|
|||
## Deploying an Update Server
|
||||
|
||||
If you're developing a private Electron application, or if you're not
|
||||
publishing releases to GitHub Releases, it may be necessary to run your own
|
||||
publishing releases to GitHub Releases, it may be necessary to run your own
|
||||
update server.
|
||||
|
||||
Depending on your needs, you can choose from one of these:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue