mirror of
https://github.com/coder/coder.git
synced 2026-06-02 20:48:20 +00:00
chore(docs): change mentions of enterprise to premium (#15258)
Matches our latest licensing verbiage.
This commit is contained in:
Stephen Kirby
@@ -10,11 +10,11 @@ page describes possible deployments, challenges, and risks associated with them.
|
||||
|
||||
|
||||
|
||||
## Enterprise
|
||||
## Premium
|
||||
|
||||
|
||||
|
||||
## Multi-Region Enterprise
|
||||
## Multi-Region Premium
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -173,8 +173,8 @@ example, running 10 provisioner containers will allow 10 users to start
|
||||
workspaces at the same time.
|
||||
|
||||
By default, the Coder server runs 3 built-in provisioner daemons, but the
|
||||
_Enterprise_ Coder release allows for running external provisioners to separate
|
||||
the load caused by workspace provisioning on the `coderd` nodes.
|
||||
_Premium_ Coder release allows for running external provisioners to separate the
|
||||
load caused by workspace provisioning on the `coderd` nodes.
|
||||
|
||||
#### Scaling formula
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ can only be delivered to one method, and this method is configured globally with
|
||||
[`CODER_NOTIFICATIONS_METHOD`](../../../reference/cli/server.md#--notifications-method)
|
||||
(default: `smtp`).
|
||||
|
||||
Enterprise customers can configure which method to use for each of the supported
|
||||
Premium customers can configure which method to use for each of the supported
|
||||
[Events](#workspace-events); see the
|
||||
[Preferences](#delivery-preferences-enterprise-premium) section below for more
|
||||
details.
|
||||
|
||||
@@ -173,7 +173,7 @@ $ coder server --derp-config-path derpmap.json
|
||||
|
||||
The dashboard (and web apps opened through the dashboard) are served from the
|
||||
coder server, so they can only be geo-distributed with High Availability mode in
|
||||
our Enterprise Edition. [Reach out to Sales](https://coder.com/contact) to learn
|
||||
our Premium Edition. [Reach out to Sales](https://coder.com/contact) to learn
|
||||
more.
|
||||
|
||||
## Browser-only connections (enterprise) (premium)
|
||||
|
||||
@@ -121,7 +121,7 @@ not it is still accessible.
|
||||
|
||||
|
||||
The sharing level is limited by the maximum level enforced in the template
|
||||
settings in enterprise deployments, and not restricted in OSS deployments.
|
||||
settings in premium deployments, and not restricted in OSS deployments.
|
||||
|
||||
This can also be used to change the sharing level of `coder_app`s by entering
|
||||
their port number in the sharable ports UI. The `share` attribute on `coder_app`
|
||||
@@ -131,8 +131,8 @@ to the app.
|
||||
|
||||
### Configure maximum port sharing level (enterprise) (premium)
|
||||
|
||||
Enterprise-licensed template admins can control the maximum port sharing level
|
||||
for workspaces under a given template in the template settings. By default, the
|
||||
Premium-licensed template admins can control the maximum port sharing level for
|
||||
workspaces under a given template in the template settings. By default, the
|
||||
maximum sharing level is set to `Owner`, meaning port sharing is disabled for
|
||||
end-users. OSS deployments allow all workspaces to share ports at both the
|
||||
`authenticated` and `public` levels.
|
||||
|
||||
@@ -122,5 +122,5 @@ log entry:
|
||||
|
||||
## Enabling this feature
|
||||
|
||||
This feature is only available with an enterprise license.
|
||||
This feature is only available with an premium license.
|
||||
[Learn more](../licensing/index.md)
|
||||
|
||||
@@ -17,7 +17,7 @@ Please note that these logs are not recorded or captured by the Coder
|
||||
organization in any way, shape, or form.
|
||||
|
||||
> This is an [Premium or Enterprise](https://coder.com/pricing) feature. To
|
||||
> learn more about Coder Enterprise, please
|
||||
> learn more about Coder licensing, please
|
||||
> [contact sales](https://coder.com/contact).
|
||||
|
||||
## How this works
|
||||
|
||||
@@ -60,7 +60,7 @@ infrastructure, software, or security patches. Learn more about
|
||||
|
||||
### Template update policies (enterprise) (premium)
|
||||
|
||||
Enterprise template admins may want workspaces to always remain on the latest
|
||||
Licensed template admins may want workspaces to always remain on the latest
|
||||
version of their parent template. To do so, enable **Template Update Policies**
|
||||
in the template's general settings. All non-admin users of the template will be
|
||||
forced to update their workspaces before starting them once the setting is
|
||||
|
||||
@@ -30,8 +30,8 @@ manage infrastructure costs.
|
||||
## Failure cleanup (enterprise) (premium)
|
||||
|
||||
Failure cleanup defines how long a workspace is permitted to remain in the
|
||||
failed state prior to being automatically stopped. Failure cleanup is an
|
||||
enterprise-only feature.
|
||||
failed state prior to being automatically stopped. Failure cleanup is only
|
||||
available for licensed customers.
|
||||
|
||||
## Dormancy threshold (enterprise) (premium)
|
||||
|
||||
@@ -41,13 +41,13 @@ by the time elapsed since a user last accessed the workspace. A workspace in the
|
||||
dormant state is not eligible for autostart and must be manually activated by
|
||||
the user before being accessible. Coder stops workspaces during their transition
|
||||
to the dormant state if they are detected to be running. Dormancy Threshold is
|
||||
an enterprise-only feature.
|
||||
only available for licensed customers.
|
||||
|
||||
## Dormancy auto-deletion (enterprise) (premium)
|
||||
|
||||
Dormancy Auto-Deletion allows a template admin to dictate how long a workspace
|
||||
is permitted to remain dormant before it is automatically deleted. Dormancy
|
||||
Auto-Deletion is an enterprise-only feature.
|
||||
Auto-Deletion is only available for licensed customers.
|
||||
|
||||
## Autostop requirement (enterprise) (premium)
|
||||
|
||||
|
||||
@@ -18,4 +18,4 @@ user can use the template to create a workspace. To prevent this, disable the
|
||||
|
||||
|
||||
|
||||
Permissions is an enterprise-only feature.
|
||||
Permissions is a premium-only feature.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# FAQs
|
||||
|
||||
Frequently asked questions on Coder OSS and Enterprise deployments. These FAQs
|
||||
come from our community and enterprise customers, feel free to
|
||||
Frequently asked questions on Coder OSS and licensed deployments. These FAQs
|
||||
come from our community and customers, feel free to
|
||||
[contribute to this page](https://github.com/coder/coder/edit/main/docs/tutorials/faqs.md).
|
||||
|
||||
For other community resources, see our
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
# Guides and Tutorials
|
||||
|
||||
Here you can find a list of employee-written guides on Coder for OSS and
|
||||
Enterprise. These tutorials are hosted on our
|
||||
[GitHub](https://github.com/coder/coder/) where you can leave feedback or
|
||||
request new topics to be covered.
|
||||
Here you can find a list of employee-written guides on Coder. These tutorials
|
||||
are hosted on our [GitHub](https://github.com/coder/coder/) where you can leave
|
||||
feedback or request new topics to be covered.
|
||||
|
||||
<children>
|
||||
This page is rendered on <https://coder.com/docs/tutorials>. Refer to the other documents in the `docs/tutorials/` directory for specific employee-written guides.
|
||||
|
||||
@@ -123,7 +123,7 @@ it is still accessible.
|
||||
|
||||
|
||||
> The sharing level is limited by the maximum level enforced in the template
|
||||
> settings in enterprise deployments, and not restricted in OSS deployments.
|
||||
> settings in licensed deployments, and not restricted in OSS deployments.
|
||||
|
||||
This can also be used to change the sharing level of port-based `coder_app`s by
|
||||
entering their port number in the sharable ports UI. The `share` attribute on
|
||||
|
||||
@@ -90,7 +90,7 @@ manually updated the workspace.
|
||||
|
||||
## Bulk operations (enterprise) (premium)
|
||||
|
||||
Enterprise admins may apply bulk operations (update, delete, start, stop) in the
|
||||
Licensed admins may apply bulk operations (update, delete, start, stop) in the
|
||||
**Workspaces** tab. Select the workspaces you'd like to modify with the
|
||||
checkboxes on the left, then use the top-right **Actions** dropdown to apply the
|
||||
operation.
|
||||
|
||||
@@ -51,7 +51,7 @@ for your workspace.
|
||||
|
||||
## Autostop requirement (enterprise) (premium)
|
||||
|
||||
Enterprise template admins may enforce a required stop for workspaces to apply
|
||||
Licensed template admins may enforce a required stop for workspaces to apply
|
||||
updates or undergo maintenance. These stops ignore any active connections or
|
||||
inactivity bumps. Rather than being specified with a CRON, admins set a
|
||||
frequency for updates, either in **days** or **weeks**. Workspaces will apply
|
||||
@@ -106,5 +106,5 @@ durations. Template admins configure an inactivity period after which your
|
||||
workspaces will gain a `dormant` badge. A separate period determines how long
|
||||
workspaces will remain in the dormant state before automatic deletion.
|
||||
|
||||
Enterprise admins may also configure failure cleanup, which will automatically
|
||||
Licensed admins may also configure failure cleanup, which will automatically
|
||||
delete workspaces that remain in a `failed` state for too long.
|
||||
|
||||
Reference in New Issue
Block a user