Legacy SVN Repository Configuration

Last reviewed: September 24, 2026

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

Recommended guidance

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

Validation workflow

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

Note: SVN is legacy guidance. Do not use it as the default repository recommendation for new AIQ implementations.

Last updated: September 24, 2026

If you have feedback on this topic, contact documentation@appvance.ai.