This is an automated email from the ASF dual-hosted git repository.
kranti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iggy-website.git
The following commit(s) were added to refs/heads/main by this push:
new bf7fd1d45 change discord url to https://discord.gg/apache-iggy
bf7fd1d45 is described below
commit bf7fd1d45ba4b9d3ec7fbd09097cb2ec29d5471c
Author: kparisa <[email protected]>
AuthorDate: Mon Sep 8 01:06:17 2025 -0700
change discord url to https://discord.gg/apache-iggy
---
blog/2023-11-26-release-0.1.0.md | 2 +-
blog/2023-12-29-building-message-streaming-in-rust.md | 2 +-
blog/2024-05-29-one-year-of-building-the-message-streaming.md | 6 +++---
blog/2024-10-28-technology-radar-and-currrent-goals.md | 4 ++--
blog/2025-02-10-apache-incubator.md | 2 +-
blog/2025-06-06-connectors-runtime.md | 2 +-
blog/2025-08-10-release-0.5.0.md | 2 +-
docs/sdk/rust/stream_builder.md | 6 +++---
docusaurus.config.ts | 4 ++--
9 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/blog/2023-11-26-release-0.1.0.md b/blog/2023-11-26-release-0.1.0.md
index 41784ba6f..646f9ac7a 100644
--- a/blog/2023-11-26-release-0.1.0.md
+++ b/blog/2023-11-26-release-0.1.0.md
@@ -43,4 +43,4 @@ While Rust **SDK** is the most mature one, and the C# is a
close second, the rem
Last but not least, we are **extremely grateful to the community**, which is
growing every day. We are getting more and more feedback, and we are doing our
best to address all the issues and feature requests. We are also getting more
and more contributions, which is a great sign that the project is going in the
right direction.
-Come and join our [Discord](https://discord.gg/C5Sux5NcRa) server, and let us
know what you think about the project. We are looking forward to hearing from
you!
\ No newline at end of file
+Come and join our [Discord](https://discord.gg/apache-iggy) server, and let us
know what you think about the project. We are looking forward to hearing from
you!
\ No newline at end of file
diff --git a/blog/2023-12-29-building-message-streaming-in-rust.md
b/blog/2023-12-29-building-message-streaming-in-rust.md
index bcd359c50..dc3abb884 100644
--- a/blog/2023-12-29-building-message-streaming-in-rust.md
+++ b/blog/2023-12-29-building-message-streaming-in-rust.md
@@ -147,7 +147,7 @@ Considering what's already there, being worked on or
planned for the future rele
**Why building another message streaming then?** A few months ago, I would
probably answer - strictly for fun. Yet, after exploring more in-depth the
status quo, what we would like to achieve is sort of twofold - on one hand,
it'd be great to deliver the general-purpose tool, such as Kafka. On the other
hand, why not to try and really push hard the OS and hardware to its limits
when speaking of the performance, reliability, throughput and latency,
something what e.g. Aeron does? And what [...]
-Only the time will tell, but **we're already excited enough to challenge
ourselves**. We'd love to hear your thoughts, ideas and **feedback** - anything
that will help us in building the best message streaming platform in Rust that
you will enjoy using! Feel free to join our
[Discord](https://discord.gg/C5Sux5NcRa) community and let us know what do you
think :)
+Only the time will tell, but **we're already excited enough to challenge
ourselves**. We'd love to hear your thoughts, ideas and **feedback** - anything
that will help us in building the best message streaming platform in Rust that
you will enjoy using! Feel free to join our
[Discord](https://discord.gg/apache-iggy) community and let us know what do you
think :)
P.S.
diff --git a/blog/2024-05-29-one-year-of-building-the-message-streaming.md
b/blog/2024-05-29-one-year-of-building-the-message-streaming.md
index e0d00ce1e..af15f69e7 100644
--- a/blog/2024-05-29-one-year-of-building-the-message-streaming.md
+++ b/blog/2024-05-29-one-year-of-building-the-message-streaming.md
@@ -16,7 +16,7 @@ date: 2024-05-29
<!--truncate-->
-This **particular article** turned out to be a sort of **catalyst**, as it
received a really nice traction on
[Reddit](https://www.reddit.com/r/rust/comments/18tgubd/iggyrs_building_message_streaming_in_rust/),
and was also mentioned on the main site of [Hacker
News](https://news.ycombinator.com/item?id=38868115), which I do believe were
the two main reasons for the growing interest & community since then. At this
point, I'd like to **thank you all very much** for such a kind feedback — [...]
+This **particular article** turned out to be a sort of **catalyst**, as it
received a really nice traction on
[Reddit](https://www.reddit.com/r/rust/comments/18tgubd/iggyrs_building_message_streaming_in_rust/),
and was also mentioned on the main site of [Hacker
News](https://news.ycombinator.com/item?id=38868115), which I do believe were
the two main reasons for the growing interest & community since then. At this
point, I'd like to **thank you all very much** for such a kind feedback — [...]
And although it may seem as if the project development has recently slowed
down a bit, I'd say it's quite the opposite — let me quickly summary, what
we've achieved so far during the last few months and what we're focusing on
now, as the future looks bright :)
@@ -24,7 +24,7 @@ And although it may seem as if the project development has
recently slowed down
## Community
-First and foremost, if it weren't for the community, we wouldn't have seen
such an enormous growth of the Iggy's ecosystem — we've received the dozens of
pull requests and there's ~250 members on our
[Discord](https://discord.gg/C5Sux5NcRa). Whether we talk about bug fixes,
improvements, new features, or just sharing the experiences and discussing
potential ideas — it's all equally important.
+First and foremost, if it weren't for the community, we wouldn't have seen
such an enormous growth of the Iggy's ecosystem — we've received the dozens of
pull requests and there's ~250 members on our
[Discord](https://discord.gg/apache-iggy). Whether we talk about bug fixes,
improvements, new features, or just sharing the experiences and discussing
potential ideas — it's all equally important.
And it's been even more than that — we've seen our community members take on
**building the new SDKs** in their favorite programming languages, fully on
their own. Today, you can find the following list of supported SDKs for Iggy.rs
— some of them could be lagging behind, but it's expected, as the project is
still evolving, and it's not an easy task, to come up with a great development
experience from the very beginning.
@@ -126,7 +126,7 @@ As mentioned before, **some of our users already experiment
with Iggy** — and
We can't guarantee that it will always be like this, but at least for now, we
do not see anything that would dramatically impact the existing solution. One
of such things could be the **redesigned storage, I/O, and clustering feature**
(as described in the previous paragraph), but even then, we'll do our best to
make it as seamless upgrade as possible — and once we achieve that, it means,
we're getting very close to the version 1.0.
-For the time being, if you're fine with a **single-node solution that delivers
a really good message streaming performance**, give Iggy a try, or at least run
the benchmarks to see what are its possibilities and please share your results
and thoughts on our [Discord](https://discord.gg/C5Sux5NcRa) — **your opinion
is really important to us and we respect it no matter what**.
+For the time being, if you're fine with a **single-node solution that delivers
a really good message streaming performance**, give Iggy a try, or at least run
the benchmarks to see what are its possibilities and please share your results
and thoughts on our [Discord](https://discord.gg/apache-iggy) — **your opinion
is really important to us and we respect it no matter what**.
It's been a very productive year for our core team (we've been and still are
doing this in our free time), and once again, huge thanks to all our supporters
and contributors!
diff --git a/blog/2024-10-28-technology-radar-and-currrent-goals.md
b/blog/2024-10-28-technology-radar-and-currrent-goals.md
index 13353975a..647b439a4 100644
--- a/blog/2024-10-28-technology-radar-and-currrent-goals.md
+++ b/blog/2024-10-28-technology-radar-and-currrent-goals.md
@@ -23,7 +23,7 @@ As you can see, we were put right into the **assess** bucket
(next to such renow
Besides gaining an additional amount of trust & recognition, it has led us to
another conclusion - someone out there we don't know yet about (maybe even one
of their customers) is using/experimenting with Iggy :)
-And if you are (or will be) one of such persons, please hop onto our
[Discord](https://discord.gg/C5Sux5NcRa) and share your invaluable feedback
with us!
+And if you are (or will be) one of such persons, please hop onto our
[Discord](https://discord.gg/apache-iggy) and share your invaluable feedback
with us!
Now, given the recent publication and increased activity within our [OSS
community](https://github.com/iggy-rs/) building the core streaming server &
SDKs in multiple programming languages, it's worth mentioning what are the
current goals for Iggy.
@@ -118,7 +118,7 @@ transport = "grpc"
endpoint = "http://localhost:7281/v1/traces";
```
-**And just like with S3 storage, it's merely a beginning** - one of the
members on our [Discord](https://discord.gg/C5Sux5NcRa) had already thought of
extending this implementation by **propagating the trace context** (via
existing message headers metadata) between the clients & server in order to get
full understanding of the distributed systems and its dependencies, which could
be further visualized by tools like [Zipkin](https://zipkin.io/) or
[Jaeger](https://www.jaegertracing.io/).
+**And just like with S3 storage, it's merely a beginning** - one of the
members on our [Discord](https://discord.gg/apache-iggy) had already thought of
extending this implementation by **propagating the trace context** (via
existing message headers metadata) between the clients & server in order to get
full understanding of the distributed systems and its dependencies, which could
be further visualized by tools like [Zipkin](https://zipkin.io/) or
[Jaeger](https://www.jaegertracing.io/).
### Optimizations
diff --git a/blog/2025-02-10-apache-incubator.md
b/blog/2025-02-10-apache-incubator.md
index e47490054..8699c4799 100644
--- a/blog/2025-02-10-apache-incubator.md
+++ b/blog/2025-02-10-apache-incubator.md
@@ -66,7 +66,7 @@ And this is just the beginning. **Welcome to the era of
Hyper-Efficient Message
👉 Follow us, contribute, and help to build the future of the message streaming!
-- [Discord](https://discord.gg/C5Sux5NcRa)
+- [Discord](https://discord.gg/apache-iggy)
- [X (Twitter)](https://x.com/ApacheIggy)
- [Bluesky](https://bsky.app/profile/iggy.rs)
- [LinkedIn](https://www.linkedin.com/company/apache-iggy/)
diff --git a/blog/2025-06-06-connectors-runtime.md
b/blog/2025-06-06-connectors-runtime.md
index 864a4af82..273e9e339 100644
--- a/blog/2025-06-06-connectors-runtime.md
+++ b/blog/2025-06-06-connectors-runtime.md
@@ -110,4 +110,4 @@ It's also worth mentioning that the runtime uses one of the
existing network pro
Finally, we would love to hear your feedback and suggestions on how to improve
the runtime and connectors. Please feel free to open an
**[issue](https://github.com/apache/iggy/issues)**, **[pull
request](https://github.com/apache/iggy/pulls)** or start a
**[discussion](https://github.com/apache/iggy/discussions)**.
-As always, you are more than welcome to join our **[Discord
community](https://discord.gg/C5Sux5NcRa)**!
+As always, you are more than welcome to join our **[Discord
community](https://discord.gg/apache-iggy)**!
diff --git a/blog/2025-08-10-release-0.5.0.md b/blog/2025-08-10-release-0.5.0.md
index ca7500d89..5553d5923 100644
--- a/blog/2025-08-10-release-0.5.0.md
+++ b/blog/2025-08-10-release-0.5.0.md
@@ -109,4 +109,4 @@ Other upcoming efforts:
Thanks to our amazing community and contributors for making Apache Iggy better
with every release.
-**Join us on [Discord](https://discord.gg/C5Sux5NcRa) and help shape the
future of the project!**
+**Join us on [Discord](https://discord.gg/apache-iggy) and help shape the
future of the project!**
diff --git a/docs/sdk/rust/stream_builder.md b/docs/sdk/rust/stream_builder.md
index dd2179e07..9a24ec1ca 100644
--- a/docs/sdk/rust/stream_builder.md
+++ b/docs/sdk/rust/stream_builder.md
@@ -17,7 +17,7 @@ you typically encounter one or more of the following
scenarios:
The stream builder provides a convenient way to create the iggy client,
producer and consumer for these use cases.
All source code examples are located in the [**examples
folder**](https://github.com/apache/iggy/tree/master/core/examples/src/stream-builder)
of the iggy repository. Also,
-if you encounter a problem with any of the examples below, please ask in the
[**community discord**](https://discord.gg/C5Sux5NcRa).
+if you encounter a problem with any of the examples below, please ask in the
[**community discord**](https://discord.gg/apache-iggy).
## IggyStream Builder
@@ -283,7 +283,7 @@ The default configuration only exists to get you started
quickly i.e. to test ou
similar. In practice, you often want fine grained control over the
configuration. The IggyConsumerConfig gives you a way
to configure the consumer in sufficient detail without distracting with low
level details.
Please note, if you have questions about any of those settings, please ask in
-the [community discord](https://discord.gg/C5Sux5NcRa). See below a commented
configuration example:
+the [community discord](https://discord.gg/apache-iggy). See below a commented
configuration example:
```rust
use iggy::clients::consumer::{AutoCommit, AutoCommitWhen};
@@ -405,4 +405,4 @@ a new configuration from just the stream, topic, batch size
and send interval. S
```
If you encounter a problem with any of the examples show on this page,
-please ask in the [**community discord**](https://discord.gg/C5Sux5NcRa).
+please ask in the [**community discord**](https://discord.gg/apache-iggy).
diff --git a/docusaurus.config.ts b/docusaurus.config.ts
index c5c92c776..908e96bd0 100644
--- a/docusaurus.config.ts
+++ b/docusaurus.config.ts
@@ -100,7 +100,7 @@ const config: Config = {
position: "left",
},
{
- href: "https://discord.gg/dnJQd3cHCC";,
+ href: "https://discord.gg/apache-iggy";,
label: "Discord",
position: "left",
},
@@ -163,7 +163,7 @@ const config: Config = {
},
{
label: "Discord",
- href: "https://discord.gg/dnJQd3cHCC";,
+ href: "https://discord.gg/apache-iggy";,
},
{
label: "X",
