<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tutorials on Open Component Model</title><link>https://ocm.software/main/docs/tutorials/</link><description>Recent content in Tutorials on Open Component Model</description><generator>Hugo</generator><language>en-US</language><atom:link href="https://ocm.software/main/docs/tutorials/index.xml" rel="self" type="application/rss+xml"/><item><title>Create a Multi-Component Product</title><link>https://ocm.software/main/docs/tutorials/create-a-multi-component-product/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ocm.software/main/docs/tutorials/create-a-multi-component-product/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Real-world software products rarely consist of a single component. A web platform, for example, might combine a frontend, a backend, shared configuration, and deployment manifests — each versioned independently. The OCM component constructor lets you model this entire hierarchy in a single file, wiring components together with references, attaching provenance metadata, and injecting versions through environment variables.&lt;/p&gt;</description></item><item><title>Understand Credential Resolution</title><link>https://ocm.software/main/docs/tutorials/understand-credential-resolution/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ocm.software/main/docs/tutorials/understand-credential-resolution/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Every time OCM accesses a registry, it resolves credentials automatically. This tutorial walks you through how that resolution works — given a config, which credentials does OCM pick for each request, and why?&lt;/p&gt;</description></item><item><title>Deploy Helm Charts with Bootstrap Setup</title><link>https://ocm.software/main/docs/tutorials/deploy-helm-charts-with-bootstrap-setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ocm.software/main/docs/tutorials/deploy-helm-charts-with-bootstrap-setup/</guid><description>&lt;h2 id="what-youll-learn"&gt;What You&amp;rsquo;ll Learn&lt;/h2&gt;
&lt;p&gt;In this tutorial, you&amp;rsquo;ll learn how to package deployment instructions (a &lt;code&gt;ResourceGraphDefinition&lt;/code&gt;) inside an OCM
component, so operators can deploy your Helm chart without knowing the underlying resource structure. You&amp;rsquo;ll also learn
&lt;strong&gt;localization&lt;/strong&gt;—how to automatically update image references in the
deployment instructions when transferring components between registries.&lt;/p&gt;</description></item><item><title>Working with Resolvers</title><link>https://ocm.software/main/docs/tutorials/working-with-resolvers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ocm.software/main/docs/tutorials/working-with-resolvers/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;When a component has &lt;strong&gt;references&lt;/strong&gt; to other components stored in different repositories, the CLI needs to know where to
find them. &lt;strong&gt;Resolvers&lt;/strong&gt; map component name patterns to repositories so the CLI can automatically locate referenced
components during recursive operations. For a high-level introduction, see the 





 
 


&lt;a href="https://ocm.software/main/docs/concepts/resolvers/"&gt;Resolvers concept page&lt;/a&gt;.
For configuration details and pattern syntax, see the 





 
 


&lt;a href="https://ocm.software/main/docs/reference/resolver-configuration/"&gt;Resolver Configuration Reference&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>