Merge branch 'dev' into issue-#23616

Author: MansurBesleney

abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json

@@ -228,7 +228,9 @@
     "Articles": "Articles",
     "Organizations": "Organizations",
     "ManageAccount": "Manage Account",
+    "MyManageAccount": "My Account",
     "CommunityProfile": "Community Profile",
+    "MyCommunityProfile": "My Community Profile",
     "BlogProfile": "Blog Profile",
     "Tickets": "Tickets",
     "Raffles": "Raffles",
@@ -248,13 +250,25 @@
     "NewsletterDefinition": "Blog posts, community news, etc.",
     "OrganizationOverview": "Organization Overview",
     "EmailPreferences": "Email Preferences",
+    "MyEmailPreferences": "My Email Preferences",
     "VideoCourses": "Essential Videos",
     "DoYouAgreePrivacyPolicy": "By clicking <b>Subscribe</b> button you agree to the <a href=\"/terms-conditions\">Terms & Conditions</a> and <a href=\"/privacy\">Privacy Policy</a>.",
     "AbpConferenceDescription": "ABP Conference is a virtual event for .NET developers to learn and connect with the community.",
     "Mobile": "Mobile",
     "MetaTwitterCard": "summary_large_image",
     "IPAddress": "IP Address",
+    "MyReferrals": "My Referrals",
     "LicenseBanner:InfoText": "Your license will <b>expire in {0} days.</b>",
-    "LicenseBanner:CallToAction": "Please <a href=\"/my-organizations/{0}\" class=\"text-decoration-underline\">extend your license.</a>"
+    "LicenseBanner:CallToAction": "Please <a href=\"/my-organizations/{0}\" class=\"text-decoration-underline\">extend your license.</a>",
+    "Referral.CreatorUserIdIsRequired": "Creator user ID is required.",
+    "Referral.TargetEmailIsRequired": "Target email is required.",
+    "Referral.TargetEmailAlreadyExists": "A referral link for this email address already exists.",
+    "Referral.MaxLinkLimitExceeded": "You have reached the maximum limit of {Limit} active referral links.",
+    "Referral.LinkNotFound": "Referral link not found.",
+    "Referral.LinkNotFoundOrNotOwned": "Referral link not found or you don't have permission to access it.",
+    "Referral.CannotDeleteUsedLink": "You cannot delete a referral link that has already been used.",
+    "LinkCopiedToClipboard": "Link copied to clipboard",
+    "AreYouSureToDeleteReferralLink": "Are you sure you want to delete this referral link?",
+    "DefaultErrorMessage": "An error occurred."
   }
 }

docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/POST.md

@@ -0,0 +1,88 @@
+# 5 Things You Should Keep in Mind When Deploying to a Clustered Environment
+
+Let’s be honest — moving from a single server to a cluster sounds simple on paper.  
+You just add a few more machines, right?  
+In practice, it’s the moment when small architectural mistakes start to grow legs.  
+Below are a few things that experienced engineers usually double-check before pressing that “Deploy” button.
+
+---
+
+## 1️⃣ Managing State the Right Way
+
+Each request in a cluster might hit a different machine.  
+If your application keeps user sessions or cache in memory, that data probably won’t exist on the next node.  
+That’s why many teams decide to push state out of the app itself.
+
+![Stateless vs Stateful](stateless.png)
+
+**A few real-world tips:**
+- Keep sessions in **Redis** or something similar instead of local memory.  
+- Design endpoints so they don’t rely on earlier requests.  
+- Don’t assume the same server will handle two requests in a row — it rarely does.
+
+---
+
+## 2️⃣ Shared Files and Where to Put Them
+
+Uploading files to local disk? That’s going to hurt in a cluster.  
+Other nodes can’t reach those files, and you’ll spend hours wondering why images disappear.
+
+![Shared Storage](shared.png)
+
+**Better habits:**
+- Push uploads to **S3**, **Azure Blob**, or **Google Cloud Storage**.  
+- Send logs to a shared location instead of writing to local files.  
+- Keep environment configs in a central place so each node starts with the same settings.
+
+---
+
+## 3️⃣ Database Connections Aren’t Free
+
+Every node opens its own database connections.  
+Ten nodes with twenty connections each — that’s already two hundred open sessions.  
+The database might not love that.
+
+![Database Connections](database.png)
+
+**What helps:**
+- Put a cap on your connection pools.  
+- Avoid keeping transactions open for too long.  
+- Tune indexes and queries before scaling horizontally.
+
+---
+
+## 4️⃣ Logging and Observability Matter More Than You Think
+
+When something breaks in a distributed system, it’s never obvious which server was responsible.  
+That’s why observability isn’t optional anymore.
+
+![Observability](logging.png)
+
+**Consider this:**
+- Stream logs to **ELK**, **Datadog**, or **Grafana Loki**.  
+- Add a **trace ID** to every incoming request and propagate it across services.  
+- Watch key metrics with **Prometheus** and visualize them in Grafana dashboards.
+
+---
+
+## 5️⃣ Background Jobs and Message Queues
+
+If more than one node runs the same job, you might process the same data twice — or delete something by mistake.  
+You don’t want that kind of excitement in production.
+
+![Background Jobs](background.png)
+
+**A few precautions:**
+- Use a **distributed lock** or **leader election** system.  
+- Make jobs **idempotent**, so running them twice doesn’t break data.  
+- Centralize queue consumers or use a proper task scheduler.
+
+---
+
+## Wrapping Up
+
+Deploying to a cluster isn’t only about scaling up — it’s about staying stable when you do.  
+Systems that handle state, logging, and background work correctly tend to age gracefully.  
+Everything else eventually learns the hard way.
+
+> A cluster doesn’t fix design flaws — it magnifies them.

docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/all.png

@@ -0,0 +1,27 @@
+# 5 Things You Should Keep in Mind When Deploying to a Clustered Environment
+
+Let’s be honest — moving from a single server to a cluster sounds simple on paper.  
+You just add a few more machines, right?  
+In practice, it’s the moment when small architectural mistakes start to grow legs.  
+Below are a few things that experienced engineers usually double-check before pressing that “Deploy” button.
+
+---
+
+## 1️⃣ Managing State the Right Way
+---
+
+## 2️⃣ Shared Files and Where to Put Them
+---
+
+## 3️⃣ Database Connections Aren’t Free
+---
+
+## 4️⃣ Logging and Observability Matter More Than You Think
+---
+
+## 5️⃣ Background Jobs and Message Queues
+---
+
+![all](all.png)
+
+👉 Read the full guide here: [5 Things You Should Keep in Mind When Deploying to a Clustered Environment](https://abp.io/community/articles/)