diff --git a/content/learning-paths/cross-platform/daytona/_index.md b/content/learning-paths/cross-platform/daytona/_index.md index cf5a27d1a9..df5aff0fa3 100644 --- a/content/learning-paths/cross-platform/daytona/_index.md +++ b/content/learning-paths/cross-platform/daytona/_index.md @@ -1,9 +1,7 @@ --- title: Manage Arm development environments with Daytona -draft: true -cascade: - draft: true + minutes_to_complete: 30 @@ -15,8 +13,8 @@ learning_objectives: - Create and manage remote development environments. prerequisites: - - One or more Arm-based computers running Windows, macOS, or Linux computer with Docker installed. - - An AWS account to create cloud development environments (optional). + - One or more Arm-based computers running Windows, macOS, or a Linux computer with Docker installed. + - Optionally, an AWS account to create cloud development environments. author_primary: Jason Andrews diff --git a/content/learning-paths/cross-platform/daytona/_review.md b/content/learning-paths/cross-platform/daytona/_review.md index b5d4b50eef..706d2093e5 100644 --- a/content/learning-paths/cross-platform/daytona/_review.md +++ b/content/learning-paths/cross-platform/daytona/_review.md @@ -15,19 +15,19 @@ review: question: > Can Daytona be used to manage local dev container based environments? answers: - - "Yes" - - "No" + - "Yes." + - "No." correct_answer: 1 explanation: > Daytona can manage local development environments. - questions: question: > - Which abstraction takes care of the details of the connection to your source code projects? + Which abstraction manages the details of the connection to your source code projects? answers: - - "Provider" - - "Target" - - "Git provider" + - "Provider." + - "Target." + - "Git provider." correct_answer: 3 explanation: > Git providers connect your source code to your workspaces. @@ -36,8 +36,8 @@ review: question: > Can Daytona manage remote development environments in machines provided by cloud service providers? answers: - - "Yes" - - "No" + - "Yes." + - "No." correct_answer: 1 explanation: > Daytona can manage development environments in AWS, Azure, and GCP. All offer Arm-based virtual machines. diff --git a/content/learning-paths/cross-platform/daytona/git-providers.md b/content/learning-paths/cross-platform/daytona/git-providers.md index d0d384b08d..d42a167d51 100644 --- a/content/learning-paths/cross-platform/daytona/git-providers.md +++ b/content/learning-paths/cross-platform/daytona/git-providers.md @@ -8,20 +8,20 @@ layout: "learningpathall" If you plan to use Daytona to work on code in your GitHub account, you can set up a Git provider. {{% notice Note %}} -This step is optional to complete the Learning Path, because Daytona doesn't require a Git provider if you want run the example project without making any changes. +This step is optional. If you want to run the example project without making any changes, you don't need to configure a Git provider. {{% /notice %}} ## How do I configure GitHub as a Git Provider for Daytona? Daytona allows you to integrate with various Git providers to manage your code repositories. You can add GitHub as a Git provider using a GitHub Personal Access Token. -Refer to the [Daytona documentation](https://www.daytona.io/docs/configuration/git-providers/) for other Git providers. +See the [Daytona documentation](https://www.daytona.io/docs/configuration/git-providers/) for other Git providers. ### How do I create a Personal Access Token on GitHub? 1. Log in to your GitHub account. -2. Navigate to **Settings** > **Developer settings** > **Personal access tokens** > **Tokens (classic)** +2. Navigate to **Settings** > **Developer settings** > **Personal access tokens** > **Tokens (classic)**. 3. Click on **Generate new token**. @@ -34,7 +34,7 @@ Refer to the [Daytona documentation](https://www.daytona.io/docs/configuration/g Make sure the Daytona server is running on your computer. -To configure GitHub run the command below: +To configure GitHub, run the command below: ```console daytona git-providers add @@ -61,4 +61,6 @@ The output displays GitHub as one of the configured Git providers with your GitH GitHub jasonrandrews jasonrandrews ``` -You have now successfully configured GitHub as a Git provider for Daytona. You can now use Daytona to manage your code repositories hosted on GitHub. +You have now successfully configured GitHub as a Git provider for Daytona. + +You can now use Daytona to manage your code repositories hosted on GitHub. diff --git a/content/learning-paths/cross-platform/daytona/install.md b/content/learning-paths/cross-platform/daytona/install.md index f91d334a8a..b59dfe3725 100644 --- a/content/learning-paths/cross-platform/daytona/install.md +++ b/content/learning-paths/cross-platform/daytona/install.md @@ -7,18 +7,26 @@ layout: "learningpathall" ## How do I install Daytona on Arm computers? -Installing Daytona on Arm-based computers is easy. The application is a single binary which can be placed anywhere. You can add the location of the `daytona` binary to your search path to make it easy to run. +Installing Daytona on Arm-based computers is easy. -Below are some recommended ways to install Daytona on a variety of operating systems. +The application is a single binary which you can place anywhere. + +To make it easy to run, you can add the location of the `daytona` binary to your search path. + +You can install Daytona on a variety of operating systems, and these are described below. ### How do I install Daytona on macOS? +Use the following code: + ```console curl -sf -L https://download.daytona.io/daytona/install.sh | sudo bash ``` ### How do I install Daytona on Arm Linux or Chrome OS? +Use the following code: + ```console curl -sf -L https://download.daytona.io/daytona/install.sh | sudo bash ``` @@ -36,9 +44,9 @@ $env:Path += ";" + $Env:APPDATA + "\bin\daytona"; [Environment]::SetEnvironmentV You can also manually download the binary for a particular operating system and place it on your computer. -Refer to the [Daytona documentation](https://www.daytona.io/docs/installation/installation/) for full details. +See the [Daytona documentation](https://www.daytona.io/docs/installation/installation/) for further information. -## How do I confirm Daytona is installed? +## How do I confirm that Daytona is installed? Print the version to confirm Daytona works on your computer: @@ -57,12 +65,12 @@ Daytona version v0.50.0 After installing Daytona, you need to start the Daytona server. {{% notice Note %}} -Always make sure Docker is running before using Daytona. +Always make sure that Docker is running before using Daytona. -Even if you plan to develop on remote computers, you still need the server on your local machine. +Even if you plan to develop on remote computers, you will still need to have the server on your local machine. {{% /notice %}} -There are 3 options you can use to start the Daytona server. +There are three options that you can use to start the Daytona server. Option 1: start the server in the background with a confirmation prompt: @@ -118,13 +126,13 @@ INFO[0013] API REQUEST URI=/health/ latency=1. You may now begin developing ``` -If you are curious, leave the Daytona server running in the terminal and see the activity as you manage development environments. +If you are curious, leave the Daytona server running in the terminal and watch the activity as you manage development environments. ## How do I stop the Daytona server? -If the server is running in the terminal, use Control-C to stop it. +If the server is running in the terminal, you can stop it by using Control-C. -If the server is running in the background, use the command below to stop it: +If the server is running in the background, you can use the command below to stop it: ```console daytona server stop @@ -139,7 +147,7 @@ daytona purge ``` {{% notice Note %}} -If you have any trouble with Daytona on macOS, remove the directory `$HOME/Library/Application\ Support/daytona` +If you experience difficulties with running Daytona on macOS, remove the directory `$HOME/Library/Application\ Support/daytona` {{% /notice %}} -With Daytona installed and the server running, you are ready to continue configuring Daytona. \ No newline at end of file +With Daytona installed and the server running, you are now ready to learn about configuring Daytona. diff --git a/content/learning-paths/cross-platform/daytona/intro.md b/content/learning-paths/cross-platform/daytona/intro.md index 120cf8bdb3..216b24fa7f 100644 --- a/content/learning-paths/cross-platform/daytona/intro.md +++ b/content/learning-paths/cross-platform/daytona/intro.md @@ -5,40 +5,46 @@ weight: 2 layout: "learningpathall" --- -[Daytona](https://www.daytona.io/) is a powerful open-source tool for managing development environments. It enables you to easily create, manage, and switch between different environments, both local and remote. +## Development Environment Manager + +[Daytona](https://www.daytona.io/) is a powerful open-source tool for managing development environments. It enables you to easily create, manage, and switch between both local and remote environments. Daytona is based on dev containers, which provide isolated and reproducible development environments. -Dev containers are lightweight, portable, and consistent environments that can be used across different development setups. They ensure that your development environment is the same regardless of where you are working. +Dev containers are lightweight, portable, and consistent environments that you can use across different development setups. They ensure that your development environment remains the same regardless of your work location. + +For more information about dev containers, see the following resources: +- [Introduction to Dev Containers](https://code.visualstudio.com/docs/remote/containers/). +- [Development Containers Specification and dev container resources](https://github.com/devcontainers/). -For more information about dev containers, you can refer to the following resources: -- [Introduction to Dev Containers](https://code.visualstudio.com/docs/remote/containers/) -- [Development Containers Specification and dev container resources](https://github.com/devcontainers/) +Daytona is a single executable that runs on a variety of computers, including Windows on Arm, Arm Linux, and macOS. It's a great way to develop on Arm as you can use it to access local and remote Arm hardware. -Daytona is a single executable that runs on a variety of computers, including Windows on Arm, Arm Linux, and macOS with Apple Silicon. It's a great way to develop on Arm as it can be used to access local and remote Arm hardware. +You can use Daytona to create development environments on the following setups: -You can use Daytona to create development environments on your local computer, on remote computers running on your local network, and on remote computers from cloud service providers such as AWS and Azure. +* On a local computer. +* On remote computers running on your local network. +* On remote computers from cloud service providers such as AWS and Azure. ## Daytona terminology -Understanding basic Daytona definitions makes it easier to get started. +Taking time to learn some the basic Daytona defintions will enable you to get started easily. You can find some of these terms described below. -### What are Git providers? +#### Git Providers A Git provider hosts Git repositories and provides tools for managing and collaborating on source code. Examples of Git providers include GitHub, GitLab, Bitbucket, and Azure Repos. With Daytona, a Git provider supplies the source code for your development environments. -### What are providers? +#### Providers -In Daytona, providers supply the resources needed to run development environments, these can be virtual machines (VMs) from AWS or Azure or container providers such as Docker. Providers abstract away the details of the underlying compute, networking, and storage. +In Daytona, providers supply the resources needed to run development environments. These can be virtual machines (VMs) from AWS or Azure, or container providers such as Docker. Providers abstract away the details of the underlying compute, networking, and storage. -### What are targets? +#### Targets A target in Daytona is the specific configuration of the development environment, including the provider, operating system, CPU and memory resources, and development tools. -The combination of a code repository from a Git provider and a target from a provider bring a development environment to life. +The combination of a code repository from a Git provider, and a target from a provider, bring a development environment to life. ## Before you begin -To try out Daytona, you need one or more Arm-based computers running Windows, macOS, or Linux. Each computer must have Docker installed. Refer to the [Docker install guide](/install-guides/docker/) for installation options. +To try out Daytona, you need one or more Arm-based computers running Windows, macOS, or Linux. Each computer must have Docker installed. See the [Docker install guide](/install-guides/docker/) for installation options. -Next, learn how to install and configure Daytona. \ No newline at end of file +In the next section, you can learn how to install and configure Daytona. \ No newline at end of file diff --git a/content/learning-paths/cross-platform/daytona/local-dev.md b/content/learning-paths/cross-platform/daytona/local-dev.md index 7e3ed727df..e01f40fcac 100644 --- a/content/learning-paths/cross-platform/daytona/local-dev.md +++ b/content/learning-paths/cross-platform/daytona/local-dev.md @@ -5,9 +5,11 @@ weight: 6 layout: "learningpathall" --- -Daytona makes it easy to manage local development environments. Follow these steps to learn how to create and manage an example local development environment. +Daytona makes it easy to manage local development environments. -You can use a small dev container example from Microsoft to learn. The example is a small Python application which uses flask to serve a single HTML page. +Follow these steps to learn how to create and manage an example local development environment. + +To have a go, you can use a small dev container example from Microsoft. The example is a small Python application which uses Flask to serve a single HTML page. Visit the [GitHub repository](https://github.com/microsoft/vscode-remote-try-python) to review the project. @@ -27,7 +29,7 @@ The workspace is created without starting any IDE. More information about how to ### Option 2: use a repository from your GitHub account -If you want to work with a repository in your GitHub account and learn how to make changes and push them to GitHub you can click the **Use this template** button on the GitHub repository. +If you want to work with a repository in your GitHub account and learn how to make changes and push them to GitHub, you can click the **Use this template** button on the GitHub repository. The template option creates a new repository in your account. Putting the repository in your account allows you to commit changes back to GitHub. @@ -37,22 +39,22 @@ daytona create --no-ide You will go through a series of prompts including: -- Select a GitHub provider -- Find the repository in your GitHub account +- Select a GitHub provider. +- Find the repository in your GitHub account. {{% notice Note %}} Use the / command to find the repo if you have many repositories in your GitHub account. {{% /notice %}} -- Select a branch -- Specify a workspace name -- Select the local (default) target using the Docker provider +- Select a branch. +- Specify a workspace name. +- Select the local (default) target using the Docker provider. The sequence is shown below: ![Create workspace #center](_images/local.gif) -The first time you create a workspace there are some delays while Docker images are pulled to your computer. After the first time, workspaces are created more quickly. +The first time you create a workspace there are some delays while Docker images are pulled to your computer. This initial setup delay is usually unique to the first time you do this, and when you create a workspace subsequently, it should be much faster. ## Connect to the workspace @@ -102,9 +104,9 @@ Any of these options can be used to connect to a Daytona workspace. A number of other IDEs can be used with Daytona. Refer to the [IDE documentation](https://www.daytona.io/docs/usage/ide/) for details. -## Start the flask application +## Start the Flask application -To start the flask application run: +To start the Flask application, run: ```console python -m flask run --port 9000 --no-debugger --no-reload @@ -112,18 +114,18 @@ python -m flask run --port 9000 --no-debugger --no-reload If you start Python in VS Code, it will automatically forward port 9000 and open a browser tab to see the web page. -If you run the Python command in a terminal after using SSH to connect to workspace, you can forward the port by running the command below on on your local machine with the name of your workspace: +If you run the Python command in a terminal after using SSH to connect to a workspace, you can forward the port by running the command below on your local machine with the name of your workspace: ```console daytona forward 9000 vscode-remote-try-python ``` -## Other workspace commands +## Useful workspace commands -Now that you can create a workspace and connect to it, there are some other commands to be aware of. +Now that you can create a workspace and connect to it, there are some other commands that you will find useful. -Use the stop command to step the workspace. The dev container will stop on your local computer. +Use the stop command to stop the workspace. The dev container will stop on your local computer: ```console daytona stop @@ -143,6 +145,6 @@ daytona delete The container is removed from the system. -You now understand the basic commands to manage local development environments with Daytona. +You have now learned the basic commands to manage local development environments with Daytona. -Next, you can learn how to manage remote development environments. +You can now move on to learn how to manage remote development environments. diff --git a/content/learning-paths/cross-platform/daytona/providers.md b/content/learning-paths/cross-platform/daytona/providers.md index df358e7650..350fba7c19 100644 --- a/content/learning-paths/cross-platform/daytona/providers.md +++ b/content/learning-paths/cross-platform/daytona/providers.md @@ -7,9 +7,9 @@ layout: "learningpathall" --- -Daytona allows you to use various cloud providers to manage your development environments. Installing providers doesn't require any configuration input. The details of using a provider are needed when a Daytona target is configured. +Daytona allows you to use various cloud providers to manage your development environments. Installing providers does not require any configuration input. The details of using a provider are required when a Daytona target is configured. -To add providers run: +To add providers, run: ```console daytona provider install @@ -17,9 +17,9 @@ daytona provider install Docker is already installed. -Select the providers you want to install using the arrow keys to select a provider. +Select the providers you want to install using the arrow keys. -Select No when asked about creating a target. You can enter the details later when a new target is created. +Select **No** when you are asked about creating a target. You can enter the details later when a new target is created. To verify providers are installed, run the following command: diff --git a/content/learning-paths/cross-platform/daytona/remote-dev-aws.md b/content/learning-paths/cross-platform/daytona/remote-dev-aws.md index 6346722443..036ea4538f 100644 --- a/content/learning-paths/cross-platform/daytona/remote-dev-aws.md +++ b/content/learning-paths/cross-platform/daytona/remote-dev-aws.md @@ -12,17 +12,19 @@ This is useful when you want to use a remote computer which is billed for the ti You can use the AWS provider to create an Arm-based development environment using AWS Graviton processors. -The main difference is that Daytona will create an EC2 instance for you and stop it when the workspace is stopped (and the billing for the EC2 instance will also stop). +The main difference is that Daytona will create an EC2 instance for you and stop it when the workspace is stopped, and the billing for the EC2 instance will also stop. ## Use the Daytona AWS provider To use the AWS provider you need an AWS account and the following items: -1. AWS Access key ID and Secret Access Key. If you don't have them, you can generate them using AWS Identity and Access Management (IAM). For additional information refer to the AWS documentation or the [AWS Credentials](/install-guides/aws_access_keys/) install guide. +1. AWS Access key ID and Secret Access Key. If you do not have them, you can generate them using AWS Identity and Access Management (IAM). For additional information, refer to the AWS documentation or the [AWS Credentials](/install-guides/aws_access_keys/) install guide. 2. Amazon Machine Image (AMI) for the operating system you want to use. The Arm-based AMIs are different from x86 so you need to look up the Arm-based AMIs. -3. Instance Type: to create Arm-based workspaces, use a Graviton-based instance type such as M6g, C6g, R6g, or T4g. Most Graviton-based instances have `g` in the name. There are instances for Graviton2, Graviton3, and Graviton4 processors. +3. Instance Type: to create Arm-based workspaces, use a Graviton-based instance type such as M6g, C6g, R6g, or T4g. + + Most Graviton-based instances have `g` in the name. There are instances for Graviton2, Graviton3, and Graviton4 processors. {{% notice Note %}} You can use Amazon EC2 `t4g.small` instances powered by AWS Graviton2 processors free for up to 750 hours per month until Dec 31st 2025. @@ -30,37 +32,37 @@ You can use Amazon EC2 `t4g.small` instances powered by AWS Graviton2 processors ### Configure an AWS target -Use the same Daytona command to create a new target based on the AWS provider. +Use the same Daytona command to create a new target based on the AWS provider: ```console daytona target set ``` -1. Select the AWS provider then select `New Target`. +1. Select the AWS provider, then select `New Target`. -2. Enter a name for the new target so you can recognize it as an AWS EC2 target in the future. +2. Enter a name for the new target so that you can recognize it as an AWS EC2 target in the future. 3. Configure the target with the information below: -Access Key ID: Your access key ID you generate in AWS for your account. +**Access Key ID**: Your access key ID that you generate in AWS for your account. -Device Name: This is the root device of your EC2 virtual machine, leave the default. +**Device Name**: This is the root device of your EC2 virtual machine. Leave the default. -Image ID: This is the AMI for the operating system you want to run, make sure to use an Arm AMI. For example, Ubuntu 24.04 for Arm is `ami-096ea6a12ea24a797`. +**Image ID**: This is the AMI for the operating system you want to run. Make sure to use an Arm AMI. For example, Ubuntu 24.04 for Arm is `ami-096ea6a12ea24a797`. -Instance Type: EC2 instance type to create, for example `t4g.small`. +**Instance Type**: EC2 instance type to create, for example `t4g.small`. -Region: The AWS region to create the EC2 instance such as `us-east-1` in N. Virginia or `us-west-2` in Oregon. +**Region**: The AWS region to create the EC2 instance such as `us-east-1` in N. Virginia or `us-west-2` in Oregon. -Secret Access Key: Also generated for your account along with the access key ID. +**Secret Access Key**: This is also generated for your account along with the access key ID. -Volume Size: size of the disk in GB. Increase the default if you want more disk space. +**Volume Size**: This is the size of the disk in GB. Increase the default if you want more disk space. The values are shown below: ![Create aws workspace #center](_images/aws.png) -Once the new target is created, you can list the targets and confirm the parameters. +Once the new target is created, you can list the targets and confirm the parameters: ```console daytona target list @@ -85,20 +87,20 @@ Target Options: { } ``` -You can now use `daytona create` to create another workspace for the example Flask project, but this time on an AWS EC2 Arm-based instance. +You can now use `daytona create` to create another workspace for the example Flask project, but this time on an AWS EC2 Arm-based instance: ```console daytona create --no-ide https://github.com/microsoft/vscode-remote-try-python/tree/main ``` -After the workspace is created, all of the same commands you used on the local workspace can be used to connect, including `daytona code` and `daytona ssh`. +After the workspace is created, all of the same commands that you used on the local workspace can be used to connect, including `daytona code` and `daytona ssh`. ## Start and stop the workspace When you use the `daytona stop` command on the AWS provided workspace, the EC2 instance is stopped. You can confirm this in your AWS console. The billing for the compute is stopped, but there is a minimal cost for the storage of stopped EC2 instances. -When you run `daytona start` on the workspace, it doesn't automatically start. You need to manually start the EC2 instance first and then run `daytona start`. +When you run `daytona start` on the workspace, it will not automatically start. You need to manually start the EC2 instance first and then run `daytona start`. -The Daytona AWS provider takes care of everything related to installing Docker, setting up remote access, creating a security group that is only accessible from your machine. You can see EC2 instance details in your AWS account. +The Daytona AWS provider manages everything related to installing Docker, setting up remote access, and creating a security group that is only accessible from your machine. You can see EC2 instance details in your AWS account. You have now learned how to manage remote development environments with the AWS provider. diff --git a/content/learning-paths/cross-platform/daytona/remote-dev-docker.md b/content/learning-paths/cross-platform/daytona/remote-dev-docker.md index 4b45c51c0b..5fedee430d 100644 --- a/content/learning-paths/cross-platform/daytona/remote-dev-docker.md +++ b/content/learning-paths/cross-platform/daytona/remote-dev-docker.md @@ -6,17 +6,17 @@ layout: "learningpathall" --- -With Daytona, you can create and manage workspaces on other computers, not your local computer. +With Daytona, you can create and manage workspaces on another computer that is not your local computer. This is useful if you have Arm-based servers on your local network or in the cloud and you want to use them for development. There are two common use cases: -1. The remote computer is always running. +1. The remote computer is always running. 2. The remote computer should stop when you stop your workspace. -The first case is typical for computers on your local network or in the cloud that you don't pay for by the minute or hour. +The first case is typical for computers on your local network or in the cloud that you do not pay for by the minute or hour. -The second case is for cloud resources that are billed as you use them (pay as you go) and you don't want to leave idle computers running. +The second case is for cloud resources that are billed as you use them (pay as you go) and you do not want to leave idle computers running. ## Daytona targets @@ -44,7 +44,7 @@ Target Options: { } ``` -You can use Daytona to manage remote development environments for always on computers (use case #1) using the Docker providers and SSH access to the computer. +You can use Daytona to manage remote development environments for always-on computers, which corresponds to the first use case, using the Docker providers and SSH access to the computer. {{% notice Note %}} Make sure Docker is installed on the remote computer. @@ -54,13 +54,13 @@ Make sure Docker is installed on the remote computer. You can use key based SSH to configure Daytona targets and manage remote workspaces. -If you are using a password to SSH to the remote computer, create key based SSH by putting a public key on the remote computer at `$HOME/.ssh/authorized_keys` +If you are using a password to SSH to the remote computer, create a key-based SSH by putting a public key on the remote computer at `$HOME/.ssh/authorized_keys` -If you need to create a key pair you can use `ssh-keygen` to create a key pair with a public and private key. +If you need to create a key pair, then you can use `ssh-keygen` to create a key pair with a public and private key. -Refer to the [SSH install guide](/install-guides/ssh/) for more details. +See the [SSH install guide](/install-guides/ssh/) for more details. -Confirm you can SSH to the remote computer using a private key: +Confirm that you can SSH to the remote computer using a private key: ```console ssh -i user@ip @@ -70,7 +70,7 @@ You need the name of the private key file on your local computer to configure a ## Managing remote Docker development environments -Daytona allows you to manage remote development environments for always on computers using the Docker provider. +Daytona allows you to manage remote development environments for always-on computers using the Docker provider. ```console daytona target set @@ -78,31 +78,31 @@ daytona target set 1. Select the Docker provider then select `New Target`. -2. Enter a name for the new target, such as the name of the machine, so you can recognize it in the future. +2. Enter a name for the new target, such as the name of the machine, so that you can recognize it in the future. 3. Configure the target with the information below: -Remote Hostname: The IP address or the DNS name (if you have one) of the remote computer. +**Remote Hostname**: This is the IP address or the DNS name of the remote computer, if you have one. -Remote Password: Not used, leave it blank. +**Remote Password**: This is not used, so leave it blank. -Remote Port: SSH port, default is 22 unless you have changed the SSH configuration on the remote computer to use a different port. +**Remote Port**: This is the SSH port, and the default is 22 unless you have changed the SSH configuration on the remote computer to use a different port. -Remote User: The username you use to SSH, it cannot be root. +**Remote User**: This is the username you use to SSH. It cannot be root. -Sock Path: Path to the Docker daemon, keep the default. +**Sock Path**: This is the path to the Docker daemon. Keep the default. -Workspace Data Dir: Location Daytona will store information on the remote computer, leave the default or change it. +**Workspace Data Dir**: This is the location where Daytona will store information on the remote computer. Leave the default, or change it to your preference. The values are shown below: ![Create remote workspace #center](_images/docker-remote.png) -The the next screen, enter the Remote Private Key Path. This is the path to the private key file you use to SSH to the remote computer, the same file used to `ssh -i ` +In the next screen, enter the Remote Private Key Path. This is the path to the private key file that you use to SSH to the remote computer. It is the same file used to `ssh -i ` Your target configuration is complete. -4. List the targets to confirm your information +4. List the targets to confirm your information: ```console daytona target list @@ -141,15 +141,15 @@ Target Options: { You see your new target and the parameters listed. It is now the default target. -### Create a new worksspace on the remote computer +### Create a new workspace on the remote computer -You can use `daytona create` to create a workspace on the remote computer. The command is the same as on the local computer. The default target is used, the new Docker remote computer. +You can use `daytona create` to create a workspace on the remote computer. The command is the same as on the local computer. The default target is used: the new Docker remote computer. ```console daytona create --no-ide https://github.com/microsoft/vscode-remote-try-python/tree/main ``` -You can also specify the target using the `-t` option be explicit about which target to use. +You can also specify the target using the `-t` option be explicit about which target to use: ```console daytona create -t arm-server-1 --no-ide https://github.com/microsoft/vscode-remote-try-python/tree/main @@ -161,7 +161,7 @@ The `daytona list` command shows the target where each workspace is running. daytona list ``` -If you have a workspace on both the local computer and the remote computer the values in the target column are similar to: +If you have a workspace on both the local computer and the remote computer, the values in the target column are similar to: ```output Workspace Repository Target Status @@ -175,4 +175,6 @@ Be patient the first time you create the new workspace on the remote computer as The management commands from the previous section are the same on the local computer and the remote computer. This includes `daytona code` and `daytona ssh`. Use them in the same way for the remote workspace. -You have now learned how to manage remote development environments using the Docker provider. Next, learn how to manage remote development environments using the AWS provider. \ No newline at end of file +You have now learned how to manage remote development environments using the Docker provider. + +In the next section, you can learn how to manage remote development environments using the AWS provider. \ No newline at end of file