GitHub Codespaces support

[Aprillion]

Not sure if you want to support external contributors who would use GitHub Codespaces, I myself don't know what would be the correct .vscode/launch.json configuration file to make a smooth experience, so I will just describe what I tried.

The default image with remote VSCode does not have postress and the python version is slightly mis-aligned:

---

After I persuaded poetry to install something, I then got following python exception which I didn't feel like debugging on Sunday (I haven't even tried to install postgres if the BE server won't work anyway):

@Aprillion ➜ /workspaces/metaculus (main) $ poetry run python manage.py mjml_compose

System check identified some issues:

WARNINGS:
?: (staticfiles.W004) The directory '/workspaces/metaculus/static' in the STATICFILES_DIRS setting does not exist.
Traceback (most recent call last):
  File "/home/codespace/.cache/pypoetry/virtualenvs/metaculus-web-a4ymonRh-py3.12/lib/python3.12/site-packages/mjml/tools.py", line 30, in _mjml_render_by_cmd
    p = subprocess.Popen(cmd_args, stdin=subprocess.PIPE, stdout=stdout_tmp_f, stderr=subprocess.PIPE)
        ...
RuntimeError: Problem to run command "mjml -i -s"
[Errno 2] No such file or directory: 'mjml'
Check that mjml is installed and allow permissions to execute.
See https://github.com/mjmlio/mjml#installation

---

Frontend npm i;npm start dev worked fine for me, but only for static content of course... Have you considered https://mswjs.io/ to mock the data for potential FE contributors by any chance?

[Aprillion]

after my first PR in this repo, I also noticed that eslint from npm run lint gives me a gadzillion errors on unchanged files, so I'm ignoring those 🤷‍♂️

and I forgot that VSCode setting "editor.formatOnSave": true is not enabled by default in these virtual images => you might want to also consider enabling in .vscode/settings.json (which is currently .gitignore-d, but if you want nicer commits from external people...) 😅

[George3d6]

I think setting up the backend is easy enough that I wouldn't want to use mocks, I would maybe provider a docker compose file that runs the entire backend and allows FE-only contributors to more easily iteratre on that, do you think that'd suffice?

As for what I'd take to run this on gihtub codespaces, I like the idea in principle but I'd probably want external contributors to maintain it, unless there are a lot of people that want to use those (?)

[Aprillion]

TBH, if it was possible for the integration tests GH action to publish "itself" as the latest-good docker image for running the same tests locally without any config whatsoever, that would be easiest to set up 😅 ... but it contains env variables from GH secrets, so probably not suitable for publishing as-is 🤔

No idea about popularity of github codespaces, I just clicked on a big green button while I comtemplated how many years ago I last updated Python on my non-work computer 🙈 Probably best to wait if more people try to use it.