mirror of https://github.com/twentyhq/twenty.git synced 2024-12-23 12:02:10 +03:00

History

Félix Malfait c90d2fd5cc Change default behavior of ENABLE DB MIGRATION (#9077 ) See: https://github.com/twentyhq/twenty/issues/9031#issuecomment-2542015975 I think it would be easier if the default behavior for the container was to run the migration, and setting the environment variable would be used to disable it (e.g. on the worker). Long-term goal is for the default setup to work out of the box with ~2 env variables only (database url, redis url) I don't think there's a big risk if people forget to turn it off on the worker?		2024-12-16 17:31:45 +01:00
..
manifests	Change default behavior of ENABLE DB MIGRATION (#9077 )	2024-12-16 17:31:45 +01:00
terraform	Change default behavior of ENABLE DB MIGRATION (#9077 )	2024-12-16 17:31:45 +01:00
README.md	Support for Kubernetes via Terraform and Manifests (#5721 )	2024-07-10 13:54:27 +02:00

README.md

README

Overview

This repository contains Kubernetes manifests and Terraform files to help you deploy and manage the TwentyCRM application. The files are located in the packages/twenty-docker/k8s directory.

Prerequisites

Before using these files, ensure you have the following installed and configured on your system:

Kubernetes cluster (e.g., Minikube, EKS, GKE)
kubectl
Terraform
Docker

Setup Instructions

Step 1: Clone the Repository

Clone the repository to your local machine:

git clone https://github.com/twentyhq/twenty.git
cd twentycrm/packages/twenty-docker/k8s

Step 2: Customize the Manifests and Terraform Files

Important: These files require customization for your specific implementation. Update the placeholders and configurations according to your environment and requirements.

Step 3: Deploy with Terraform

Navigate to the Terraform directory:
```
cd terraform
```
Initialize Terraform:
```
terraform init
```
Plan the deployment:
```
terraform plan
```
Apply the deployment:
```
terraform apply
```

OR

Step 3: Deploy with Kubernetes Manifests

Navigate to the Kubernetes manifests directory:
```
cd ../k8s
```

Create Server Secret

kubectl create secret generic -n twentycrm tokens --from-literal accessToken=changeme --from-literal loginToken="changeme" --from-literal refreshToken="changeme" --from-literal fileToken="changeme"

Apply the manifests:
```
kubectl apply -f .
```

Customization

Kubernetes Manifests

Namespace: Update the namespace in the manifests as needed.
Resource Limits: Adjust the resource limits and requests according to your application's requirements.
Environment Variables: Configure server tokens in the Secret command above.

Terraform Files

Variables: Update the variables in the variables.tf file to match your environment.
Locals: Update the locals in the main.tf file to match your environment.
Providers: Ensure the provider configurations (e.g., AWS, GCP) are correct for your setup.
Resources: Modify the resource definitions as needed to fit your infrastructure.

Troubleshooting

Common Issues

Connectivity: Ensure your Kubernetes cluster is accessible and configured correctly.
Permissions: Verify that you have the necessary permissions to deploy resources in your cloud provider.
Resource Limits: Adjust resource limits if you encounter issues related to insufficient resources.

Logs and Debugging

Use kubectl logs to check the logs of your Kubernetes pods.
Use terraform show and terraform state to inspect your Terraform state and configurations.

Conclusion

This setup provides a basic structure for deploying the TwentyCRM application using Kubernetes and Terraform. Ensure you thoroughly customize the manifests and Terraform files to suit your specific needs. For any issues or questions, please refer to the official documentation of Kubernetes and Terraform or seek support from your cloud provider.

Feel free to contribute and improve this repository by submitting pull requests or opening issues. Happy deploying!