一个社交发布平台。
Idno is under active development and requires PHP 8.3+ with selected extensions, together with a supported database backend. You can find detailed installation instructions here:
Unofficial install packages, which are periodically built from the latest code, are available:
You can opt to check out the work-in-progress development code from the git repository:
git clone https://github.com/idno/idno.gitcd idno; composer installYou can install Idno directly from composer using: composer create-project idno/idno
Optionally, you can install the latest bleeding edge code the same way: composer create-project idno/idno -s dev
By default, Idno processes events synchronously — that is, things like Webmention pings, syndication, and ActivityPub delivery all happen inside the web request that triggered them. This works, but it makes page saves slow and means a timeout or crash loses the work.
Enabling the asynchronous queue moves all of that into a background worker. The web request just drops an event into the database and returns immediately; the worker picks it up and processes it separately.
This is required for ActivityPub. Follow-accept delivery, post distribution to followers, and update/delete propagation are all dispatched through the queue. If the worker is not running, those events sit in the database unprocessed and remote servers will never receive them.
Add this line to your config.ini:
event_queue = 'AsynchronousQueue'Without this line (or with the default SynchronousQueue), all events are
processed inline during the web request.
sudo -u www-data IDNO_DOMAIN='your.domain' ./idno.php service-event-queue| Option | Default | Description |
|---|---|---|
--queue |
default |
Named queue to process |
--interval |
1 |
Seconds to sleep between polling cycles |
How it works: The worker runs an infinite loop. Each cycle it:
/service/queue/dispatch/{id},
which triggers the event handler (e.g., signing and POSTing an ActivityPub
activity to a remote inbox).--interval seconds, then repeats.If the worker dies, queued events pile up in the database but are not lost. They will be processed once the worker is restarted.
The worker must stay running permanently. The simplest way is a systemd service
unit. Create /etc/systemd/system/idno-queue.service, taking care to replace the
values here with your own paths, users, and domains:
[Unit]
Description=Idno async event queue worker
After=network.target
[Service]
Type=simple
User=www-data
Environment=IDNO_DOMAIN=your.domain
WorkingDirectory=/var/www/idno
ExecStart=/var/www/idno/idno.php service-event-queue #replace with your path
Restart=always
RestartSec=5
[Install]
WantedBy=multi-user.targetThen enable and start it:
sudo systemctl daemon-reload
sudo systemctl enable --now idno-queueCheck status any time with:
sudo systemctl status idno-queue
sudo journalctl -u idno-queue -f # tail the logsIf you don't have access to systemd (e.g. shared hosting), you can use cron
instead. The --once flag makes the worker process one batch of pending events
and exit, which is ideal for cron:
* * * * * sudo -u www-data IDNO_DOMAIN='your.domain' /var/www/idno/idno.php service-event-queue --once >> /var/log/idno-queue.log 2>&1This processes pending events once per minute. Events may take up to 60 seconds to be delivered (compared to ~1 second with the systemd worker above).
If you need periodic background tasks (triggered via cron/minute,
cron/hourly, and cron/daily events), start the cron service the same way:
sudo -u www-data IDNO_DOMAIN='your.domain' ./idno.php service-cronYou can create a second systemd unit (idno-cron.service) following the same
pattern as above if you want it managed automatically.
When you update Idno core or any plugins, restart both services so they pick up the new code:
sudo systemctl restart idno-queue idno-cronFor details on contributing to the Idno project, please read CONTRIBUTING.md.
This project exists thanks to all the people who contribute. [Contribute].
Except for included third-party projects, Idno is (c) The Open Community Company LLC.
Unless otherwise stated, Idno is licensed under the Apache Software License 2.0. See LICENSE for more information.
Idno logos are (c) Idno, Inc. Permission from Idno, Inc is required to use the Idno name or logo as part of any project, product, service, domain or company name, except as included in official themes distributed by Idno.
Logos of external services are (c) their respective owners. All rights reserved.
Third party libraries are licensed separately.
Thanks to BrowserStack for providing the infrastructure that allows us to test in real browsers.
暂无开放 Issues，或尚未同步最近议题。