Missing certain options for local testing purposes.

[zcaliptium]

Is your suggested enhancement related to a problem? Please describe.

When I tried to run labrinth backend locally I encountered such problems. I can't just register account for testing purposes.

1. It will throw out Captcha Error. Try resubmitting the form..

Then If I disable Cloudflare integration code...

2. It will throw out SMTP Error: Connection error: No such host is known. (os error 11001) because SMTP server is not configured.

Describe the solution you'd like

Put options into dotenvy config:

1. To completely disable Turnstile (Cloudflare Integration).
2. To disable email sending and account verification.

Adding such options can make running local instance less painful.

Describe alternatives you've considered

No response

Additional context

No response

[piprett]

I think this is a barrier for most people who want to contribute to labrinth. It's just hard to get dummy data and accounts. There seems to be some code in the test package for generating dummy data, but there is no documentation around how to use this. Ideally I think we should allow most env variables be empty, and disable those features. For example if no SMTP is configured, instead print the email contents in the logs. In addition to disabling these features, I would suggest that we also implement and document some utility to generate dummy data.

For the turnstile specifically, there seems to be some testing tokens for development: https://developers.cloudflare.com/turnstile/troubleshooting/testing/

[piprett]

I have now gotten labrinth to work locally-ish. Steps:

1. Update frontend .env with following settings:

BASE_URL=http://localhost:8000/v2/
BROWSER_BASE_URL=http://localhost:8000/v2/

2. In labrinth update the following in .env:

-TURNSTILE_SECRET=none
+TURNSTILE_SECRET=1x0000000000000000000000000000000AA

-SMTP_USERNAME=none
-SMTP_PASSWORD=none
-SMTP_HOST=none
+SMTP_USERNAME=hello
+SMTP_PASSWORD=world
+SMTP_HOST=localhost
+SMTP_PORT=2525
+SMTP_TLS=false

3. Run a program like smtp4dev to start a mock SMTP server on port 2525 with no authentication or TLS.
4. Modify labrinth to add SMTP_PORT and SMTP_TLS settings, or install certs and use correct port. (see feat(labrinth): environment variables for more customizable SMTP #2886)
5. Run dependencies (meilisearch, postgres, redis, etc)
6. Run frontend & backend

[AlexTMjugador]

Now that PRs #3545, #3544, and #2886 have been merged, spinning up a local, mostly functional Labrinth instance is now a much better experience, and I'd say this issue has been addressed! 🎉

There are still a few integrations that could use test doubles, such as client IDs for auth providers or billing providers. However, these feel out of scope for this issue, and likely for most Labrinth development as well, in addition to probably also harder to mock.