QuaK IDE

About

This repository contains the source code for the Quantum Kit (QuaK) Web IDE.

Docker Workflows

Development Workflow (Docker-only)

This ensures a consistent environment and supports hot-reloading.

1. Start Backend & Database:

   • Linux/macOS:

     docker compose -f docker-compose.dev.yaml up --build

   • Windows:

     docker-compose -f docker-compose.dev.yaml up --build

   • Runs the Spring Boot backend on port 8080.

   • Runs MariaDB on port 3306.

   • Note: The backend does not serve frontend files in this mode.

2. Start Frontend: In a new terminal:

   cd frontend
   npm run dev

Hybrid Workflow (Debugger-Friendly)

Recommended for backend development. This allows you to run the backend in your IDE or via terminal with a debugger while using Docker for the database.

1. Start Database:

   docker-compose -f docker-compose.dev.yaml up -d database

2. Start Backend (with Debugging): You can run the backend in debug mode via terminal. It will listen on port 5005 for a debugger while the API remains on 8080.

   cd backend
   ./gradlew bootRun -PjvmArgs="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005"

   • Port 8080: Standard Web/API (Frontend stays connected).
   • Port 5005: Debugging (Connect your IDE here via "Remote JVM Debug").

3. Start Frontend:

   cd frontend
   npm run dev

Access the app at http://localhost:5173.

Production Workflow

To run the full application (Backend + Frontend served statically):

1. Start Application:

   docker compose -f docker-compose.prod.yaml up --build

   • Builds the frontend and serves it via the backend (or Nginx if configured).
   • Runs the Spring Boot backend and MariaDB.
   • Access the app at http://localhost:8080 (or the configured production port).

Developing

Please have a look at the developer guidelines.

Testing

Backend Tests

To run the backend tests, execute the following command in the backend directory:

./gradlew test

Frontend Tests

To run the frontend tests, execute the following command in the frontend directory:

npm run test

Deployment

The project will automatically be deployed when a change to the development-branch happens.

Setting up the Deployment Server

On a server of your choice, set up the following:

• Docker
• Dokku
  • Make sure to enable vhost during the installation-dialog (this is the default)

Then, run the following commands:

dokku apps:create quak
dokku builder:set quak build-dir backend

# Set up an ssh-key
ssh-keygen -f github -N ""
cat github.pub | sudo sshcommand acl-add dokku runner@github
cat github
# Save the content of the private for later
# You may also want to move the ssh-keys somewhere else

We now want to set the GitHub-Secrets inside this repository:

• DEPLOYMENT_SERVER_ADDRESS
• DEPLOYMENT_SERVER_SSH_KEY
  • This has the content of the private-key generated above

Lastly, make sure that all relevant ports (e.g. 8080) are exposed to the outside world.

Legacy Execution (Not Recommended)

Note: This method is deprecated. Please use the Docker Development Workflow above.

To run the QuaK editor manually without Docker, run: gradlew bootRun inside the backend directory

Dependencies

The project requires the following dependencies to be installed on the system:

• Java >= Version 21

Automatic installation of nodejs

Through the use of the gradle-node-plugin, the project can automatically install npm. If you want to use this feature, run any gradle-command with the flag -PdownloadNode (i.e. gradlew :bootRun -PdownloadNode).

If you wish to remove the custom nodejs install, run gradlew :removeCustomNode.

License

Copyright (c) 2025 MoQel

This project is available under the MIT License