diff --git a/concepts/llm_provider.html b/concepts/llm_provider.html index 632e1c03..60cd7259 100755 --- a/concepts/llm_provider.html +++ b/concepts/llm_provider.html @@ -166,7 +166,7 @@ across applications.
Below is an example of how you can configure llm_providers with an instance of an Arch gateway.
1version: v0.1
+ 1version: v0.1.0
2
3listeners:
4 ingress_traffic:
diff --git a/concepts/tech_overview/listener.html b/concepts/tech_overview/listener.html
index 4292aeb6..22dae083 100755
--- a/concepts/tech_overview/listener.html
+++ b/concepts/tech_overview/listener.html
@@ -183,7 +183,7 @@ address like arch.l
To configure a Downstream (Ingress) Listener, simply add the listener directive to your configuration file:
- 1version: v0.1
+ 1version: v0.1.0
2
3listeners:
4 ingress_traffic:
diff --git a/concepts/tech_overview/prompt.html b/concepts/tech_overview/prompt.html
index 47162625..4d6e46e1 100755
--- a/concepts/tech_overview/prompt.html
+++ b/concepts/tech_overview/prompt.html
@@ -187,7 +187,7 @@ ensuring that unauthorized or harmful behaviors are intercepted early in the pro
To add jailbreak guardrails, see example below:
- 1version: v0.1
+ 1version: v0.1.0
2
3listeners:
4 ingress_traffic:
@@ -231,7 +231,7 @@ when a user’s intent has changed so that you can build faster, more accurate R
Configuring prompt_targets is simple. See example below:
- 1version: v0.1
+ 1version: v0.1.0
2
3listeners:
4 ingress_traffic:
diff --git a/concepts/tech_overview/request_lifecycle.html b/concepts/tech_overview/request_lifecycle.html
index dea949fb..abfcfbcf 100755
--- a/concepts/tech_overview/request_lifecycle.html
+++ b/concepts/tech_overview/request_lifecycle.html
@@ -218,7 +218,7 @@ enables scaling to very high core count CPUs.
Configuration
Today, only support a static bootstrap configuration file for simplicity today:
-version: v0.1
+version: v0.1.0
listeners:
ingress_traffic:
diff --git a/get_started/quickstart.html b/get_started/quickstart.html
index 7fd5367b..7ef1fddf 100755
--- a/get_started/quickstart.html
+++ b/get_started/quickstart.html
@@ -183,7 +183,7 @@
Step 1. Create arch config file
Create arch_config.yaml file with the following content:
- version: v0.1
+ version: v0.1.0
listeners:
ingress_traffic:
@@ -275,7 +275,7 @@
Step 1. Create arch config file
Arch operates based on a configuration file where you can define LLM providers, prompt targets, guardrails, etc. Below is an example configuration that defines OpenAI and Mistral LLM providers.
Create arch_config.yaml file with the following content:
- version: v0.1
+ version: v0.1.0
listeners:
egress_traffic: