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
We keep changing our course recommendations for how people should host backends because we keep relying on free tiers of services that either take them away or change them.
This sucks.
Our trainees/graduates make really small, low-resource-consuming apps.
I think we should just host a https://www.coolify.io/ instance somewhere, and make it easy for our trainees to host their stuff on it.
Or just pay for Coolify Cloud.
I think we should be comfortable spending something like £1000/year on this problem, but I suspect we can solve it for less.
Acceptance criteria
Scenario: free creating of project on our trainees and graduates
GIVEN a trainee OR graduate on the CYF GitHub organisation
AND I need to create a CYF project
WHEN they log onto the CYF Coolify
THEN I can create my projects for free
Scenario: free deployment of projects for our trainees and graduates
GIVEN a trainee OR graduate on the CYF GitHub organisation
AND I need to deploy a CYF project
WHEN they log onto the CYF Coolify
THEN I can host my projects for free
Scenario: free configuration of projects for our trainees and graduates
GIVEN a trainee OR graduate on the CYF GitHub organisation
AND I need to configure my CYF project
WHEN they log onto the CYF Coolify
THEN I can configure my projects for free
Scenario: tech stack accepted on CYF Coolify
GIVEN I am a trainee OR graduate with access to the CYF Coolify
WHEN I load my project using
NodeJS
AND Python backends
AND PostgreSQL databases
AND static frontend
THEN it is hosted on CYF Coolify
Scenario: cost threshold - £1,000
Depends on spiike
Scenario: document instructions on how trainees and grads can use our instance
GIVEN I am a trainee or graduate with access to CYF Coolify
WHEN I use the instructions
THEN I can easily use this software.
I really agree with this. I proposed something similar a few years ago but we found some problems with getting access and budget for things. If you could drive this I would be super happy.
Background
We keep changing our course recommendations for how people should host backends because we keep relying on free tiers of services that either take them away or change them.
This sucks.
Our trainees/graduates make really small, low-resource-consuming apps.
I think we should just host a https://www.coolify.io/ instance somewhere, and make it easy for our trainees to host their stuff on it.
Or just pay for Coolify Cloud.
I think we should be comfortable spending something like £1000/year on this problem, but I suspect we can solve it for less.
Acceptance criteria
Scenario: free creating of project on our trainees and graduates
GIVEN a trainee OR graduate on the CYF GitHub organisation
AND I need to create a CYF project
WHEN they log onto the CYF Coolify
THEN I can create my projects for free
Scenario: free deployment of projects for our trainees and graduates
GIVEN a trainee OR graduate on the CYF GitHub organisation
AND I need to deploy a CYF project
WHEN they log onto the CYF Coolify
THEN I can host my projects for free
Scenario: free configuration of projects for our trainees and graduates
GIVEN a trainee OR graduate on the CYF GitHub organisation
AND I need to configure my CYF project
WHEN they log onto the CYF Coolify
THEN I can configure my projects for free
Scenario: tech stack accepted on CYF Coolify
GIVEN I am a trainee OR graduate with access to the CYF Coolify
WHEN I load my project using
NodeJS
AND Python backends
AND PostgreSQL databases
AND static frontend
THEN it is hosted on CYF Coolify
Scenario: cost threshold - £1,000
Depends on spiike
Scenario: document instructions on how trainees and grads can use our instance
GIVEN I am a trainee or graduate with access to CYF Coolify
WHEN I use the instructions
THEN I can easily use this software.
Stakeholder
@illicitonion
The text was updated successfully, but these errors were encountered: