Skip to content

Commit c68c0fa

Browse files
committed
Add Push Notifications section
1 parent a333540 commit c68c0fa

File tree

2 files changed

+77
-0
lines changed

2 files changed

+77
-0
lines changed

.vitepress/config.mjs

+1
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,7 @@ export default defineConfig({
4141
{ text: 'Installation', link: '/running-pixelfed/installation' },
4242
{ text: 'Configuration', link: '/running-pixelfed/configuration' },
4343
{ text: 'Administration', link: '/running-pixelfed/administration' },
44+
{ text: 'Push Notifications', link: '/running-pixelfed/push-notifications' },
4445
{ text: 'CLI Cheatsheet', link: '/running-pixelfed/cli-cheatsheet' },
4546
{ text: 'Troubleshooting', link: '/running-pixelfed/troubleshooting' }
4647
]
+76
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
title = "Pixelfed Push Notifications"
3+
summary = "Instructions on Push Notifications support"
4+
weight = 20
5+
[menu]
6+
[menu.docs]
7+
---
8+
9+
# Push Notifications
10+
11+
::: warning
12+
Push Notifications are experimental and only supported on our official mobile apps.
13+
:::
14+
15+
[[toc]]
16+
17+
## Overview
18+
19+
Push notifications enhance the Pixelfed experience by delivering real-time updates directly to users' devices. These notifications inform users about new followers, likes, comments, and other important interactions, keeping them engaged with their community.
20+
21+
## Availability
22+
23+
Currently, push notifications are limited to the official Pixelfed mobile applications. We plan to support web push and 3rd party applications in the future.
24+
25+
26+
## Instance Approval and API Key Requirement
27+
28+
To enable push notifications on your Pixelfed instance, you must obtain manual approval and a unique API key from the Pixelfed team. This process helps maintain the integrity and performance of the push notification service across the network.
29+
30+
### Steps to Enable Push Notifications for Your Instance
31+
32+
1) **Contact the Pixelfed Team**: Reach out to us at [email protected] with your request to enable push notifications for your instance. Please include the following information:
33+
- Email subject should contain "**Push Notification Gateway Request**"
34+
- Your instance's domain name
35+
- Administrator contact details
36+
- Mention you will abide by our [Code of Conduct](https://github.com/pixelfed/pixelfed/blob/dev/CODE_OF_CONDUCT.md)
37+
- Brief description of your instance and community
38+
39+
2) **Await Approval**: The Pixelfed team will review your request and may reach out for additional information. Approval is granted on a case-by-case basis to ensure compliance with our guidelines.
40+
41+
3) **Receive Your API Key**: Once approved, you will be provided with a unique API key specific to your instance.
42+
43+
4) **Configure Your Instance**: Update your instance settings to include the provided API key. Refer to the [Configuration](#configuration) docs.
44+
45+
## Configuration
46+
47+
Once you recieve your API key, you need to perform the following steps to enable Push Notification support on your server.
48+
49+
1) Add your API key to your `.env`
50+
```
51+
PIXELFED_PUSHGATEWAY_KEY=XXXXXXXXXX
52+
```
53+
54+
2) Re-cache config by running the following command:
55+
```
56+
php artisan config:cache
57+
```
58+
59+
3) Run the following command and force a re-check:
60+
```
61+
php artisan app:push-gateway-refresh
62+
```
63+
64+
4) Re-deploy or run the following command (if you are using the Horizon job queue):
65+
```
66+
php artisan horizon:terminate
67+
```
68+
69+
## Contact Us
70+
71+
For any questions or to begin the approval process for push notifications on your instance, please reach out:
72+
73+
74+
- Website: https://pixelfed.org
75+
76+
We appreciate your cooperation as we work towards supporting third-party apps while maintaining a secure and efficient network for all Pixelfed users.

0 commit comments

Comments
 (0)