So far, I have researched whether it is feasible for us or not. I have analyzed the system requirements related to working with the kampus-monorepo on Codespaces or similar systems. Together with @durmusrasit, we have discussed other aspects that our contributors are going to need, such as working/idle hours, etc.

At the moment, it seems like 4GB of RAM is going to be sufficient for us to work on development. After testing the dockerized version of the repository, we will finally be able to determine the which Codespace machine configuration that we are going to need.

I've made progress with the custom codespaces setup. Anyone who wants to use it can create a custom codespace using this script.

In this setup, all requirements (such as Docker, npm, Node, Prettier, etc.) and extensions come pre-installed, along with the requirements specified in the package.json file.

Usage

• Create /.devcontainer/devcontainer.json file in your fork.
• Copy this script into that file.
• And start a new codespace in your fork.
• After the codespace is created, you can continue running the project from here

Right now, I haven't been able to resolve the issues related to modifying the hosts file and setting up .env files with my script. If I manage to solve these problems or if we decide to dockerize the project in the future, we'll be able to run the project immediately after creating the codespace.