2024-03-26 22:39:37 +02:00
|
|
|
# hydroxide-push
|
|
|
|
### *Forked from [Hydroxide](https://github.com/emersion/hydroxide)*
|
2017-09-03 21:21:22 +03:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
## Push notifications for Proton Mail mobile via a UP provider
|
2017-12-03 13:32:33 +02:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
Protonmail depends on Google services to deliver push notifications,
|
|
|
|
This is a stripped down version of [Hydroxide](https://github.com/emersion/hydroxide)
|
|
|
|
to get notified of new mail. See original repo for details on operation.
|
2019-03-22 22:08:15 +02:00
|
|
|
|
2017-12-09 15:22:54 +02:00
|
|
|
## Setup
|
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
Download (soon), build the binary or the container image or pull the container image yourself.
|
|
|
|
Simplest way is to run the container image.
|
2017-12-09 15:22:54 +02:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
Login and push gateway details are saved under `$HOME/.config/hydroxide`. The container
|
|
|
|
image saves configuration under `/data`, so mount a named volume or host directory there.
|
|
|
|
The examples below use a named volume.
|
2017-12-09 15:22:54 +02:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
If using Docker, substitute `podman` with `docker` in the examples.
|
2017-12-09 15:22:54 +02:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
Binary:
|
2017-12-09 15:22:54 +02:00
|
|
|
```shell
|
2024-03-26 22:39:37 +02:00
|
|
|
./hydroxide-push auth your.proton@email.address
|
2017-12-09 15:22:54 +02:00
|
|
|
```
|
2024-03-26 22:39:37 +02:00
|
|
|
Container:
|
2017-09-03 21:21:22 +03:00
|
|
|
```shell
|
2024-03-26 22:39:37 +02:00
|
|
|
podman run -it --rm -v hydroxide-config:/data ghcr.io/0ranki/hydroxide-push auth your.proton@email.address
|
2017-12-03 13:32:33 +02:00
|
|
|
```
|
2024-03-26 22:39:37 +02:00
|
|
|
You will be prompted for the Proton account credentials and the details for the push server. Proton credentials are stored encrypted form.
|
2017-12-03 13:32:33 +02:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
The auth flow generates a separate password for the bridge, which is stored in plaintext
|
|
|
|
to `$HOME/.config/notify.json`. Unlike upstream `hydroxide`, there is no service listening on any port,
|
|
|
|
all communications is internal to the program.
|
2019-03-22 22:08:15 +02:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
### Reconfigure push server
|
2024-03-26 22:47:28 +02:00
|
|
|
Binary:git.oranki.net/jarno/hydroxide-push:latest
|
2019-03-22 22:08:15 +02:00
|
|
|
```shell
|
2024-03-26 22:39:37 +02:00
|
|
|
hydroxide-push setup-ntfy
|
2019-03-22 22:08:15 +02:00
|
|
|
```
|
2024-03-26 22:39:37 +02:00
|
|
|
Container:
|
2017-12-03 13:32:33 +02:00
|
|
|
```shell
|
2024-03-26 22:39:37 +02:00
|
|
|
podman run -it --rm -v hydroxide-config:/data ghcr.io/0ranki/hydroxide-push setup-ntfy
|
2017-09-03 21:21:22 +03:00
|
|
|
```
|
2024-03-26 22:39:37 +02:00
|
|
|
You'll be asked for the base URL of the push server, and the topic. These will probably
|
|
|
|
be combined to a single string in future versions.
|
2017-09-03 21:21:22 +03:00
|
|
|
|
2024-03-26 22:39:37 +02:00
|
|
|
**NOTE:** Authentication for the push endpoint is not yet supported.
|
2018-01-13 12:40:21 +02:00
|
|
|
|
2017-09-03 21:21:22 +03:00
|
|
|
## License
|
|
|
|
|
|
|
|
MIT
|