Community Hours #15: Key Workflow Enhancements

In this edition of Daytona Community Hours, we reviewed the latest updates from version 0.35.0 and a recent patch release, along with a glimpse of what’s ahead in our roadmap. We covered new features, important fixes, and a few breaking changes that enhance the overall user experience. 

Key Features in 0.35.0

Restart Workspace Command
A new Daytona Restart Workspace command allows you to restart a workspace with a single command, eliminating the need to manually stop and start Daytona.

Auto-Install Remote SSH Extension
For users working with VS Code, we now auto-install the Remote SSH extension if it’s missing. This saves you the hassle of installing it manually, keeping your workflow smooth.

Spinner for Tailscale Delays

When setting up a workspace, the Tailscale connection sometimes takes longer than expected. We now display a spinner to indicate progress, so you know it’s working behind the scenes.

Public by Default: Port Forwarding Workspace Mode

A significant change was made to the port-forwarding feature: now, when you run Daytona forward inside a project, the port forwards to our reverse proxy automatically, making it easier to share. Local forwarding has been removed, simplifying the process.

Spinner During Repo URL Validation

If you’ve ever experienced lag when validating a repo URL during project creation, we’ve added a spinner for real-time feedback.

Auto-Mark Git Repositories as Safe

Annoyed by constantly marking your Git repositories as safe? This is now automatic for Daytona projects.

Other fixes and improvements:

• Fixed a broken Code of Conduct link.

• Improved Bitbucket integration with multiple fixes.

• Updated dependencies for Headscale and FRP to ensure stability.

Telemetry and Breaking Changes

We’ve added telemetry to track command errors and flag usage (but don’t worry, no personal data is collected). There’s also a breaking change where the public flag for Daytona forward has been removed, as it’s now the default behavior.

Patch Release Highlights

In addition to the major release, we had a patch release that tackled a few minor issues:

• Version Flag Fix: A panic was triggered when using daytona --version. This has now been resolved.

• Correct Server Stopping on Uninstall: Daytona will now stop the server correctly during uninstallation.

• Proper Git Provider Handling: We’ve fixed an issue where the wrong Git provider could be selected when using similar repo names across platforms like GitHub and GitLab.

Roadmap: What’s Next?

We’re already working on version 0.36.0, with a few cool things in the pipeline:

• Daytona Logs Command: Soon, you’ll be able to retrieve logs for any workspace or project directly via the CLI, improving transparency and debugging.

• Commit Signing: For organizations that require it, we’re adding support for signing commits using SSH or GPG keys, streamlining compliance for developers.

• Smaller Quality-of-Life Improvements: Expect enhancements like a new alias for batch processing (DTN), and better purging of directories that were previously missed.

Conclusion

That’s it for this week! As always, if you have any questions, feel free to reach out via Slack, Twitter, LinkedIn, or wherever you can find us. We hope to see you at the next Daytona Office Hours for more updates!