Skip to content

Commit f828759

Browse files
Merge pull request #1520 from madeline-underwood/Daytona
Daytona_AP approved and ready to be merged
2 parents 901a6dc + 23ceac5 commit f828759

File tree

9 files changed

+128
-108
lines changed

9 files changed

+128
-108
lines changed

content/learning-paths/cross-platform/daytona/_index.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,7 @@
11
---
22
title: Manage Arm development environments with Daytona
33

4-
draft: true
5-
cascade:
6-
draft: true
4+
75

86
minutes_to_complete: 30
97

@@ -15,8 +13,8 @@ learning_objectives:
1513
- Create and manage remote development environments.
1614

1715
prerequisites:
18-
- One or more Arm-based computers running Windows, macOS, or Linux computer with Docker installed.
19-
- An AWS account to create cloud development environments (optional).
16+
- One or more Arm-based computers running Windows, macOS, or a Linux computer with Docker installed.
17+
- Optionally, an AWS account to create cloud development environments.
2018

2119
author_primary: Jason Andrews
2220

content/learning-paths/cross-platform/daytona/_review.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,19 +15,19 @@ review:
1515
question: >
1616
Can Daytona be used to manage local dev container based environments?
1717
answers:
18-
- "Yes"
19-
- "No"
18+
- "Yes."
19+
- "No."
2020
correct_answer: 1
2121
explanation: >
2222
Daytona can manage local development environments.
2323
2424
- questions:
2525
question: >
26-
Which abstraction takes care of the details of the connection to your source code projects?
26+
Which abstraction manages the details of the connection to your source code projects?
2727
answers:
28-
- "Provider"
29-
- "Target"
30-
- "Git provider"
28+
- "Provider."
29+
- "Target."
30+
- "Git provider."
3131
correct_answer: 3
3232
explanation: >
3333
Git providers connect your source code to your workspaces.
@@ -36,8 +36,8 @@ review:
3636
question: >
3737
Can Daytona manage remote development environments in machines provided by cloud service providers?
3838
answers:
39-
- "Yes"
40-
- "No"
39+
- "Yes."
40+
- "No."
4141
correct_answer: 1
4242
explanation: >
4343
Daytona can manage development environments in AWS, Azure, and GCP. All offer Arm-based virtual machines.

content/learning-paths/cross-platform/daytona/git-providers.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,20 +8,20 @@ layout: "learningpathall"
88
If you plan to use Daytona to work on code in your GitHub account, you can set up a Git provider.
99

1010
{{% notice Note %}}
11-
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.
11+
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.
1212
{{% /notice %}}
1313

1414
## How do I configure GitHub as a Git Provider for Daytona?
1515

1616
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.
1717

18-
Refer to the [Daytona documentation](https://www.daytona.io/docs/configuration/git-providers/) for other Git providers.
18+
See the [Daytona documentation](https://www.daytona.io/docs/configuration/git-providers/) for other Git providers.
1919

2020
### How do I create a Personal Access Token on GitHub?
2121

2222
1. Log in to your GitHub account.
2323

24-
2. Navigate to **Settings** > **Developer settings** > **Personal access tokens** > **Tokens (classic)**
24+
2. Navigate to **Settings** > **Developer settings** > **Personal access tokens** > **Tokens (classic)**.
2525

2626
3. Click on **Generate new token**.
2727

@@ -34,7 +34,7 @@ Refer to the [Daytona documentation](https://www.daytona.io/docs/configuration/g
3434

3535
Make sure the Daytona server is running on your computer.
3636

37-
To configure GitHub run the command below:
37+
To configure GitHub, run the command below:
3838

3939
```console
4040
daytona git-providers add
@@ -61,4 +61,6 @@ The output displays GitHub as one of the configured Git providers with your GitH
6161
GitHub jasonrandrews jasonrandrews
6262
```
6363

64-
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.
64+
You have now successfully configured GitHub as a Git provider for Daytona.
65+
66+
You can now use Daytona to manage your code repositories hosted on GitHub.

content/learning-paths/cross-platform/daytona/install.md

Lines changed: 20 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,26 @@ layout: "learningpathall"
77

88
## How do I install Daytona on Arm computers?
99

10-
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.
10+
Installing Daytona on Arm-based computers is easy.
1111

12-
Below are some recommended ways to install Daytona on a variety of operating systems.
12+
The application is a single binary which you can place anywhere.
13+
14+
To make it easy to run, you can add the location of the `daytona` binary to your search path.
15+
16+
You can install Daytona on a variety of operating systems, and these are described below.
1317

1418
### How do I install Daytona on macOS?
1519

20+
Use the following code:
21+
1622
```console
1723
curl -sf -L https://download.daytona.io/daytona/install.sh | sudo bash
1824
```
1925

2026
### How do I install Daytona on Arm Linux or Chrome OS?
2127

28+
Use the following code:
29+
2230
```console
2331
curl -sf -L https://download.daytona.io/daytona/install.sh | sudo bash
2432
```
@@ -36,9 +44,9 @@ $env:Path += ";" + $Env:APPDATA + "\bin\daytona"; [Environment]::SetEnvironmentV
3644

3745
You can also manually download the binary for a particular operating system and place it on your computer.
3846

39-
Refer to the [Daytona documentation](https://www.daytona.io/docs/installation/installation/) for full details.
47+
See the [Daytona documentation](https://www.daytona.io/docs/installation/installation/) for further information.
4048

41-
## How do I confirm Daytona is installed?
49+
## How do I confirm that Daytona is installed?
4250

4351
Print the version to confirm Daytona works on your computer:
4452

@@ -57,12 +65,12 @@ Daytona version v0.50.0
5765
After installing Daytona, you need to start the Daytona server.
5866

5967
{{% notice Note %}}
60-
Always make sure Docker is running before using Daytona.
68+
Always make sure that Docker is running before using Daytona.
6169

62-
Even if you plan to develop on remote computers, you still need the server on your local machine.
70+
Even if you plan to develop on remote computers, you will still need to have the server on your local machine.
6371
{{% /notice %}}
6472

65-
There are 3 options you can use to start the Daytona server.
73+
There are three options that you can use to start the Daytona server.
6674

6775
Option 1: start the server in the background with a confirmation prompt:
6876

@@ -118,13 +126,13 @@ INFO[0013] API REQUEST URI=/health/ latency=1.
118126
You may now begin developing
119127
```
120128

121-
If you are curious, leave the Daytona server running in the terminal and see the activity as you manage development environments.
129+
If you are curious, leave the Daytona server running in the terminal and watch the activity as you manage development environments.
122130

123131
## How do I stop the Daytona server?
124132

125-
If the server is running in the terminal, use Control-C to stop it.
133+
If the server is running in the terminal, you can stop it by using Control-C.
126134

127-
If the server is running in the background, use the command below to stop it:
135+
If the server is running in the background, you can use the command below to stop it:
128136

129137
```console
130138
daytona server stop
@@ -139,7 +147,7 @@ daytona purge
139147
```
140148

141149
{{% notice Note %}}
142-
If you have any trouble with Daytona on macOS, remove the directory `$HOME/Library/Application\ Support/daytona`
150+
If you experience difficulties with running Daytona on macOS, remove the directory `$HOME/Library/Application\ Support/daytona`
143151
{{% /notice %}}
144152

145-
With Daytona installed and the server running, you are ready to continue configuring Daytona.
153+
With Daytona installed and the server running, you are now ready to learn about configuring Daytona.

content/learning-paths/cross-platform/daytona/intro.md

Lines changed: 21 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -5,40 +5,46 @@ weight: 2
55
layout: "learningpathall"
66
---
77

8-
[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.
8+
## Development Environment Manager
9+
10+
[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.
911

1012
Daytona is based on dev containers, which provide isolated and reproducible development environments.
1113

12-
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.
14+
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.
15+
16+
For more information about dev containers, see the following resources:
17+
- [Introduction to Dev Containers](https://code.visualstudio.com/docs/remote/containers/).
18+
- [Development Containers Specification and dev container resources](https://github.com/devcontainers/).
1319

14-
For more information about dev containers, you can refer to the following resources:
15-
- [Introduction to Dev Containers](https://code.visualstudio.com/docs/remote/containers/)
16-
- [Development Containers Specification and dev container resources](https://github.com/devcontainers/)
20+
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.
1721

18-
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.
22+
You can use Daytona to create development environments on the following setups:
1923

20-
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.
24+
* On a local computer.
25+
* On remote computers running on your local network.
26+
* On remote computers from cloud service providers such as AWS and Azure.
2127

2228
## Daytona terminology
2329

24-
Understanding basic Daytona definitions makes it easier to get started.
30+
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.
2531

26-
### What are Git providers?
32+
#### Git Providers
2733

2834
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.
2935

30-
### What are providers?
36+
#### Providers
3137

32-
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.
38+
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.
3339

34-
### What are targets?
40+
#### Targets
3541

3642
A target in Daytona is the specific configuration of the development environment, including the provider, operating system, CPU and memory resources, and development tools.
3743

38-
The combination of a code repository from a Git provider and a target from a provider bring a development environment to life.
44+
The combination of a code repository from a Git provider, and a target from a provider, bring a development environment to life.
3945

4046
## Before you begin
4147

42-
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.
48+
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.
4349

44-
Next, learn how to install and configure Daytona.
50+
In the next section, you can learn how to install and configure Daytona.

content/learning-paths/cross-platform/daytona/local-dev.md

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,11 @@ weight: 6
55
layout: "learningpathall"
66
---
77

8-
Daytona makes it easy to manage local development environments. Follow these steps to learn how to create and manage an example local development environment.
8+
Daytona makes it easy to manage local development environments.
99

10-
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.
10+
Follow these steps to learn how to create and manage an example local development environment.
11+
12+
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.
1113

1214
Visit the [GitHub repository](https://github.com/microsoft/vscode-remote-try-python) to review the project.
1315

@@ -27,7 +29,7 @@ The workspace is created without starting any IDE. More information about how to
2729

2830
### Option 2: use a repository from your GitHub account
2931

30-
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.
32+
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.
3133

3234
The template option creates a new repository in your account. Putting the repository in your account allows you to commit changes back to GitHub.
3335

@@ -37,22 +39,22 @@ daytona create --no-ide
3739

3840
You will go through a series of prompts including:
3941

40-
- Select a GitHub provider
41-
- Find the repository in your GitHub account
42+
- Select a GitHub provider.
43+
- Find the repository in your GitHub account.
4244

4345
{{% notice Note %}}
4446
Use the / command to find the repo if you have many repositories in your GitHub account.
4547
{{% /notice %}}
4648

47-
- Select a branch
48-
- Specify a workspace name
49-
- Select the local (default) target using the Docker provider
49+
- Select a branch.
50+
- Specify a workspace name.
51+
- Select the local (default) target using the Docker provider.
5052

5153
The sequence is shown below:
5254

5355
![Create workspace #center](_images/local.gif)
5456

55-
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.
57+
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.
5658

5759
## Connect to the workspace
5860

@@ -102,28 +104,28 @@ Any of these options can be used to connect to a Daytona workspace.
102104

103105
A number of other IDEs can be used with Daytona. Refer to the [IDE documentation](https://www.daytona.io/docs/usage/ide/) for details.
104106

105-
## Start the flask application
107+
## Start the Flask application
106108

107-
To start the flask application run:
109+
To start the Flask application, run:
108110

109111
```console
110112
python -m flask run --port 9000 --no-debugger --no-reload
111113
```
112114

113115
If you start Python in VS Code, it will automatically forward port 9000 and open a browser tab to see the web page.
114116

115-
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:
117+
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:
116118

117119
```console
118120
daytona forward 9000 vscode-remote-try-python
119121
```
120122

121-
## Other workspace commands
123+
## Useful workspace commands
122124

123-
Now that you can create a workspace and connect to it, there are some other commands to be aware of.
125+
Now that you can create a workspace and connect to it, there are some other commands that you will find useful.
124126

125127

126-
Use the stop command to step the workspace. The dev container will stop on your local computer.
128+
Use the stop command to stop the workspace. The dev container will stop on your local computer:
127129

128130
```console
129131
daytona stop
@@ -143,6 +145,6 @@ daytona delete
143145

144146
The container is removed from the system.
145147

146-
You now understand the basic commands to manage local development environments with Daytona.
148+
You have now learned the basic commands to manage local development environments with Daytona.
147149

148-
Next, you can learn how to manage remote development environments.
150+
You can now move on to learn how to manage remote development environments.

content/learning-paths/cross-platform/daytona/providers.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,19 @@ layout: "learningpathall"
77

88
---
99

10-
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.
10+
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.
1111

12-
To add providers run:
12+
To add providers, run:
1313

1414
```console
1515
daytona provider install
1616
```
1717

1818
Docker is already installed.
1919

20-
Select the providers you want to install using the arrow keys to select a provider.
20+
Select the providers you want to install using the arrow keys.
2121

22-
Select No when asked about creating a target. You can enter the details later when a new target is created.
22+
Select **No** when you are asked about creating a target. You can enter the details later when a new target is created.
2323

2424
To verify providers are installed, run the following command:
2525

0 commit comments

Comments
 (0)