Example project to showcase how to use dev env vars in Daytona

[bellatrick]

/claim #29

Loom Link

Writer's Checklist

Writing Structure

• Use short sentences and paragraphs, and include bucket brigades.
• Include more than two descriptive H2 headings to organize content.
• Capitalize headings according to the AP Stylebook (use this tool)
• Include an introduction with at least two paragraphs before the first H2 section.
• Use appropriate formatting (bold, italic, underline), notes, quotes, TLDRs, and key points.
• Incorporate code elements and Markdown format where appropriate.
• Ensure at least one visual element per “screen” of the article (screenshots, diagrams, tables, graphs, lists, sidenotes, blockquotes).

Fact-Checking

• Verify all facts and data points included in the article.

Asset Management

• Save images in the /assets folder.
• Follow naming conventions: YYYYMMDD_title_of_the_article_IMG_NAME_NO.png.
• (Optional) Create a GitHub repo for the code referenced in the article and share it.
• (Optional) Include a link to this Loom video in the PR comments.

Interlinking

• Use CTRL+F to search for relevant keywords in:
  • Daytona Dotfiles Sitemap
  • Daytona Definitions Sitemap
• Interlink keywords using the appropriate URLs.

Glossary/Definitions

• Create new definition in /defitnitions folder.

Review and Edit

• Ensure articles address the needs of the target audience and their search intent.
• Read the article out loud to catch any awkward phrasing.
• Run the draft through Grammarly or a similar grammar tool.
• Double-check adherence to the style guide and repository guidelines.
• Use the name of the article for the title of the PR.

[bellatrick]

Hey! @mojafa, this PR is ready for review.

[mojafa]

@bellatrick I wonder why you didn't check this, yet you have it:

• (Optional) Create a GitHub repo for the code referenced in the article and share it.

[mojafa]

Also see the spelling here:

It's Dev Container

[bellatrick]

@bellatrick I wonder why you didn't check this, yet you have it:

• (Optional) Create a GitHub repo for the code referenced in the article and share it.

I didn't explicitly mention the branch with env_demo.py because I linked to the main branch for readers to pull the initial code. Since the remaining code is just one file with a few lines, I felt it was unnecessary to include a separate branch link at the end of the article.

[bellatrick]

Also see the spelling here:

It's Dev Container

Oh okay, got it!

[mojafa]

@bellatrick I wanted to let you know that I've just pushed some changes to the main branch that fix some linting issues and update the compliance rules. These updates should help you pass the content compliance checks in your current pull request.

When you get a chance, please pull the latest changes from the main branch into your working branch. This should make the integration smoother and help avoid any potential conflicts.

[mojafa]

@bellatrick please update the command daytona create --code to daytona create [repo_url] in this case https://github.com/bellatrick/python_starter.git
Like this

code examples work otherwise,

[bellatrick]

@bellatrick please update the command daytona create --code to daytona create [repo_url] in this case https://github.com/bellatrick/python_starter.git Like this

code examples work otherwise,

Alright got it!

[bellatrick]

@bellatrick I wanted to let you know that I've just pushed some changes to the main branch that fix some linting issues and update the compliance rules. These updates should help you pass the content compliance checks in your current pull request.

When you get a chance, please pull the latest changes from the main branch into your working branch. This should make the integration smoother and help avoid any potential conflicts.

Thanks! Will do that.