# Setting up CI/CD with Drone
### Follow these steps to set up CI/CD using Drone along with Gitea:

- Start by setting up a Docker container for Drone with Gitea integration. You can refer to this tutorial: Drone and Gitea Integration.
- There's a Docker Compose project for Drone and Gitea on our work server located at: {fill this path with the correct value}.
- Next, you need to configure a runner for your CI/CD setup.
- In my case, I opted for the "exec runner" instead of the "docker runner." This choice is due to our use of a dockerized CoreBOS environment for running tests. CoreBOS is part of a docker-compose project with multiple containers. Running them inside another Docker container is not feasible. The "exec runner" solves this by executing code directly on the server where it's running. This gives us a traditional Linux environment capable of running dockerized CoreBOS.
- The "exec runner" operates as a service on Linux. It continuously checks the Drone server for new builds to execute and follows the commands specified in the .drone.yml file.
- To install the "exec runner," consult the installation guide available here: Installing the Exec Runner.
- After installing the service and configuring it, verify its setup by checking the logs. Ensure that the "exec runner service" is properly connected to the Drone server.
- Access the web application exposed by Drone. In this case, it should be available at: http://code.spike.studio:3001/.
- Sign in using your Gitea credentials to create a new Drone account.
- Locate the repository for which you want to enable CI/CD. Click on the repository and activate CI/CD by clicking the respective button. Make sure you have the necessary write permissions for the repository, as Drone will attempt to add a webhook through your account.
- At this point, you should be all set to run builds based on your .drone.yml configuration for the selected repository.