feat: Adding support to run on Github Codespaces for local development and testing.

[alexjyong]

Signed-off-by: Alex Yong [email protected]

Please make sure to check the following tasks before opening and submitting a PR

• I understand and have followed the contribution guide
• I have tested my changes locally and they are working as intended

[DeclanChidlow]

While this all seems to be working quite well, I do question the utility of such a thing. Given this repository runs everything with Docker containers, it isn't really suited for development.

I suppose it is handy for testing, but users wishing to test Revolt would probably just be best off checking out the already hosted instance, and the Codespaces environment isn't a great reproduction of running Revolt on a server.

Perhaps there is a use case I'm missing?

[alexjyong]

In my case, I wanted to be able to run something myself quickly and easily without having to set up an account on a hosting platform (and at the time, digitalocean, which I do have an account with, was having an incident).

This can also be useful if you modify the revolt code, rebuild the docker images, and want to test it out quickly in a ephemeral environment.

I myself do a lot of work in GitHub codespaces and having something available that I can use to quickly fire up a dev environment is pretty handy.

[IAmTomahawkx]

This may be more suited towards adding onto the backend repo. This repo is specifically intended for deploying static release builds, not really for development. I'll leave it open to @insertish for final say though.