deploy: 3f12d74

blog/index.xml

@@ -42,7 +42,7 @@ CNCF landscape</a
 <p>This approach has the benefit that each app gets a dedicated namespace. Within that namespace, the app can do whatever it wants, without interfering with other apps. At app installation time, a check is done whether the domain path being requested is available. If some other app is using that path, the new app installation is rejected. A SQLite database is used to <a href="https://clace.io/blog/sqlite/" >store app metadata</a>, so API driven app updates do not conflict with each other.</p>
 <p>Within the app, rules are defined using <a href="https://starlark-lang.org/" target="_blank" rel="noopener">Starlark</a>. This avoids the need to learn a new DSL. The <a href="https://clace.io/docs/app/routing/" >routing</a> config is read at app initialization only and the actual <a href="https://clace.io/docs/app/overview/#sample-starlark-app" >handler</a> logic can be expressed alongside the routing rules. For <a href="https://clace.io/docs/container/overview/" >containerized apps</a>, the routing rule specifies the revery proxy url. Reloading an app updates its config, without impacting other apps.</p>
 <h2>Conclusion<span class="hx-absolute -hx-mt-20" id="conclusion"></span>
-&lt;a href="#conclusion" class="subheading-anchor" aria-label="Permalink for this section">&lt;/a>&lt;/h2>&lt;p>By enforcing app-level isolation in routing rules, Clace allows each app to manage its own domain and path namespace without risking conflicts or breakages. This approach encourages developers to utilize efficient web server–level routing features, confident that changes in one app won’t disrupt others. No all webserver routing use case can use this approach, but this is useful for app deployment use cases.&lt;/p></description></item><item><title>Go Composition does not compose well with Implicit Interfaces</title><link>https://clace.io/blog/go-composition/</link><pubDate>Tue, 24 Dec 2024 00:00:00 +0000</pubDate><guid>https://clace.io/blog/go-composition/</guid><description>
+&lt;a href="#conclusion" class="subheading-anchor" aria-label="Permalink for this section">&lt;/a>&lt;/h2>&lt;p>By enforcing app-level isolation in routing rules, Clace allows each app to manage its own domain and path namespace without risking conflicts or breakages. This approach encourages developers to utilize efficient web server–level routing features, confident that changes in one app won’t disrupt others. Some webserver routing use cases which are more complex cannot use this approach, but this is useful for app deployment scenarios.&lt;/p></description></item><item><title>Go Composition does not compose well with Implicit Interfaces</title><link>https://clace.io/blog/go-composition/</link><pubDate>Tue, 24 Dec 2024 00:00:00 +0000</pubDate><guid>https://clace.io/blog/go-composition/</guid><description>
 &lt;div
 class="hx-overflow-x-auto hx-mt-6 hx-flex hx-rounded-lg hx-border hx-py-2 ltr:hx-pr-4 rtl:hx-pl-4 contrast-more:hx-border-current contrast-more:dark:hx-border-current hx-border-blue-200 hx-bg-blue-100 hx-text-blue-900 dark:hx-border-blue-200/30 dark:hx-bg-blue-900/30 dark:hx-text-blue-200">
 &lt;div class="ltr:hx-pl-3 ltr:hx-pr-2 rtl:hx-pr-3 rtl:hx-pl-2">