@@ -25,7 +25,7 @@ Coder v1 will have 3 sunset or end-of-life dates.
25
25
<details >
26
26
<summary >How will we continue to get v1 support?</summary >
27
27
28
- Yes. Continue to either work with your account executive at Coder or leverage
28
+ Continue to either coordinate with your Coder account executive or leverage
29
29
the [ Slack] ( https://cdr.co/join-community ) channel.
30
30
31
31
</details >
@@ -39,16 +39,16 @@ make workspace compute a Kubernetes pod, a VM, or a Docker container, and an
39
39
open-source platform for the community to get the developer-centric benefits of
40
40
remote development without a license fee. See the blog post [ Lessons learned
41
41
from
42
- v1] ( https://coder.com/blog/lessons-learned-from-v1-and-oss-to-enterprise-editions )
42
+ v1] ( https://coder.com/blog/lessons-learned-from-v1-and-oss-to-enterprise-editions ) .
43
43
44
44
</details >
45
45
46
46
<details >
47
47
<summary >What Coder v2 features are open-source and paid?</summary >
48
48
49
- Functionality for a developer to be productive are in the open-source , while
49
+ Functionality for a developer to be productive are in the v2 OSS , while
50
50
scalability, governance and control features for DevOps teams are in the
51
- Enterprise paid version. [ See this page for feature
51
+ v2 Enterprise paid version. [ See this page for feature
52
52
comparisons.] ( https://coder.com/pricing )
53
53
54
54
</details >
@@ -75,23 +75,23 @@ platform into a new code base. v2 also has a different Postgres database schema.
75
75
76
76
In v1, workspaces are Kubernetes pods with an inner container based on [ container
77
77
images] ( ../images/index.md ) with an optional configure script in the image that runs additional
78
- configurations as the non-root user after the workspace is built. v1 has an
78
+ configurations as the non-root user after the workspace is built. Coder v1 has an
79
79
optional workspace template yaml spec to define compute and additional bash
80
80
scripting steps.
81
81
82
- In v2, workspaces are defined as [ Terraform
82
+ In Coder v2, workspaces are defined as [ Terraform
83
83
templates] ( https://coder.com/docs/coder-oss/latest/templates ) with Terraform
84
- resources to define the compute type. e.g., Kubernetes pod, Docker container, or
85
- VM. Docker or alternatively VM images are specified in the template. The
86
- template includes a ` startup_script ` configuration that can run the configure
87
- script in the image or additional steps like in v1 workspace templates. v1
88
- workspace applications are configured as ` coder_app ` resources in the Terraform
89
- template.
84
+ resources to specify the infrastructure provider and compute type. e.g.,
85
+ Kubernetes pod, Docker container, or VM. Docker or alternatively VM images are
86
+ specified in the template. The template includes an agent resource and
87
+ ` startup_script ` configuration that can run the configure script in the image or
88
+ additional steps like in v1 workspace templates. Coder v1 workspace applications
89
+ are configured as ` coder_app ` resources in the Terraform template.
90
90
91
91
v1 [ organizations] ( ../admin/organizations/index.md ) are
92
92
[ groups] ( https://coder.com/docs/coder-oss/latest/admin/groups ) in v2.
93
93
94
- Integration points remain like
94
+ Integration points remain the same like
95
95
[ OIDC] ( https://coder.com/docs/coder-oss/latest/admin/auth ) for single-sign-on
96
96
and specifying image registries in v2 templates.
97
97
@@ -108,7 +108,7 @@ is preferred.
108
108
<summary >Are there migration scripts from v1 to v2?</summary >
109
109
110
110
No. The database schema and architectural concepts are so different in v2, it is
111
- not reasonable to build migration scripts that meet customer deployment
111
+ not reasonable to build migration scripts that meet all customer deployment
112
112
scenarios. See [ the migration strategy] ( ./moving-to-oss.md#migration-strategy )
113
113
and [ recommendations on moving workspace
114
114
contents] ( ./moving-to-oss.md#workspaces ) .
@@ -128,6 +128,6 @@ community.
128
128
129
129
</br >
130
130
131
- > For more information on v2 concepts, please review the [ Moving to Coder
131
+ > For more information on Coder v2 concepts, please review the [ Moving to Coder
132
132
> v2] ( ./moving-to-oss.md ) guide.
133
133
0 commit comments