docs: refactor workspaces, projects, and targets (#207)

Signed-off-by: stefanicjuraj <[email protected]>

Author: stefanicjuraj

astro.config.mjs

@@ -97,6 +97,13 @@ export default defineConfig({
                 icon: 'git-commit.svg',
               },
             },
+            {
+              label: 'Target Configs',
+              link: '/configuration/target-config',
+              attrs: {
+                icon: 'tag.svg',
+              },
+            },
             {
               label: 'Container Registries',
               link: '/configuration/container-registries',
@@ -105,10 +112,17 @@ export default defineConfig({
               },
             },
             {
-              label: 'Targets',
-              link: '/configuration/targets',
+              label: 'Workspace Templates',
+              link: '/configuration/workspace-templates',
               attrs: {
-                icon: 'tag.svg',
+                icon: 'computer.svg',
+              },
+            },
+            {
+              label: 'Server',
+              link: '/configuration/server',
+              attrs: {
+                icon: 'server.svg',
               },
             },
             {
@@ -131,17 +145,17 @@ export default defineConfig({
               },
             },
             {
-              label: 'Agent Toolbox',
-              link: '/usage/agent-toolbox',
+              label: 'Targets',
+              link: '/usage/targets',
               attrs: {
-                icon: 'agent-toolbox.svg',
+                icon: 'tag.svg',
               },
             },
             {
-              label: 'Projects',
-              link: '/usage/projects',
+              label: 'Agent Toolbox',
+              link: '/usage/agent-toolbox',
               attrs: {
-                icon: 'folder.svg',
+                icon: 'agent-toolbox.svg',
               },
             },
             {
@@ -173,10 +187,10 @@ export default defineConfig({
               },
             },
             {
-              label: 'Server',
-              link: '/usage/server',
+              label: 'Runners',
+              link: '/usage/runners',
               attrs: {
-                icon: 'server.svg',
+                icon: 'cluster.svg',
               },
             },
           ],

src/content/docs/configuration/container-registries.mdx

@@ -11,35 +11,66 @@ import Label from '@components/Label.astro'
 
 Container registries store credentials used to pull container images from specified registry servers. Adding container registry credentials is useful for users who want to create Workspaces from private images and those hosted on private registries.
 
-## Add a Container Registry
+Container registries are managed through environment variables, enabling you to securely store and manage credentials. Daytona provides options to set, list, and delete container registries for your Workspaces.
 
-Daytona provides an option to add a container registry for your Workspace.
+Daytona provides options to set global environment variables that apply to all Workspaces or set environment variables for a specific Workspace. To set environment variables for a specific Workspace, use the `--env` flag when creating a new Workspace, or configure the environment variables in the Workspace's template. For server-wide environment variables that apply to all new Workspaces, use the `daytona env` command.
 
-1. Run the following command to add a container registry:
+## Set a Container Registry
+
+Daytona provides an option to set a container registry through environment variables for your Workspace.
+
+1. Run the following command to set a container registry environment variable:
 
 ```shell
-daytona container-registry add
+daytona env set
 ```
 
-Upon running the command, you will be prompted to enter the following details:
-
-- **Server URL**: The URL of the container registry.
-- **Username**: The username to authenticate with the container registry.
-- **Password**: The password to authenticate with the container registry.
+2. Set the server environment variable key for the container registry:
 
 ```text
-Server URL
+Set server environment variable
+Key
 >
+```
 
-Username
->
+:::tip
+Add the following environment variables to configure your container registry:
+
+- **`<*>_CONTAINER_REGISTRY_SERVER`**
+
+  The URL of the container registry.
+
+- **`<*>_CONTAINER_REGISTRY_USERNAME`**
+
+  The username to authenticate with the container registry.
+
+- **`<*>_CONTAINER_REGISTRY_PASSWORD`**
+
+  The password to authenticate with the container registry.
 
-Password
+:::
+
+<br />
+
+3. Set the server environment variable value for the container registry:
+
+```text
+Value
 >
 ```
 
+4. Select whether to add another environment variable:
+
+```text
+Add another environment variable?
+
+[Yes]     [No]
+```
+
+Upon selecting, Daytona will set the container registry environment variables for your Workspace.
+
 ```text
-Registry set successfully
+Server environment variables have been set successfully
 ```
 
 ## List Container Registries
@@ -49,15 +80,15 @@ Daytona provides an option to list the container registries configured for your
 1. Run the following command to list the container registries:
 
 ```shell
-daytona container-registry list
+daytona env list
 ```
 
-Upon running this command, Daytona will display a list of your configured container registries with their respective details.
+Upon running this command, Daytona will display a list of your configured container registries' environment variables.
 
 ```text
-Server                  Username            Password                     
-─────────────────────────────────────────────────────────────────────    
-myregistry.com          daytona             ********  
+Key                         Value
+────────────────────────────────────  
+MyEnvVariable               ********
 ```
 
 ## Delete a Container Registry
@@ -67,19 +98,19 @@ Daytona provides an option to delete a container registry from your Workspace.
 1. Run the following command to delete a container registry:
 
 ```shell
-daytona container-registry delete
+daytona env delete
 ```
 
 Upon running this command, you will be prompted to select the container registry you want to delete.
 
 ```text
-Choose a container registry
+Select Server Environment Variables To Delete
 1 item
 ===
-myregistry.com
-daytona
+MyEnvVariable
+********
 ```
 
 ```text
-Container registry deleted successfully
+Server environment variables have been successfully removed
 ```

src/content/docs/configuration/git-providers.mdx

@@ -19,6 +19,8 @@ By adding a Git Provider, your credentials are securely embedded into your Works
 
 ## Add a Git Provider
 
+Daytona provides an option to add a Git Provider, enabling you to connect your preferred Git Provider and access your repositories directly from Daytona.
+
 1. Run the following command to add a Git Provider:
 
 ```shell
@@ -116,7 +118,7 @@ Git provider has been registered
 
 ## List Connected Git Providers
 
-Daytona allows you to keep track of your Git Providers by listing all previously created Git Providers.
+Daytona provides an option to keep track of your Git Providers by listing all previously created Git Providers.
 
 1. Run the following command to list currently connected Git Providers:
 
@@ -133,7 +135,7 @@ GitLab (alias)
 
 ## Update a Git Provider
 
-Daytona allows you to update an existing Git Provider, enabling you to apply the latest enhancements and bug fixes.
+Daytona provides an option to update an existing Git Provider, enabling you to apply the latest enhancements and bug fixes.
 
 1. Run the following command to update a Git Provider:
 
@@ -175,7 +177,7 @@ Git provider has been updated
 
 ## Delete a Git Provider
 
-Daytona allows you to delete Git Providers, helping you manage and delete those that are no longer needed. Once a Git Provider is deleted, you will not be able to manage or deploy Workspaces without adding another Git Provider.
+Daytona provides an option to delete Git Providers, helping you manage and delete those that are no longer needed. Once a Git Provider is deleted, you will not be able to manage or deploy Workspaces without adding another Git Provider.
 
 1. Run the following command to delete a Git Provider:
 
@@ -201,7 +203,7 @@ Git provider has been removed
 
 ## GitHub
 
-Daytona allows you to connect your GitHub account and access your repositories directly from Daytona.
+Daytona provides an option to connect your GitHub account and access your repositories directly from Daytona.
 
 1. Run the following command to add GitHub as a Git Provider:
 
@@ -243,7 +245,7 @@ Git provider has been registered
 
 ## GitLab
 
-Daytona allows you to connect your GitLab account and access your repositories directly from Daytona.
+Daytona provides an option to connect your GitLab account and access your repositories directly from Daytona.
 
 1. Run the following command to add GitLab as a Git Provider:
 
@@ -285,7 +287,7 @@ Git provider has been registered
 
 ## Bitbucket
 
-Daytona allows you to connect your Bitbucket account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Bitbucket account and access your repositories directly from Daytona.
 
 1. Run the following command to add Bitbucket as a Git Provider:
 
@@ -332,7 +334,7 @@ Git provider has been registered
 
 ## GitHub Enterprise Server
 
-Daytona allows you to connect your GitHub Enterprise Server account and access your repositories directly from Daytona.
+Daytona provides an option to connect your GitHub Enterprise Server account and access your repositories directly from Daytona.
 
 1. Run the following command to add GitHub Enterprise Server as a Git Provider:
 
@@ -385,7 +387,7 @@ Git provider has been registered
 
 ## GitLab Self-Managed
 
-Daytona allows you to connect your GitLab Self-Managed account and access your repositories directly from Daytona.
+Daytona provides an option to connect your GitLab Self-Managed account and access your repositories directly from Daytona.
 
 1. Run the following command to add GitLab Self-Managed as a Git Provider:
 
@@ -438,7 +440,7 @@ Git provider has been registered
 
 ## Bitbucket Server
 
-Daytona allows you to connect your Bitbucket Server account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Bitbucket Server account and access your repositories directly from Daytona.
 
 1. Run the following command to add Bitbucket Server as a Git Provider:
 
@@ -496,7 +498,7 @@ Git provider has been registered
 
 ## Codeberg
 
-Daytona allows you to connect your Codeberg account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Codeberg account and access your repositories directly from Daytona.
 
 1. Run the following command to add Codeberg as a Git Provider:
 
@@ -543,7 +545,7 @@ Git provider has been registered
 
 ## Gitea
 
-Daytona allows you to connect your Gitea account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Gitea account and access your repositories directly from Daytona.
 
 1. Run the following command to add Gitea as a Git Provider:
 
@@ -596,7 +598,7 @@ Git provider has been registered
 
 ## Gitness
 
-Daytona allows you to connect your Gitness account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Gitness account and access your repositories directly from Daytona.
 
 1. Run the following command to add Gitness as a Git Provider:
 
@@ -649,7 +651,7 @@ Git provider has been registered
 
 ## Azure DevOps
 
-Daytona allows you to connect your Azure DevOps account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Azure DevOps account and access your repositories directly from Daytona.
 
 1. Run the following command to add Azure DevOps as a Git Provider:
 
@@ -702,7 +704,7 @@ Git provider has been registered
 
 ## AWS CodeCommit
 
-Daytona allows you to connect your AWS CodeCommit account and access your repositories directly from Daytona.
+Daytona provides an option to connect your AWS CodeCommit account and access your repositories directly from Daytona.
 
 1. Run the following command to add AWS CodeCommit as a Git Provider:
 
@@ -766,7 +768,7 @@ Git provider has been registered
 
 ## Gogs
 
-Daytona allows you to connect your Gogs account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Gogs account and access your repositories directly from Daytona.
 
 1. Run the following command to add Gogs as a Git Provider:
 
@@ -832,7 +834,7 @@ Git provider has been registered
 
 ## Gitee
 
-Daytona allows you to connect your Gitee account and access your repositories directly from Daytona.
+Daytona provides an option to connect your Gitee account and access your repositories directly from Daytona.
 
 1. Run the following command to add Gitee as a Git Provider: