Updated Notify_pushjet (markdown)

Chris Caron 2019-09-07 16:47:46 -04:00
parent 43dfc17f47
commit 2ee8d50ca5

@ -8,16 +8,20 @@
### Syntax
If you want to use your own custom Pushjet server, then the following identify the syntax you may use:
* **pjet**://**{secret_key}**@**{host}**
* **pjet**://**{secret_key}**@**{host}**:**{port}**
* **pjets**://**{secret_key}**@**{host}**
* **pjets**://**{secret_key}**@**{host}**:**{port}**
* `pjet://{host}/{secret_key}`
* `pjet://{host}:{port}/{secret_key}`
* `pjet://{user}:{password}@{host}/{secret_key}`
* `pjets://{host}/{secret_key}`
* `pjets://{host}:{port}/{secret_key}`
* `pjets://{user}:{password}@{host}/{secret_key}`
### Parameter Breakdown
| Variable | Required | Description
| ----------- | -------- | -----------
| secret_key | Yes | The Secret Key associated with your Pushjet account.
| host | Yes | The Pushjet server you're hosting
| host | Yes | The Pushjet server you're hosting
| user | No | If you're system is set up to use HTTP-AUTH, you can provide _username_ for authentication to it.
| password | No | If you're system is set up to use HTTP-AUTH, you can provide _password_ for authentication to it.
| port | No | The Pushjet port optional and only required if you're hosting your own notification server on a different port then the standard ones. By default the port is **80** for **pjet://** and **443** for all **pjets://** references.
#### Example