Skip to main content

Legacy SVN Repository Configuration

<p><strong>Last reviewed:</strong> September 24, 2026</p>

<p>This article is retained as a legacy reference for teams that still maintain SVN-backed AIQ assets.</p>

<h2>

<ul><li>

  • Use Git-based repository workflows where available for current AIQ projects.</li><li>
  • Keep SVN access limited to environments that still depend on historical repositories.</li><li>
  • Store repository credentials securely and rotate them according to your organization policy.</li></ul>

<h2>

Validation workflow</h2>

<ol><li>

  1. Verify that the project still requires SVN before configuring it.</li><li>
  2. Create or validate the repository path and user permissions outside AIQ.</li><li>
  3. Connect the repository from AIQ and run a small save or sync test.</li></ol>

<div class="callout warning"><p><strong>Note:</strong> SVN is legacy guidance. Do not use it as the default repository recommendation for new AIQ implementations.</p></div>

<hr>

<p>Last updated: September 24, 2026</p>

<p>If you have feedback on this topic, contact <a href="mailto:documentation@appvance.ai">documentation@appvance.ai</a>.</p>

Back to top