update

Author: mythz

MyApp/_includes/admin-ui-claims-validation.md

@@ -25,8 +25,8 @@ It will generate that Error Response instead:
 <error-summary :status="{message:`'todos:write' Permission Required`}"></error-summary>
 :::
 
-Which is a good example showing how `HasClaimValidator.ClaimErrorMessages` can be used to add custom error messages
-for your own custom claim validation. 
+This is a good example for how to use `HasClaimValidator.ClaimErrorMessages` to add custom error messages
+for your own custom claim validations.
 
 ### Inspecting Claims inside Services
 

MyApp/_pages/admin-ui-analytics.md

@@ -2,7 +2,7 @@
 title: Admin UI Analytics
 ---
 
-Comprehensive API Analytics is available to all ServiceStack Apps configured with [SQLite Request Logging[(/sqlite-request-logs).
+Comprehensive API Analytics is available to all ServiceStack Apps configured with [SQLite Request Logging](/sqlite-request-logs).
 
 ### Benefits of API Analytics
 
@@ -15,21 +15,19 @@ IPs where most traffic generates:
 - **Troubleshooting:** Aids in quickly identifying trends, anomalies, or specific endpoints related to issues.
 - **Resource Planning:** Understanding usage patterns helps in scaling infrastructure appropriately.
 - **Security Insight:** Identifying bot traffic and unusual request patterns can be an early indicator of security concerns.
+- **Interactive Analytics:** Analytics are also interactive where you're able to drill down to monitor the activity of individual APIs, Users, API Keys and IPs with links back to the request logs which the summary analytics are derived from.
 
-### Interactive Analytics
+### Getting Started
 
-Analytics are also interactive where you're able to drill down to monitor the activity of individual APIs, Users, API Keys 
-and IPs which have further links back to the request logs which the summary analytics are derived from.
-
-As they offer significant and valuable insights they're now built into all ASP.NET Core IdentityAuth templates, 
+As they offer significant and valuable insights they're now built into all new ASP.NET Core IdentityAuth templates, 
 existing .NET 8 IdentityAuth templates can enable it with: 
 
 :::sh
 x mix sqlitelogs
 :::
 
-.NET 8 Templates that are not configured to use [Endpoint Routing[(/endpoint-routing)
-and [ASP.NET Core IOC[(/net-ioc) will need to explicitly register `SqliteRequestLogger`
+.NET 8 Templates that are not configured to use [Endpoint Routing](/endpoint-routing)
+and [ASP.NET Core IOC](/net-ioc) will need to explicitly register `SqliteRequestLogger`
 as a singleton dependency in addition to configuring it on the `RequestLogsFeature` plugin:
 
 ```csharp
@@ -56,18 +54,24 @@ public class ConfigureRequestLogs : IHostingStartup
 }
 ```
 
-This will enable a more feature rich Request Logging Admin UI which utilizes the full queryability of an AutoQueryGrid
-to filter, sort and export Request Logs. 
+## Analytics Admin UI
+
+Once configured, [SQLite Request Logs](/sqlite-request-logs) enable a more feature rich Request Logging Admin UI which utilizes the full queryability of an AutoQueryGrid to filter, sort and export Request Logs. 
 
 [![](/img/pages/admin-ui/sqlitelogs.webp)](/img/pages/admin-ui/sqlitelogs.webp)
 
+### Rolling Monthly Request Logs
+
+Benefits of using SQLite includes removing load from your App's primary database and being able to create naturally scalable and isolated Monthly databases on-the-fly which allow requests to be easily archived into managed file storage instead of a singular growing database.
+
 ## Analytics Overview
 
-Utilizing an `SqliteRequestLogger` will also enable the new **Analytics** Admin UI in the sidebar which initially
-displays the API Analytics Dashboard:
+It also enables the new **Analytics** Admin UI in the sidebar which initially displays the API Analytics overview Dashboard:
 
 [![](/img/pages/admin-ui/analytics-apis1.webp)](/img/pages/admin-ui/analytics-apis1.webp)
 
+Different charts displayed on the dashboard include:
+
 ### Distribution Pie Charts
 
 Lets you quickly understand the composition of your user base and traffic sources and the 
@@ -229,3 +233,78 @@ bar chart to view its individual analytics made from that IP Address.
 Provides comprehensive IP Address analytics Similar to User Analytics but limited to the API Usage from a single IP Address:
 
 [![](/img/pages/admin-ui/analytics-ip.webp)](/img/pages/admin-ui/analytics-ip.webp)
+
+## Blocking User Agents
+
+The insights from the Analytics showed us that our [pvq.app](https://pvq.app) was experiencing significant load from
+AI bots and scrapers which was the primary cause of its high resource usage and detrimental load times for normal
+user requests, so much so we've intervened to prevent these bots from scraping our site.
+
+### Disallowing Bots in robots.txt
+
+In an ideal world you would just need to instruct problematic bots not to scrape your site by adding them to [pvq.app/robots.txt](https://pvq.app/robots.txt), e.g:
+
+```txt
+User-agent: Googlebot
+Allow: /
+User-agent: Bingbot
+Allow: /
+
+User-agent: bytespider
+Disallow: /
+User-agent: gptbot
+Disallow: /
+User-agent: claudebot
+Disallow: /
+User-agent: amazonbot
+Disallow: /
+User-agent: mj12bot
+Disallow: /
+User-agent: semrushbot
+Disallow: /
+User-agent: dotbot
+Disallow: /
+User-agent: WhatsApp Bot
+Disallow: /
+User-agent: *
+Disallow: /
+```
+
+### Disallowing Bot Requests
+
+As this was not having an immediate effect we took a more forceful approach to implement a middleware to reject all
+requests from disallowed bots from accessing our App which you can add to your own App with:
+
+:::sh
+x mix useragent-blocking
+:::
+
+This will allow you to configure which Bot User Agents you want to reject from accessing your site, e.g:
+
+```csharp
+services.Configure<UserAgentBlockingOptions>(options =>
+{
+    // Add user agents to block
+    options.BlockedUserAgents.AddRange([
+        "bytespider",
+        "gptbot",
+        "gptbot",
+        "claudebot",
+        "amazonbot",
+        "imagesiftbot",
+        "semrushbot",
+        "dotbot",
+        "semrushbot",
+        "dataforseobot",
+        "WhatsApp Bot",
+        "HeadlessChrome",
+        "PetalBot",
+    ]);
+    
+    // Optional: Customize the response status code
+    // options.BlockedStatusCode = StatusCodes.Status429TooManyRequests;
+    
+    // Optional: Customize the blocked message
+    options.BlockedMessage = "This bot is not allowed to access our website";
+});
+```

MyApp/_pages/admin-ui-identity-roles.md

@@ -27,7 +27,7 @@ services.AddPlugin(
 
 ### IdentityAuth Role Claims
 
-The Edit Role Admin UI can also be configured to Add/Remove Claims to a Role, e.g:
+The Edit Role Admin UI also supports Adding and Remove Claims for a Role, e.g:
 
 ![](/img/pages/admin-ui/identityauth-role-claims.webp)
 

MyApp/_pages/ai-server/image-to-text.md

@@ -18,6 +18,14 @@ AI Server's Image to Text UI lets you request image classifications from its act
 
 ::include ai-server/endpoint-usage.md::
 
+### Ollama Vision Models
+
+If AI Server has access to any Ollama Vision Models (e.g. **gemma3:27b** or **mistral-small**), it can be used
+instead to get information about the uploaded image:
+
+ - `Model` - the ollama vision model to use
+ - `Prompt` - vision model prompt
+
 ### Image to Text {#image-to-text}
 
 ::include ai-server/cs/image-to-text-1.cs.md::
@@ -29,4 +37,52 @@ AI Server's Image to Text UI lets you request image classifications from its act
 :::info
 Ensure that the ComfyUI Agent has the Florence 2 model downloaded and installed for the Image-To-Text functionality to work.
 This can be done by setting the `DEFAULT_MODELS` environment variable in the `.env` file to include `image-to-text`
-:::
+:::
+
+## Support for Ollama Vision Models
+
+By default [ImageToText](/ai-server/image-to-text) uses a purpose-specific **Florence 2 Vision model** with ComfyUI for its functionality which is capable of generating a very short description about an image, e.g:
+
+> A woman sitting on the edge of a lake with a wolf
+
+But with LLMs gaining multi modal capabilities and Ollama's recent support of Vision Models we can instead use popular
+Open Source models like Google's **gemma3:27b** or Mistral's **mistral-small:24b** to extract information from images.
+
+Both models are very capable vision models that's can provide rich detail about an image:
+
+### Describe Image
+
+<div class="not-prose mt-8 grid grid-cols-2 gap-4">
+    <a class="block group border dark:border-gray-800 hover:border-indigo-700 dark:hover:border-indigo-700 flex flex-col justify-between" href="/img/pages/ai-server/image-to-text/gemma3-describe.png">
+        <img class="p-2" src="/img/pages/ai-server/image-to-text/gemma3-describe.png" />
+    </a>
+    <a class="block group border dark:border-gray-800 hover:border-indigo-700 dark:hover:border-indigo-700 flex flex-col justify-between" href="/img/pages/ai-server/image-to-text/mistral-small-describe.png">
+        <img class="p-2" src="/img/pages/ai-server/image-to-text/mistral-small-describe.png" />
+    </a>
+</div>
+
+### Caption Image
+
+Although our initial testing sees gemma being better at responding to a wide variety of different prompts, e.g:
+
+<div class="not-prose mt-8 grid grid-cols-2 gap-4">
+    <a class="block group border dark:border-gray-800 hover:border-indigo-700 dark:hover:border-indigo-700 flex flex-col justify-between" href="/img/pages/ai-server/image-to-text/gemma3-caption.png">
+        <img class="p-2" src="/img/pages/ai-server/image-to-text/gemma3-caption.png" />
+    </a>
+    <a class="block group border dark:border-gray-800 hover:border-indigo-700 dark:hover:border-indigo-700 flex flex-col justify-between" href="/img/pages/ai-server/image-to-text/mistral-small-caption.png">
+        <img class="p-2" src="/img/pages/ai-server/image-to-text/mistral-small-caption.png" />
+    </a>
+</div>
+
+## Support OllamaGenerate Endpoint
+
+To support Ollama's vision models AI Server added a new feature pipeline around
+[Ollama's generate completion API](https://github.com/ollama/ollama/blob/main/docs/api.md#generate-a-completion):
+
+
+- `ImageToText`
+  - **Model** - Whether to use a Vision Model for the request
+  - **Prompt** - Prompt for the vision model
+- `OllamaGeneration`: Synchronous invocation of Ollama's Generate API
+- `QueueOllamaGeneration`: Asynchronous or Web Callback invocation of Ollama's Generate API
+- `GetOllamaGenerationStatus`: Get the generation status of an Ollama Generate API

MyApp/_pages/templates/angular.md

@@ -31,7 +31,7 @@ The default Angular SPA Template can be downloaded below:
     </project-template>
 </project-creator>
 
-Alternatively you can download a custom template from the [Start Page](/start).
+Alternatively you can download a custom template from the [Start Page](https://servicestack.net/start).
 
 The source code for the template is maintained at [NetCoreTemplates/angular-spa](https://github.com/NetCoreTemplates/angular-spa)
 whilst an online live-demo is available from: [angular-spa.web-templates.io](https://angular-spa.web-templates.io)
@@ -254,8 +254,7 @@ export class BookingListComponent implements OnInit {
 }
 ```
 
-Using `provideApiState()` implicitly injects the populated API context containing both the APIs Loading and Error into
-child components saving you from explicitly specifying it in each component.
+Using `provideApiState()` implicitly injects the populated API context containing both the APIs Loading and Error state into child components saving you from having to explicitly inject it into each component.
 
 E.g. the `<form-loading>` component will display when API Requests are in-flight whilst API Error Responses are displayed
 after receiving failed API Responses: