mirrors/opencode
1
0
Fork 0
mirror of https://github.com/sst/opencode.git synced 2025-08-03 21:28:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

docs: update enterprise doc

Browse source
This commit is contained in:
Jay V 2025-07-16 16:44:28 -04:00
parent eb4cdf4b20
commit 7520f5efa8
1 changed files with 42 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

72
packages/web/src/content/docs/docs/enterprise.mdx
View file

@ -23,7 +23,7 @@ Since opencode is open source and does not store any of your code or context dat
**opencode does not store your code or context data.** All processing happens locally or through direct API calls to your AI provider.
The only caveat here is the optional `/share` feature that must be manually enabled.
The only caveat here is the optional `/share` feature.
---
@ -33,6 +33,17 @@ If a user enables the `/share` feature, the conversation and the data associated
The data is currently served through our CDN's edge network, and is cached on the edge near your users.
We recommend you disable this for your trial.
```json title="opencode.json"
{
"$schema": "https://opencode.ai/config.json",
"share": "disabled"
}
```
[Learn more about sharing](/docs/share).
---
### Code ownership
@ -51,9 +62,37 @@ pricing and implementation options.
### SSO
SSO integration can be implemented for enterprise deployments after your trial. Currently users manage and configure individual API keys locally.
SSO integration can be implemented for enterprise deployments after your trial.
This will allow your team's session data and shared conversations to be protected
by your enterprise's authentication system.
This can be switched to a centralized authentication system that your organization uses.
---
### Private NPM
opencode supports private npm registries through Bun's native `.npmrc` file support. If your organization uses a private registry, such as JFrog Artifactory, Nexus, or similar, ensure developers are authenticated before running opencode.
To set up authentication with your private registry:
```bash
npm login --registry=https://your-company.jfrog.io/api/npm/npm-virtual/
```
This creates `~/.npmrc` with authentication details. opencode will automatically
pick this up.
:::caution
You must be logged into the private registry before running opencode.
:::
Alternatively, you can manually configure a `.npmrc` file:
```bash title="~/.npmrc"
registry=https://your-company.jfrog.io/api/npm/npm-virtual/
//your-company.jfrog.io/api/npm/npm-virtual/:_authToken=${NPM_AUTH_TOKEN}
```
Developers must be logged into the private registry before running opencode to ensure packages can be installed from your enterprise registry.
---
@ -61,30 +100,3 @@ This can be switched to a centralized authentication system that your organizati
The share feature can be self-hosted and the share pages can be made accessible
only after the user has been authenticated.
---
### Private NPM registries
opencode supports private npm registries through Bun's native `.npmrc` file support. If your organization uses a private registry (such as JFrog Artifactory, Nexus, or similar), ensure developers are authenticated before running opencode.
To set up authentication with your private registry:
```bash
# Authenticate with your enterprise registry
npm login --registry=https://your-company.jfrog.io/api/npm/npm-virtual/
# This creates ~/.npmrc with authentication
# opencode will automatically use it through Bun's native support
```
Alternatively, you can manually configure a `.npmrc` file:
```bash
# ~/.npmrc
registry=https://your-company.jfrog.io/api/npm/npm-virtual/
//your-company.jfrog.io/api/npm/npm-virtual/:_authToken=${NPM_AUTH_TOKEN}
```
**Important**: Developers must be logged into the private registry before running opencode
to ensure packages can be installed from your enterprise registry.