Coming soon. Depotex is in active development, so features and these docs may still change.

Frequently asked questions

Answers to the questions administrators ask most

1. Licensing

  • How do I get a license? Read the installation ID (setup wizard, Settings → Application → Licensing, or ./server --machine-id) and send it through vectored.dev/#contact or to support@vectored.dev. See Get a license.
  • What happens when the license expires? Any grace period first, with banners; then only sign-in, health checks and the license page answer, until a new license is applied. Nothing is deleted. See When a license expires.
  • We moved Depotex to new servers and it wants a new license. The installation ID follows the machine (on Kubernetes, the pod's identity). Request a license for the new ID before moving, and apply it on the recovery page.
  • Does applying a license need a restart? No, it applies at once. Some features notice a change of tier only after a restart.
  • Does Depotex call home? No. It doesn't need internet access to check its license. It sends the installation ID only when it downloads the vibe artifacts package list (Enterprise, off without an address).

2. Installation

  • Do I need Redis? Not for a single server. A cluster needs it. See Single Node & Cluster.
  • Which PostgreSQL? 15 or later; managed services work. The role must own the database and needn't be a superuser.
  • Can it run without internet access? Yes. Mirror the images, use Depotex or internal mirrors as upstreams, and upload vulnerability data offline (Settings → Vulnerability data).
  • Can I run it under a path such as /depotex? No, it needs its own host name.
  • Can I set it up with no browser? Yes, from a YAML file: Set up without the UI.
  • Where is the Helm chart? The published chart location is TBD; see Install with Helm.
  • How do I move from Nexus or Artifactory? Create proxy repositories on your old server as an upstream to switch builds without downtime, then publish your hosted packages to Depotex with each format's client. Ask support for help planning a migration.

3. Access

  • I'm locked out: single sign-on is down. Start one server with SSO_ENFORCEMENT_OVERRIDE=true, sign in with a password as a super admin, fix the provider, then remove the variable.
  • An account is locked after failed sign-ins. It unlocks after AUTH_LOCKOUT_DURATION (15 minutes), or a super admin unlocks it in Settings → Access → Users.
  • A super admin forgot their password. Another super admin resets it. If no one can sign in, use Forgot password with email configured, or contact support.
  • How do I give CI access without a person's token? A service account with an OAuth application, or workload identity with no secret at all. See OAuth Applications.
  • Why does everyone seem to come from the same address? TRUSTED_PROXIES doesn't include your proxy. See Behind a proxy.

4. Data

  • What's in a backup? The database (settings, people, repositories' records) and platform files (logos, avatars, plugin packages), not artifacts. Protect artifact storage with your storage platform. See Backups.
  • I lost CONFIG_ENCRYPTION_KEY. Stored credentials and backups made with it can't be read; there is no recovery. Keep the key in a secret store and with your backup records.
  • How do I reclaim disk space? Cleanup policies per space, quotas, emptying the trash, and Docker garbage collection (automatic). See Spaces.
  • Can a deleted repository be restored? Yes, for 7 days by default: Settings → Repositories → Deleted repositories.

5. Operations

  • How do I upgrade without downtime? Run a cluster and upgrade one server at a time. See Upgrades & maintenance.
  • The system check warns about Live updates. Route /api/ws to the server with WebSocket upgrades allowed.
  • How do I see what a server is doing? Settings → Logging: levels per area, log files, exports and profiles; Settings → Advanced → Scheduled jobs for background work.
  • How do I hear about security fixes? Subscribe to the security advisory feed.