Merge branch 'images/registry' into 'main'

Point image references at the new registry

See merge request coffey-labs/unraid-templates!1
This commit was merged in pull request #1.
This commit is contained in:
2026-09-20 22:49:52 -07:00
2 changed files with 10 additions and 10 deletions
+3 -3
View File
@@ -6,7 +6,7 @@ Community Applications reads for the repository listing.
| App | Template | Image | Licence of the app |
| --- | --- | --- | --- |
| [ihasmail](https://ihasmail.org) — immutable webmail for Stalwart Mail Server | [`templates/ihasmail.xml`](templates/ihasmail.xml) | `ghcr.io/coffey-labs/ihasmail:latest` (amd64, arm64) | AGPL-3.0-or-later |
| [ihasmail](https://ihasmail.org) — immutable webmail for Stalwart Mail Server | [`templates/ihasmail.xml`](templates/ihasmail.xml) | `registry.coffeylabs.org/coffey-labs/ihasmail:latest` (amd64, arm64) | AGPL-3.0-or-later |
## Installing
@@ -19,7 +19,7 @@ in the **Template** drop-down of **Docker → Add Container**:
```sh
wget -P /boot/config/plugins/dockerMan/templates-user/ \
https://raw.githubusercontent.com/Coffey-Labs/unraid-templates/main/templates/ihasmail.xml
https://git.coffeylabs.org/coffey-labs/unraid-templates/-/raw/main/templates/ihasmail.xml
```
## ihasmail
@@ -47,7 +47,7 @@ Every other setting is documented at
[docs.ihasmail.org/configure](https://docs.ihasmail.org/configure/).
Problems with the app go to
[Coffey-Labs/ihasmail issues](https://github.com/Coffey-Labs/ihasmail/issues);
[coffey-labs/ihasmail issues](https://git.coffeylabs.org/coffey-labs/ihasmail/-/work_items);
problems with the template go to the issues on this repository.
## Licence
+7 -7
View File
@@ -1,19 +1,19 @@
<?xml version="1.0" encoding="utf-8"?>
<Container version="2">
<Name>ihasmail</Name>
<Repository>ghcr.io/coffey-labs/ihasmail:latest</Repository>
<Registry>https://github.com/Coffey-Labs/ihasmail/pkgs/container/ihasmail</Registry>
<Repository>registry.coffeylabs.org/coffey-labs/ihasmail:latest</Repository>
<Registry>https://git.coffeylabs.org/coffey-labs/ihasmail/container_registry</Registry>
<Network>bridge</Network>
<Shell>sh</Shell>
<Privileged>false</Privileged>
<Support>https://github.com/Coffey-Labs/ihasmail/issues</Support>
<Project>https://github.com/Coffey-Labs/ihasmail</Project>
<ReadMe>https://raw.githubusercontent.com/Coffey-Labs/ihasmail/main/README.md</ReadMe>
<Support>https://git.coffeylabs.org/coffey-labs/ihasmail/-/work_items</Support>
<Project>https://git.coffeylabs.org/coffey-labs/ihasmail</Project>
<ReadMe>https://git.coffeylabs.org/coffey-labs/ihasmail/-/raw/main/README.md</ReadMe>
<Overview>Immutable webmail for Stalwart Mail Server. Mail, calendars, contacts, files and filters in one responsive app that works as well on a phone as on a desktop, talking only JMAP to a Stalwart you already run. There is no database, no IMAP or SMTP configuration and nothing to migrate between versions: everything durable stays in Stalwart, and the container is disposable. The root filesystem runs read-only; the only optional write is a session file, kept so that nobody is signed out when the container restarts. Try it first at https://demo.ihasmail.com and read the docs at https://docs.ihasmail.org.</Overview>
<Category>Productivity: Network:Web Network:Messenger</Category>
<WebUI>http://[IP]:[PORT:8080]</WebUI>
<TemplateURL>https://raw.githubusercontent.com/Coffey-Labs/unraid-templates/main/templates/ihasmail.xml</TemplateURL>
<Icon>https://raw.githubusercontent.com/Coffey-Labs/unraid-templates/main/templates/ihasmail.png</Icon>
<TemplateURL>https://git.coffeylabs.org/coffey-labs/unraid-templates/-/raw/main/templates/ihasmail.xml</TemplateURL>
<Icon>https://git.coffeylabs.org/coffey-labs/unraid-templates/-/raw/main/templates/ihasmail.png</Icon>
<ExtraParams>--read-only --tmpfs /tmp --user 99:100</ExtraParams>
<ExtraSearchTerms>webmail email mail stalwart jmap calendar contacts immutable</ExtraSearchTerms>
<Requires>A Stalwart Mail Server 0.16 or newer that this container can reach over the network. ihasmail is a mail client, not a mail server: it holds no mail, no accounts and no database of its own. Put it behind a reverse proxy with HTTPS before exposing it beyond your LAN.</Requires>