You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
usirin opened this issue
Aug 15, 2023
· 3 comments
· May be fixed by #734
Assignees
Labels
CI/CDthings related to continuous integration & deployment of the repositoryepica big issue that tracks other issues, if you know jira, you know what epics are :D
This is a dream project for me where we provide free resources for the proven contributors of @kamp-us/kampus-devs
I've joined @koding almost 10 years ago, dreaming that one day we can do this. Open source communities funded via community sponsorships can remove the barrier to use compute for everyone, and I want us, as @kamp-us/kampus-devs, to start working towards this goal.
Thanks to @sevilayerkan we realized we can actually do it with codespaces. This epic will track the progress of this effort.
Acceptance criteria
any member of @kamp-us/kampus-devs can create a codespace develop on cloud for free, kampus will pay that.
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.
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.
CI/CDthings related to continuous integration & deployment of the repositoryepica big issue that tracks other issues, if you know jira, you know what epics are :D
What is this epic about?
This is a dream project for me where we provide free resources for the proven contributors of @kamp-us/kampus-devs
I've joined @koding almost 10 years ago, dreaming that one day we can do this. Open source communities funded via community sponsorships can remove the barrier to use compute for everyone, and I want us, as @kamp-us/kampus-devs, to start working towards this goal.
Thanks to @sevilayerkan we realized we can actually do it with codespaces. This epic will track the progress of this effort.
Acceptance criteria
Tasks
@sevilayerkan please fill this out :D
The text was updated successfully, but these errors were encountered: