Skip to content

Releases: daytonaio/daytona

v0.52.0-alpha.1

17 Jan 15:37
c213b32
Compare
Choose a tag to compare
v0.52.0-alpha.1 Pre-release
Pre-release

Workspace Management Rework

TL;DR

  • Targets now have state (e.g. Daytona is aware of the state of the EC2 instance used by the AWS provider)
  • Workspaces can be created/deleted on running targets (e.g. No more need to create an EC2 instance for every workspace. Keep one running and add workspaces to it)
  • Remote runners can offload jobs to remote machines
  • Use workspace labels to group workspaces and filter them with daytona ls --label
  • If you want to help us test this major update, jump straight into the How to test section below

Description

Projects have been renamed to Workspaces.
Workspaces have been renamed to Targets
Targets have been renamed to Target Configs.

Project configs have also been renamed to Templates; e.g. daytona template list

Workspaces have been "detached" from targets - they can now be created inside and deleted from targets removing the
need to provision a new target whenever creating a workspace.

Resource state management issues have been resolved - new resource states regarding starting/stopping/deleting workspaces or e.g. running builds are introduced.

Issues for a "remote provisioner" and "remote image builder" have been solved by introducing Runners - a standalone mode/component in charge of asynchronously fetching and running workspace/target/build creation and other processes.
This allows users to e.g. create a remote VM, install Daytona and connect it to the existing Daytona Server to create workspaces. Local provisioning/building is managed by the Local Runner which can be disabled through the Daytona
Server configuration.

Runners are responsible for managing providers and each one has its own set of providers. When creating target configs, users are prompted to choose a runner to link it to.

Introduced Workspace Labels allowing workspaces to be grouped and filtered by user-defined text fields.

It is now possible to SSH into targets and use the Daytona binary inside of them to view info and read logs.

Container registries are no longer managed through a CLI command and are now managed by environment variables instead

Purging Daytona now delegates removal of Resources (workspaces, targets, builds) to the user because they are now treated independently.

Telemetry has been updated/improved to match the changes.

CLI commands arguments and aliases have been made to be more consistent.

README.md has been redone to adhere to the changes and trimmed of a large amount of the content.

How to test?

To start, you will need to remove the entire Daytona configuration from your system with daytona purge or:

Linux:

rm -rf ~/.config/daytona

Mac:

rm -rf ~/Library/Application\ Support/daytona

Windows (PowerShell):

Remove-Item -Recurse -Force "C:\Users\<USERNAME>\AppData\Roaming\daytona"

Next, you can update to this version of Daytona by running:

curl -sfL get.daytona.io | DAYTONA_SERVER_VERSION=v0.52.0-alpha.1 sudo -E bash

To start the server for the first time, please use this command:

DEFAULT_REGISTRY_URL=https://download.daytona.io/daytona-providers-pre-release daytona server -y

** You can skip the DEFAULT_REGISTRY_URL on subsequent starts. It's only important to set it for the first time

Available providers to test with this release are:

  • Docker
  • AWS
  • DigitalOcean

Installing other providers will cause the server to malfunction at the moment. We are working on updating the rest of them.

If you want to test remote runners, run:

daytona server runner create

You will get a command that you can run to configure and start a remote runner.

When reporting issues, please make sure to mention the version in the description.

Full Changelog: v0.51.0...v0.52.0-alpha.1

v0.51.0

10 Jan 13:31
f9ece40
Compare
Choose a tag to compare

What's Changed

Features

Fixes

Samples

Read more

v0.50.0

20 Dec 14:34
844454c
Compare
Choose a tag to compare

What's Changed

Features

Fixes

Providers

Providers will require an update because of #1428. Make sure to update all of them with daytona provider update --all.

Samples

New Contributors

Full Changelog: v0.49.0...v0.50.0

v0.49.0

13 Dec 14:42
d2cd518
Compare
Choose a tag to compare

What's Changed

Features

Fixes

Chores and tests

  • chore(deps): bump golang.org/x/crypto from 0.26.0 to 0.31.0 by @dependabot in #1452
  • docs: expanded the contributing to Daytona section on README file by @mojafa in #1414

Workspace Toolbox API (#1455)

Workspace Toolbox API is a new feature that allows interaction with the workspace agent using Rest API calls.
The Toolbox provides FileSystem, Git, LSP, and Process operations.

This features requires users all providers to be updated daytona provider update --all.

You can interact with the Toolbox API using the Daytona Server builtin swagger editor on: localhost:3986/swagger/index.html.

Tip

Make sure to authorize yourself by setting Bearer <API_KEY> in the Authentication tab.
You can grab your API key with daytona config -k

Screenshot 2024-12-13 at 15 41 24

Samples

New Contributors

Full Changelog: v0.48.0...v0.49.0

v0.48.0

06 Dec 14:14
785302a
Compare
Choose a tag to compare

What's Changed

Features

Fixes

Chores and tests

  • chore(deps): bump github.com/quic-go/quic-go from 0.42.0 to 0.48.2 by @dependabot in #1407

Providers

Because of #1426, all providers will need to be updated with daytona provider update --all.

New Contributors

Full Changelog: v0.47.0...v0.48.0

v0.47.0

29 Nov 15:21
128daa5
Compare
Choose a tag to compare

What's Changed

Features

Fixes

Providers

Because of #1393, #1394 and #1395, providers will need to be updated with daytona provider update --all.

Full Changelog: v0.46.1...v0.47.0

v0.46.1

26 Nov 14:38
2966736
Compare
Choose a tag to compare

What's Changed

Fixes

Telemetry

  • telemetry: disable telemetry on server daemon command by @Tpuljak in #1374

Providers

Because of #1365 and #1372, users should update all providers with daytona provider update --all.

Full Changelog: v0.46.0...v0.46.1

v0.46.0

22 Nov 12:14
ea2db7f
Compare
Choose a tag to compare

What's Changed

Features

Fixes

  • fix: working dir for running devcontainer initialize command by @Tpuljak in #1356
  • fix: handle multiple compose files in devcontainers by @Tpuljak in #1349

Telemetry

Chores and tests

Breaking changes

#1300

Before running the Server again, all providers will need to be removed by running the following command:

Linux:

rm -rf ~/.config/daytona/providers/*-provider/*-provider

Mac:

rm -rf ~/Library/Application\ Support/daytona/providers/*-provider/*-provider

Windows (PowerShell):

Remove-Item -Recurse -Force "C:\Users\<USERNAME>\AppData\Roaming\daytona\providers\*-provider\*-provider.exe"

After updating and starting the server. You can reinstall your providers with daytona provider install

Full Changelog: v0.45.0...v0.46.0

v0.45.0

15 Nov 14:33
59fa89a
Compare
Choose a tag to compare

What's Changed

Features

Fixes

  • Fix: Randomization of Daytona Provider Install by @unsuman in #1336

Full Changelog: v0.44.1...v0.45.0

v0.44.1

12 Nov 13:28
75cf898
Compare
Choose a tag to compare

What's Changed

Fixes

Providers

All providers received an update to the latest version of Daytona. You can update all providers with daytona provider update --all.

Full Changelog: v0.44.0...v0.44.1