<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Working with Porch Repositories on Porch Documentation</title><link>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/</link><description>Recent content in Working with Porch Repositories on Porch Documentation</description><generator>Hugo</generator><language>en-us</language><atom:link href="/docs/4_tutorials_and_how-tos/working_with_porch_repositories/index.xml" rel="self" type="application/rss+xml"/><item><title>Registering Repositories</title><link>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-registration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-registration/</guid><description>&lt;p>Registering a repository connects Porch to your Git storage backend, allowing it to discover and manage packages. You can register repositories with various authentication methods and configuration options.&lt;/p>
&lt;h3 id="register-a-git-repository">Register a Git Repository&lt;/h3>&lt;p>Register a Git repository with Porch:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">porchctl repo register https://github.com/example/porch-test.git &lt;span class="se">\
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="se">&lt;/span> --namespace default &lt;span class="se">\
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="se">&lt;/span> --name&lt;span class="o">=&lt;/span>porch-test &lt;span class="se">\
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="se">&lt;/span> --description&lt;span class="o">=&lt;/span>&lt;span class="s2">&amp;#34;Blueprint packages&amp;#34;&lt;/span> &lt;span class="se">\
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="se">&lt;/span> --branch&lt;span class="o">=&lt;/span>main
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This command registers the Git repository with Porch, creates a Repository resource in Kubernetes and begins synchronizing packages from the repository.&lt;/p></description></item><item><title>Repositories Basic Usage</title><link>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-basic-usage/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-basic-usage/</guid><description>&lt;h2 id="basic-operations">Basic Operations&lt;/h2>&lt;p>These operations cover the fundamental commands for viewing and managing registered repositories.&lt;/p>
&lt;h3 id="list-registered-repositories">List Registered Repositories&lt;/h3>&lt;p>View all repositories registered with Porch:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">porchctl repo get --namespace default
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This command queries Porch for all registered repositories in the specified namespace, displays the repository type, content type, sync schedule, and status and shows the repository address.&lt;/p>


&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note&lt;/h4>

 &lt;p>&lt;code>porchctl repo list&lt;/code> is an alias for &lt;code>porchctl repo get&lt;/code> and can be used interchangeably:&lt;/p></description></item><item><title>Synchronizing Repositories</title><link>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-synchronization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-synchronization/</guid><description>&lt;h2 id="repository-synchronization">Repository Synchronization&lt;/h2>&lt;p>Porch periodically synchronizes with registered repositories to discover new packages and updates. You can also trigger manual synchronization when you need immediate updates.&lt;/p>


&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note&lt;/h4>

 &lt;strong>Sync Schedule Format:&lt;/strong> Cron expressions follow the format &lt;code>minute hour day month weekday&lt;/code>. For example, &lt;code>*/10 * * * *&lt;/code> means &amp;ldquo;every 10 minutes&amp;rdquo;.

&lt;/div>

&lt;h3 id="trigger-manual-sync">Trigger Manual Sync&lt;/h3>&lt;p>Force an immediate synchronization of a repository:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">porchctl repo sync porch-test --namespace default
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This command schedules a one-time sync (minimum 1-minute delay), updates packages from the repository. This sync is independent of the periodic sync schedule.&lt;/p></description></item><item><title>Unregistering Repositories</title><link>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-unregistration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/4_tutorials_and_how-tos/working_with_porch_repositories/repository-unregistration/</guid><description>&lt;h2 id="unregistering-repositories">Unregistering Repositories&lt;/h2>&lt;p>When you no longer need Porch to manage packages from a repository, you can unregister it. This removes Porch&amp;rsquo;s connection to the repository without affecting the underlying Git storage.&lt;/p>
&lt;h3 id="unregister-a-repository">Unregister a Repository&lt;/h3>&lt;p>Remove a repository from Porch:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">porchctl repo unregister porch-test --namespace default
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>This command removes the Repository resource from Kubernetes, it stops synchronizing packages from the repository, removes Porch&amp;rsquo;s cached metadata for the repository but &lt;strong>does not delete&lt;/strong> the underlying Git repository or its contents.&lt;/p></description></item></channel></rss>