Update documentation for clarity and consistency
All checks were successful
Build and Deploy Hugo / Deploy Hugo Website (pull_request) Successful in 24s
All checks were successful
Build and Deploy Hugo / Deploy Hugo Website (pull_request) Successful in 24s
Remove emojis and em dash separators Simplify introductory sentences Standardize section headings
This commit is contained in:
@@ -11,13 +11,13 @@ cascade:
|
||||
- [DevPod](https://devpod.sh/docs/what-is-devpod) ⚙️
|
||||
- [DevContainer](https://containers.dev) 🐳
|
||||
|
||||
## Introduction 🚀
|
||||
## Introduction
|
||||
|
||||
In this article, I want to introduce a fantastic tool that belongs to the same family as GitPod and Codespaces: **DevPod**! It lets you create development environments effortlessly — without getting locked in to a single provider. 🔒❌
|
||||
|
||||
DevPod is based on the **DevContainer** architecture and uses the specifications contained in a [devcontainer.json](https://containers.dev) file to launch your development environment. Personally, I use it to quickly deploy network mockups with ContainerLab. 💻🧰
|
||||
|
||||
## What is a DevContainer? 🤔
|
||||
## What is a DevContainer?
|
||||
|
||||
A development container (often called a "dev container") lets you use a container as a full-fledged development environment. (Check out the official [containers.dev](https://containers.dev) documentation for more details.)
|
||||
|
||||
@@ -56,13 +56,13 @@ The cornerstone of the DevContainer is the `devcontainer.json` file. For example
|
||||
DevContainers are great for local development, but sometimes you need more power — maybe your workloads are huge, or you want to run specialized labs. That's where **DevPod** comes in. 💪
|
||||
**So you can easily deploy labs to the Cloud**
|
||||
|
||||
## What is DevPod? 🤖
|
||||
## What is DevPod?
|
||||
|
||||
**DevPod** is an open-source tool that lets you launch development environments either on your local machine or in the cloud provider of your choice. Think of it as a self-hosted, highly customizable version of GitHub Codespaces. 🎉
|
||||
|
||||
In my day-to-day networking adventures, I deploy ContainerLab-based setups with DevContainers on AWS. Let's see how you can use DevPod to do exactly that (details on ContainerLab will follow in another article, I promise!). 😜
|
||||
|
||||
## AWS Provider 🌐
|
||||
## AWS provider
|
||||
|
||||
DevPod uses **Providers**, which are configuration modules that define where and how DevPod launches your environment. Here's the list of providers:
|
||||
|
||||
@@ -74,7 +74,7 @@ We're going to focus on the **AWS Provider** — even though there are plenty of
|
||||
|
||||
Before you panic at all these settings, don't worry. If you're just doing a bit of experimenting, the default values will usually do the job. 🙌
|
||||
|
||||
> [!NOTE] **The perks of open source** 🎁
|
||||
> [!NOTE] **The perks of open source**
|
||||
>
|
||||
> The fact that DevPod is open-source means you can peek under the hood to see exactly how it works. Check out the AWS code [here](https://github.com/loft-sh/devpod-provider-aws/tree/main) if you're curious.
|
||||
|
||||
@@ -136,7 +136,7 @@ You'll need to create an IAM user and attach an IAM policy to it that grants jus
|
||||
- **Route 53 (optional):**
|
||||
- `route53:ListHostedZones`, `route53:GetHostedZone`, `route53:ChangeResourceRecordSets`
|
||||
|
||||
## AWS Configuration 🏗️
|
||||
## AWS configuration
|
||||
|
||||
I usually use the AWS web console to set this up, but you can absolutely do it via the CLI too.
|
||||
|
||||
@@ -249,7 +249,7 @@ Go back to **Users** → **devpod-tool-user** → **Permissions** to confirm tha
|
||||
|
||||
**Bonus**: Note your **VPC ID** (in the VPC section on AWS). You'll need it when configuring DevPod.
|
||||
|
||||
## Configuring DevPod 🛠️
|
||||
## Configuring DevPod
|
||||
|
||||
### 1. Configure the AWS profile
|
||||
|
||||
@@ -279,7 +279,7 @@ Click **Add Provider**.
|
||||
|
||||

|
||||
|
||||
## Testing a deployment 🧪
|
||||
## Testing a deployment
|
||||
|
||||
### Deploy
|
||||
|
||||
@@ -310,8 +310,8 @@ Deleting the workspace removes all AWS resources associated with that environmen
|
||||
|
||||

|
||||
|
||||
## Conclusion 💡
|
||||
## Conclusion
|
||||
|
||||
By combining **DevContainers** and **DevPod** on **AWS**, you can build flexible, self-managed development environments that scale with your needs — without being locked into vendor-specific platforms. Say goodbye to "It works on my machine!" issues and hello to frictionless coding. 🚀✨
|
||||
By combining **DevContainers** and **DevPod** on **AWS**, you can build flexible, self-managed development environments that scale with your needs, without being locked into vendor-specific platforms. Say goodbye to "It works on my machine!" issues and hello to frictionless coding.
|
||||
|
||||
Have fun! 🎉
|
||||
Have fun!
|
||||
|
||||
Reference in New Issue
Block a user