Update binwiederhier/ntfy Docker tag to v2 #103
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/binwiederhier-ntfy-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.28.0->v2.15.0Release Notes
binwiederhier/ntfy (binwiederhier/ntfy)
v2.15.0Compare Source
This release adds a
require-loginflag to topics, which forces users to log in before they can use the web app. This is useful for self-hosters and will obviously not be enabled on ntfy.sh.Features:
require-loginflag to redirect to login page if not logged in (#1434/#238/#1329, thanks to @theatischbein for implementing most of this)Bug fixes + maintenance:
database lockederrors (#1397, #1391, thanks to @timofej673)nopayments,nofirebaseandnowebpushto allow excluding external dependencies, useful forpackaging in Debian (#1420, discussion in #1258, thanks to @thekhalifa for packaging ntfy for Debian/Ubuntu)
v2.14.0Compare Source
This release adds support for declarative users, declarative ACL entries and declarative tokens. This allows you to define users, ACL entries and tokens in the config file, which is useful for static deployments or deployments that use a configuration management system.
It also adds support for pre-defined templates and custom templates for enhanced JSON webhook support, as well as advanced template functions based on the Sprig functions.
❤️ If you like ntfy, please consider sponsoring me via GitHub Sponsors, Liberapay, Bitcoin (
1626wjrw3uWk9adyjCfYwafw4sQWujyjn8), or by buying a paid plan via the web app. ntfywill always remain open source.
Features:
v2.13.0Compare Source
This is a relatively small release, mainly to support IPv6 and to add more sophisticated
proxy header support. Quick reminder that if you like ntfy, please consider sponsoring us
via GitHub Sponsors and Liberapay, or buying a paid plan via the web app.
ntfy will always remain open source.
Features:
X-Client-IP,X-Real-IP,Forwardedheaders for rate limiting viaproxy-forwarded-headerandproxy-trusted-hosts(#1360 / #1252, thanks to @pixitha)ntfy publish(#1382, thanks to @srevn)Languages
v2.12.0Compare Source
This is mainly a maintenance release that updates dependencies, though since it's been over a year, there are a few new features and bug fixes as well.
Thanks to everyone who contributed to this release, and special thanks to @wunter8 for his continued user support in Discord/Matrix/GitHub! You rock, man!
Features:
ntfy webpush --output-file(#1138, thanks to @nogweii)latestsubscription param for grabbing just the most recent message (#1216, thanks to @wunter8)NTFY_PASSWORD_HASHinntfy usercommand instead of raw password (#1340, thanks to @Tom-Hubrecht for implementing)v1/usersAPI (#1267, thanks to @wunter8 for implementing)ntfy-client.service(#1002, thanks to @dandersch)Bug fixes + maintenance:
Dateheader to outgoing emails to avoid rejection (#1141, thanks to @pcouy)cacheandfirebasevia JSON publishing (#1119/#1123, thanks to @stendler)Documentation:
Languages
v2.11.0Compare Source
This is a tiny release that fixes a database index issue that caused performance issues on ntfy.sh. It also fixes a bug in the rate visitor logic that caused rate visitors to be assigned to seemingly random topics. Nothing major this time.
❤️ Quick reminder that if you like ntfy, please consider sponsoring us via GitHub Sponsors and Liberapay, or buying a paid plan via the web app. ntfy will always remain open source.
Bug fixes + maintenance:
idx_topicto themessagestable to fix performance issues on ntfy.sh (no ticket, big thanks to @tcaputi for finding this issue)config.js(#1098, thanks to @wunter8)v2.10.0Compare Source
This release adds support for message templating: in the ntfy server, which allows you to include a message and/or title template that will be filled with values from a JSON body (e.g.
curl -gd '{"alert":"Disk space low"}' "ntfy.sh/mytopic?tpl=1&m={{.alert}}"). This is great for services that let you specify a webhook URL but do not let you change the webhook body (such as GitHub, or Grafana).Features:
That's all. Short and sweet.
If you like ntfy, please consider donating via GitHub Sponsors, Liberapay, or by buying a ntfy Pro plan.
v2.9.0Compare Source
A small release after a long pause (lots of day job work). This release adds for larger messages and longer message delays in scheduled delivery messages. The web app also now supports pasting images from the clipboard. Other than that, only a few bug fixes and documentation updates, and a teeny tiny breaking change 😬.
⚠️ Breaking changes:
Rate-Topicsheader was removed due to a DoS issue (see #1048). This only affects installations withvisitor-subscriber-rate-limiting: true, which is not the default and likely very rarely used. Normally I'd never remove a feature, but this is a security issue, and likely affects almost nobody.Features:
message-delay-limit(see message limits, #1019, thanks to @MrChadMWood for reporting)message-size-limit(use at your own risk, see message limits, #836/#1050, thanks to @zhzy0077 for implementing this, and to @nkjshlsqja7331 for reporting)Bug fixes + maintenance:
Rate-Topicsheader due to DoS security issue ifvisitor-subscriber-rate-limiting: true(#1048)Documentation:
mkdocs-simple-hooks(#1016, thanks to @Tom-Hubrecht)❤️ Special thanks to @wunter8 for always answering all the questions on Discord/Matrix!
v2.8.0Compare Source
This release brings a handful of random bug fixes: two unrelated access control list fixes, a fix around web app crashes for languages with underscores in the language code (e.g.
zh_Hant,zh_Hans,pt_BR, ...), a workaround for thePriorityheader (often used in Cloudflare setups), and support among others support for HTML-only emails (finally), web app crash fixesBug fixes + maintenance:
tzdatato Docker images for amd64 image (#894, #307)Priorityheader if it resembles an RFC 9218 value (#851/#895, thanks to @gusdleon, see also #351, #353, #461)Additional languages:
v2.7.0Compare Source
This release ships Markdown support for the web app (not in the Android app yet), and adds support for right-to-left languages (RTL) in the web app. It also fixes a few issues around date/time formatting, internationalization support, a CLI auth bug.
⚠️ Furthermore, it fixes a security issue around access tokens getting erroneously deleted for other users in a specific scenario. This was a denial-of-service-type security issue, since it effectively allowed a single user to deny access to all other users of a ntfy instance. Please note that while tokens were erroneously deleted, nobody but the token owner ever had access to it. Please refer to the ticket for details. Please upgrade your ntfy instance if you run a multi-user system.
Features:
⚠️ Security:
Bug fixes + maintenance:
client.ymlfor an individual subscription to remove the Authorization header (#829, thanks to @tomeon for reporting and to @wunter8 for fixing)Documentation:
v2.6.2Compare Source
With this release, the ntfy web app now contains a progressive web app (PWA) with Web Push support, which means you'll be able to install the ntfy web app on your desktop or phone similar to a native app (even on iOS! 🥳). Installing the PWA gives ntfy web its own launcher, a standalone window, push notifications, and an app badge with the unread notification count.
On top of that, this release also brings dark mode 🧛🌙 to the web app.
🙏 A huge thanks for this release goes to @nimbleghost, for basically implementing the Web Push / PWA and dark mode feature by himself. I'm really grateful for your contributions.
❤️ If you like ntfy, please consider sponsoring us via GitHub Sponsors and Liberapay, or buying a paid plan via the web app (20% off if you use promo code
MYTOPIC). ntfy will always remain open source.Features:
Bug fixes:
ntfy pub %segfaulting (#760, thanks to @clesmian for reporting)<topic>+<token>@​<domain>email syntax (#773, thanks to gingervitiz for reporting)Maintenance:
Changes in tarball/zip naming:
Due to a change in GoReleaser, some of the binary release
archives now have slightly different names. My apologies if this causes issues in the downstream projects that use ntfy:
ntfy_v${VERSION}_windows_x86_64.zip->ntfy_v${VERSION}_windows_amd64.zipntfy_v${VERSION}_linux_x86_64.tar.gz->ntfy_v${VERSION}_linux_amd64.tar.gzntfy_v${VERSION}_macOS_all.tar.gz->ntfy_v${VERSION}_darwin_all.tar.gzv2.6.1Compare Source
(⚠️ This release is superseded by v2.6.2)
With this release, the ntfy web app now contains a progressive web app (PWA) with Web Push support, which means you'll be able to install the ntfy web app on your desktop or phone similar to a native app (even on iOS! 🥳). Installing the PWA gives ntfy web its own launcher, a standalone window, push notifications, and an app badge with the unread notification count.
On top of that, this release also brings dark mode 🧛🌙 to the web app.
🙏 A huge thanks for this release goes to @nimbleghost, for basically implementing the Web Push / PWA and dark mode feature by himself. I'm really grateful for your contributions.
❤️ If you like ntfy, please consider sponsoring us via GitHub Sponsors and Liberapay, or buying a paid plan via the web app (20% off if you use promo code
MYTOPIC). ntfy will always remain open source.Features:
Bug fixes:
ntfy pub %segfaulting (#760, thanks to @clesmian for reporting)<topic>+<token>@​<domain>email syntax (#773, thanks to gingervitiz for reporting)v2.6.0Compare Source
(⚠️ This release is superseded by v2.6.2)
With this release, the ntfy web app now contains a progressive web app (PWA) with Web Push support, which means you'll be able to install the ntfy web app on your desktop or phone similar to a native app (even on iOS! 🥳). Installing the PWA gives ntfy web its own launcher, a standalone window, push notifications, and an app badge with the unread notification count.
On top of that, this release also brings dark mode 🧛🌙 to the web app.
🙏 A huge thanks for this release goes to @nimbleghost, for basically implementing the Web Push / PWA and dark mode feature by himself. I'm really grateful for your contributions.
❤️ If you like ntfy, please consider sponsoring us via GitHub Sponsors and Liberapay, or buying a paid plan via the web app (20% off if you use promo code
MYTOPIC). ntfy will always remain open source.Features:
Bug fixes:
ntfy pub %segfaulting (#760, thanks to @clesmian for reporting)<topic>+<token>@​<domain>email syntax (#773, thanks to gingervitiz for reporting)v2.5.0Compare Source
This release brings a number of new features, including support for text-to-speech style phone calls, an admin API to manage users and ACL (currently in beta, and hence undocumented), and support for authorized access to upstream servers via the
upstream-access-tokenconfig option.❤️ If you like ntfy, please consider sponsoring me via GitHub Sponsors and Liberapay, or by buying a paid plan via the web app (20% off if you use promo code
MYTOPIC). ntfy will always remain open source.Features:
X-Callheader (no ticket)v1/users+v1/users/access(intentionally undocumented as of now, #722, thanks to @CreativeWarlock for sponsoring this ticket)upstream-access-tokenconfig option to allow authorized access to upstream servers (no ticket)Bug fixes + maintenance:
quoted-printablein incoming emails (#719, thanks to @Aerion)v2.4.0Compare Source
This release adds a tiny
v1/statsendpoint to expose how many messages have been published, and adds suport to encode theX-Title,X-MessageandX-Tagsheader as RFC 2047. It's a pretty small release, and mainly enables the release of the new ntfy.sh website.❤️ If you like ntfy, please consider sponsoring me via GitHub Sponsors and Liberapay, or by buying a paid plan via the web app. ntfy will always remain open source.
Features:
ntfy publishandntfy subscribeonly) can now be installed via Homebrew (thanks to @Moulick)v1/statsendpoint to expose messages stats (no ticket)Bug fixes + maintenance:
ntfy subnow uses default auth credentials as defined inclient.yml(#698, thanks to @CrimsonFez for reporting, and to @wunter8 for fixing it)Documentation:
Additional languages:
v2.3.1Compare Source
Changelog
a75fb08Tidyv2.3.0Compare Source
This release primarily fixes an issue with delayed messages, and it adds support for Go's profiler (if enabled), which will allow investigating usage spikes in more detail. There will likely be a follow-up release this week to fix the actual spikes caused by iOS devices.
Features:
pprofprofiler, if enabled (relates to #677)Bug fixes + maintenance:
v2.2.0Compare Source
With this release, ntfy is now able to expose metrics via a
/metricsendpoint for Prometheus, if enabled. The endpoint exposes about 20 different counters and gauges, from the number of published messages and emails, to active subscribers, visitors and topics. If you'd like more metrics, pop in the Discord/Matrix or file an issue on GitHub.On top of this, you can now use access tokens in the ntfy CLI (defined in the
client.ymlfile), fixed a bug inntfy subscribe, removed the dependency on Google Fonts, and more.🔥 Reminder: Purchase one of three ntfy Pro plans for 50% off for a limited time (if you use promo code
MYTOPIC). ntfy Pro gives you higher rate limits and lets you reserve topic names. Buy through web app.❤️ If you don't need ntfy Pro, please consider sponsoring ntfy via GitHub Sponsors and Liberapay. ntfy will stay open source forever.
Features:
/metricsendpoint for Prometheus if configured (#210, thanks to @rogeliodh for reporting)client.ymlfor publishing and subscribing (#653, thanks to @wunter8)Bug fixes + maintenance:
ntfy sub --poll --from-configwill now include authentication headers from client.yml (if applicable) (#658, thanks to @wunter8)Documentation:
v2.1.2Compare Source
This is a hotfix release, mostly to combat the ridiculous amount of Matrix requests with invalid/dead pushkeys, and the corresponding HTTP 507 responses the ntfy.sh server is sending out. We're up to >600k HTTP 507 responses per day 🤦. This release solves this issue by rejecting Matrix pushkeys, if nobody has subscribed to the corresponding topic for 12 hours.
The release furthermore reverts the default rate limiting behavior for UnifiedPush to be publisher-based, and introduces a flag to enable subscriber-based rate limiting for high volume servers.
Features:
Bug fixes + maintenance:
client.yml(#650, thanks to @Xinayder)visitor-subscriber-rate-limitingflag to allow enabling subscriber-based rate limiting (off by default now, #649/#655, thanks to @barathrm for reporting, and to @karmanyaahm and @p1gp1g for help with the design)visitor-subscriber-rate-limitingis enabled (#643, thanks to @karmanyaahm and @p1gp1g for help with the design)Additional languages:
v2.1.1Compare Source
This is a tiny release with a few bug fixes, but it's big for me personally. After almost three months of work,
today I am finally launching the paid plans on ntfy.sh 🥳 🎉.
You are now able to purchase one of three plans that'll give you higher rate limits (messages, emails, attachment sizes, ...),
as well as the ability to reserve topic names for your personal use, while at the same time supporting me and the
ntfy open source project ❤️. You can check out the pricing, and purchase plans through the web app (use
promo code
MYTOPICfor a 50% discount, limited time only).And as I've said many times: Do not worry. ntfy will always stay open source, and that includes all features. There
are no closed-source features. So if you'd like to run your own server, you can!
Bug fixes + maintenance:
Dockerfileand document it (#635, thanks to @Andersbiha)log-level-overrideson the same field (no ticket)ntfy publish --env-topicflag (as per deprecations, no ticket)billing-contactconfig option (no ticket)v2.1.0Compare Source
This release changes the way UnifiedPush (UP) topics are rate limited from publisher-based rate limiting to subscriber-based rate limiting. This allows UP application servers to send higher volumes, since the subscribers carry the rate limits. However, it also means that UP clients have to subscribe to a topic first before they are allowed to publish. If they do no, clients will receive an HTTP 507 response from the server.
We also fixed another issue with UnifiedPush: Some Mastodon servers were sending unsupported
Authorizationheaders, which ntfy rejected with an HTTP 401. We now ignore unsupported header values.As of this release, ntfy also supports sending emails to protected topics, and it ships code to support annual billing cycles (not live yet).
As part of this release, I also enabled sign-up and login (free accounts only), and I also started reducing the rate limits for anonymous & free users a bit. With the next release and the launch of the paid plan, I'll reduce the limits a bit more. For 90% of users, you should not feel the difference.
Features:
up*topics (#584/#609/#633, thanks to @karmanyaahm)Bug fixes + maintenance:
Authorizationheader like header was not sent (#629, thanks to @Boebbele and @S1m for reporting)Documentation:
Additional languages:
v2.0.1Compare Source
This is a quick bugfix release to address a panic that happens when
attachment-cache-diris not set.Bug fixes + maintenance:
attachment-cache-diris not set (#617, thanks to @ksurl)log.Printlnalso output JSON (no ticket)v2.0.0Compare Source
This is the biggest ntfy server release I've ever done 🥳 . Lots of new and exciting features.
Brand-new features:
enable-signupandenable-login.ntfy.sh/philbackupsand define access so that only you can publish/subscribe to the topic. Reservations let you claim ownership of a topic, and you can define access permissions for others asdeny-all(only you have full access),read-only(you can publish/subscribe, others can subscribe),write-only(you can publish/subscribe, others can publish),read-write(everyone can publish/subscribe, but you remain the owner). Topic reservations can be configured in the web app ifenable-reservationsis enabled, and only if the user has a tier that supports reservations.ntfy tokencommand. See creating tokens, and publishing using tokens.jq. On top of that, you can override the log level if certain fields match. For instance, you can sayuser_name=phil -> debugto log everything related to a certain user with debug level. See logging & debugging.Standardthat allows 500 messages/day, 15 MB attachments and 5 allowed topic reservations, and another tierFriends & Familywith much higher limits. For ntfy.sh, I'll mostly use these tiers to facilitate paid plans (see below). Tiers can be configured via thentfy tier ...command. See tiers.ntfy is forever open source!
Yes, I will be offering some paid plans. But you don't need to panic! I won't be taking any features away, and everything will remain forever open source, so you can self-host if you like. Similar to the donations via GitHub Sponsors and Liberapay, paid plans will help pay for the service and keep me motivated to keep going. It'll only make ntfy better.
Special thanks:
A big Thank-you goes to everyone who tested the user account and payments work. I very much appreciate all the feedback,
suggestions, and bug reports. Thank you, @nwithan8, @deadcade, @xenrox, @cmeis, @wunter8, and the others who I forgot.
v1.31.0Compare Source
This is a tiny release before the really big release, and also the last before the big v2.0.0. The most interesting things in this release are the new preliminary health endpoint to allow monitoring in K8s (and others), and the removal of
upxbinary packing (which was causing erroneous virus flagging). Aside from that, thego-smtplibrary did a breaking-change upgrade, which required some work to get working again.Features:
/v1/healthAPI endpoint for service monitoring (no ticket)Dockerfile(#555, thanks to @bt90)Bug fixes + maintenance:
chownissues with RHEL-like based systems (#566/#565, thanks to @danieldemus)upx(binary packing) for all builds due to false virus warnings (#576, thanks to @shawnhwei for reporting)go-smtplibrary and tests to v0.16.0 (#569)Documentation:
client.yml(#562, thanks to @fleopaulD)Additional languages:
v1.30.1Compare Source
This is a special holiday edition version of ntfy, with all sorts of holiday fun and games, and hidden quests.
Nahh, just kidding. This release is an intermediate release mainly to eliminate warnings in the logs, so I can
roll out the TLSv1.3, HTTP/2 and Unix mode changes on ntfy.sh (see #552).
Features:
Bug fixes + maintenance:
--env-topicoption fromntfy publishas per deprecation (no ticket)v1.29.1Compare Source
This is mostly a bugfix release to address the high load on ntfy.sh. There are now two new options that allow
synchronous batch-writing of messages to the cache. This avoids database locking, and subsequent pileups of waiting
requests.
Bug fixes:
cache-batch-*options (#498/#502)Documentation:
Other things:
v1.29.0Compare Source
This release adds the ability to add rate limit exemptions for IP ranges instead of just specific IP addresses. It also fixes a few bugs in the web app and the CLI and adds lots of new examples and install instructions.
Thanks to some love on HN, we got so many new ntfy users trying out ntfy and joining the chat rooms. Welcome to the ntfy community to all of you! We also got a ton of new sponsors and donations 💸, which is amazing. I'd like to thank all of you for believing in the project, and for helping me pay the server cost. The HN spike increased the AWS cost quite a bit.
Features:
visitor-request-limit-exempt-hosts(#423, thanks to @karmanyaahm)Bug fixes + maintenance:
client.yml(#374, thanks to @cyqsimon for reporting, and @wunter8 for fixing)ntfy pubwill now use default username and password fromclient.yml(#431, thanks to @wunter8 for fixing)ntfy subwork withNTFY_USERenv variable (#447, thanks to @SuperSandro2000)Documentation:
?auth=..query parameter (#433, thanks to @wunter8)Additional translations:
Sponsorships::
Thank you to the amazing folks who decided to sponsor ntfy. Thank you for
helping carry the cost of the public server and developer licenses, and more importantly: Thank you for believing in ntfy!
You guys rock!
A list of all the sponsors can be found in the README.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
fe9458ba51to4201286d3fView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.