daytonaio/installer

Demo Version of Daytona Enterprise that runs on a Single-Node.

Daytona Enterprise Demo

Try out a demo version of Daytona Enterprise on a single-node.

Report Bug · Request Feature · Join Our Slack · Twitter

---

What is the Daytona Enterprise Demo?

The Daytona Enterprise Demo is a resource limited, single-node deployment of Daytona's enterprise offering. This allows you to experience the capabilities of Daytona Enterprise, demonstrating how it can streamline Development Environment Management (DEM) within your organization.

Important

The information in this repository does not apply to the Daytona open source project. Please refer to daytonaio/daytona for information on setting up the Daytona open source project.

Getting Started

Requirements

• An x86_64 Linux host operating system with minimum specs:
  • 4-core CPU
  • 16GB RAM
  • 200GB disk
• Accessible TCP ports 80, 443, and 30000
• A registered domain with the following DNS records:
  • <domain> IN A host.ip
  • *.<domain> IN A host.ip
• An OAuth application with a supported identity provider (GitHub, GitLab, Bitbucket) configured with the following values:
  • Homepage URL: https://<domain>
  • Authorization callback URL: https://id.<domain>

Note

The deployment script has been officially tested with Ubuntu 22.04, Ubuntu 23.04, and Debian 12.

If you need access to the Kubernetes cluster, ensure TCP port 6443 is open.

Tip

For information on setting up an OAuth application, visit the corresponding documentation for your provider:

• GitHub OAuth documentation
• GitLab OAuth documentation
• Bitbucket OAuth documentation

Guided Deployment

You can deploy Daytona Enterprise Demo using the guided method. This method will prompt you for all the information required to set up Daytona Enterprise Demo on your host machine, subsequently deploying the components required.

1. Clone this repository to the host machine and run the setup script:

   git clone https://github.com/daytonaio/enterprise-demo
   cd enterprise-demo
   ./setup.sh

2. When prompted, enter the following information:
   1. App hostname (FQDN): The registered domain (<domain>)
   2. Identity provider (IdP): Your chosen identity provider
   3. IdP Client ID: The client ID associated with your OAuth application
   4. IdP Client Secret: The client secret associated with your OAuth application
3. Enter any additional information prompted for based on your selection of identity provider.
4. Follow the instructions output by the script to configure required DNS records.

Using Environment Variables

You can use environment variables to configure the deployment script at run time. This allows you to skip the prompts in the Guided deployment procedure.

1. Clone this repository to the host machine:

   git clone https://github.com/daytonaio/enterprise-demo
   cd enterprise-demo

2. Set the appropriate environment variables for your identity provider in your shell, with reference to the Environment Variable Reference table.

3. Run ./setup.sh with the environment variables set to start the deployment.

   Example:

   URL="daytona.example.com" IDP="github" IDP_ID="changeme" IDP_SECRET="changeme" ./setup.sh

4. Follow the instructions output by the script to configure required DNS records.

Updating

You can update an existing deployment of Daytona Enterprise Demo.

1. In your clone of this repository, execute the following to incorporate the latest updates:

   git pull origin
   

2. Follow either the Guided Deployment or Using Environment Variables procedure using the same variables.

Removing/Uninstalling

You can remove a deployed version of Daytona Enterprise Demo from the host machine. This procedure allows you to redeploy the demo from scratch using the Guided Deployment or Using Environment Variables procedure. It's also useful to reset your host machine to it's previous state before deployment.

• In your clone of this repository, run:

  ./setup.sh --remove

Environment Variable Reference

Environment variable	Required?	Description
URL	Yes	The domain name (<domain>) used to access Daytona.
IDP	Yes	One of github, gitlab, bitbucket, gitlabSelfManaged, githubEnterpriseServer.
IDP_ID	Yes	Client ID from by the provider's OAuth application.
IDP_SECRET	Yes	Client secret from the provider's OAuth application.
IDP_URL	Only for IdPs gitlabSelfManaged or gitHubEnterpriseServer	Base URL for your hosted Git provider.
IDP_API_URL	Only for IdP githubEnterpriseServer	API base URL for your GitHub Enterprise Server.

Contributing

Daytona is licensed under the Elastic License 2.0. If you would like to contribute to the software, you must:

1. Read the Developer Certificate of Origin Version 1.1 (https://developercertificate.org/)
2. Sign all commits to the Daytona project.

This ensures that users, distributors, and other contributors can rely on all the software related to Daytona being contributed under the terms of the License. No contributions will be accepted without following this process.

License

This repository contains the Daytona Enterprise Demo installer, covered under the Elastic License 2.0, except where noted (any Daytona logos or trademarks are not covered under the Elastic License, and should be explicitly noted by a LICENSE file.)

Others are allowed to make their own distribution of the software in this repository under the license, but they cannot use any of the Daytona trademarks, cloud services, etc.

We explicitly grant permission for you to make a build that includes our trademarks while developing Daytona itself. You may not publish or share the build, and you may not use that build to run Daytona for any other purpose.

Code of Conduct

This project has adapted the Code of Conduct from the Contributor Covenant. For more information see the Code of Conduct or contact [email protected]. with any additional questions or comments.

Questions

For more information on how to use and develop Daytona, talk to us on Slack.

installer's Issues

DigitalOcean install stuck

I followed https://www.daytona.io/dotfiles/install-daytona-on-digitalocean-in-minutes

...
ℹ Installing watkins helm chart...
Pulled: ghcr.io/daytonaio/charts/watkins:2.91.2
Digest: sha256:5c41f1395727e76f66fa298892d46787c280963da3fedc656c4adbe45a3e6e3d
coalesce.go:237: warning: skipped value for keycloak.configuration: Not a table.
coalesce.go:289: warning: destination for keycloak.postgresql.networkPolicy.egressRules.customRules is a table. Ignoring non-table value ([])
coalesce.go:289: warning: destination for keycloak.postgresql.networkPolicy.ingressRules.readReplicasAccessOnlyFrom.customRules is a table. Ignoring non-table value ([])
coalesce.go:289: warning: destination for keycloak.postgresql.networkPolicy.ingressRules.primaryAccessOnlyFrom.customRules is a table. Ignoring non-table value ([])
coalesce.go:237: warning: skipped value for rabbitmq.configuration: Not a table.
W0306 20:33:03.860171   16773 warnings.go:70] metadata.name: this is used in Pod names and hostnames, which can result in surprising behavior; a DNS label is recommended: [must not contain dots]

I tried to insert a label, but nothing happened.

Can't install this for the life of me...

Hi,

I'd really like to try out Daytona but I've spent the last few hours tearing my hair out as I can't get passed this setup.sh script. I created a GitHub Oauth Application with Client ID and Secret. I also have correctly configured a subdomain on one of domains to be provisioned for Daytona and I get passed the certificate checking and TXT record verification fine. Where it fails is the Installing ingress-nginx helm chart step. It hangs on that task for 5-10mins and then throws the following error: Error: release ingress-nginx failed, and has been uninstalled due to atomic being set: failed pre-install: 1 error occurred: * timed out waiting for the condition

Full output:

Enter app hostname (valid domain) [FQDN]: daytona.<REDACTED>.com
Identity Providers (IdP) available [IDP]: 
1) github
2) gitlab
3) bitbucket
4) gitlabSelfManaged
5) githubEnterpriseServer
Choose an IdP (type the number and press Enter): 1
Enter IdP Client ID [IDP_ID]: <REDACTED>
Enter IdP Client Secret [IDP_SECRET] (input hidden): ✔ All required variables set.
ℹ Checking wildcard certificate...
✔ Certificate valid and matching daytona.<REDACTED>.com and *.daytona.<REDACTED>.com domains
✔ k3s is installed and running.
✔ iSCSI installed.
✔ iscsid service is active.
✔ Multipathd service not found or not running.
ℹ Installing longhorn helm chart
✔ The release 'longhorn' is deployed.
ℹ Installing ingress-nginx helm chart
Error: release ingress-nginx failed, and has been uninstalled due to atomic being set: failed pre-install: 1 error occurred:
	* timed out waiting for the condition

Any help would be greatly appreciated. After each failure I've also made sure to run the sudo ./setup.sh --remove command to clean up. I really have no idea what the issue is and it's annoying as it's preventing me from trying Daytona..

Stuck in initial setup during invited test

Own assumptions for testing: "I have never used Daytona and my only knowledge is that I have the requirements detailed in the README.md so I can plug&play-start via the daytonaio/installer"

Stuck here: https://github.com/daytonaio/installer/blob/main/setup.sh#L413

IdP has correctly been configured in before and letsencrypt was successful. Looping at

Waiting for k3s to be ready...

Aborting proceeds with the final print out

✘ The release watkins is not deployed. Please repeat installation script. Exiting...

Error: Kubernetes cluster unreachable: Get "http://localhost:8080/version": dial tcp 127.0.0.1:8080: connect: connection refused

Installation of k3s did not configure correctly, I guess. Manually executing k3s kubectl get nodes results in the folllowing which hints to the error in the setup script:

E0120 17:35:19.383542      46 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?

k3s config is correctly written with the defined values of the setup script in before, verified with:

cat /etc/rancher/k3s/config.yaml

Stuck in the installation

Describe the bug
I'm trying to install Daytona following the documentation (setup.sh), and the process fails at a certain point of the installation.

To Reproduce
Steps to reproduce the behavior:

1. Install Docker on S.O.
2. Download the repo
3. Go to installer directory
4. Run setup.sh
5. Complete the requested steps.
6. Failure in the part "Installing longhorn helm chart"

Expected behavior
Successful installation.

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu 22.04.4 LTS
• Browser: NA
• Daytona Version: 8.86.0

Additional context
I'm using a machine on AWS EC2 and I have the required ports enabled so that it can be accessed by everyone (testing).

There are anyway to manage daytona?

i can only login keycloak via admin. there any way to manage daytona by admin?
i createed a workspace, and delete the user, and rejoin, and recreate workspace then can't create workspace.
I would like to delete every things related the deleted user by admin.

There are any admin page for daytona? not a keycloak.

Selfhosted in a home lab

Hello!

I want to install daytona on my homelab but I am confused if it's only for enterprise only.
So will I be able to install or no?

Thanks you

404 Error

Hey There!

I installed daytona using the script and it gives me 2 links, I open them both to receive a no ssl warning and a 404 page not found.
Not sure what's going on.

This is still running as well, so maybe I have to wait for it.