-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building a DuckDB Playground with Daytona #57
Comments
/bounty $100 |
💎 $100 bounty • DaytonaSteps to solve:
If no one is assigned to the issue, feel free to tackle it, without confirmation from us, after registering your attempt. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code. Please respect others by working on PRs that you are allowed to submit attempts to. e.g. If you reached the limit of active attempts, please wait for the ability to do so before submitting a new PR. If you can not submit an attempt, you will not receive your payout. Thank you for contributing to daytonaio/content! Add a bounty • Share on socials
|
/attempt #57
|
/attempt #57
|
💡 @onyedikachi-david submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
/attempt #57 Options |
Content Type
Guide
Article Description
This guide will walk developers through setting up a DuckDB playground environment using Python, Daytona and DevContainers. We'll cover:
The focus will be on creating a hands-on environment to experiment with DuckDB's capabilities.
Target Audience
References/Resources
Examples
Special Instructions
Create a new GitHub repository named "playground-duckdb"
Provide step-by-step instructions in the guide on how to:
The text was updated successfully, but these errors were encountered: