This needs secrets which makes it impossible to run the CI for external collaborators when they create a PR.

Add more locations, mainly in LATAM and also Spain

A test failure should not be recognized by the error code but by the message from shadowtest.
This way we can integrate with shadowtest easier and we don't rely on status code given that the service is working correctly, just the key don't work.
Upcoming changes to shadowtest require this shadowmere-xyz/ShadowTest#76

Django 5.0 is out and with it GeneratedFields.
Replace the manually generated fields with the proper ones https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.GeneratedField

https://github.com/jadolg/shadowmere/blob/main/proxylist/models.py#L97-L117

warning: PostgreSQL only supports persisted columns

The latest release broke the huey scheduling. Figure out what broke it and fix it.

Add a /metrics endpoint to be scraped with prometheus.
We need at least error metrics to detect when stuff is broken.

If a subscription fails to be fetched, in the admin site there should be a column with the reason.

Sentry Issue: SHADOWMERE-2

Error: Invalid base64-encoded string: number of data characters (249) cannot be 1 more than a multiple of 4
(17 additional frame(s) were not displayed)
...
  File "rest_framework/fields.py", line 562, in run_validators
    validator(value)
  File "proxylist/models.py", line 17, in validate_sip002
    if get_sip002(value) == "":
  File "proxylist/models.py", line 76, in get_sip002
    decoded_url = decode_base64(url.encode("ascii"))
  File "proxylist/base64_decoder.py", line 16, in decode_base64
    return base64.b64decode(data, altchars)
  File "base64.py", line 88, in b64decode
    return binascii.a2b_base64(s, strict_mode=validate)

We need a space to test production-ready code before deploying it to prod.
Right now we only test locally before deploying to prod.
This has worked so far with some bumps and we want to make it easier to test everything before publishing.

We might want to add support in Shadowtest first or try converting the key to a static one

Sometimes we can only use 443 to connect to this servers...

On the admin page, it should be visible the last time a subscription was successfully scraped.

https://github.com/MatsuriDayo/nekoray

https://shadowmere.akiel.dev/api/sub

Some subscriptions are slow to respond and eventually timeout even when they are alive. Either increase the default timeout or make it configurable.

but still leave it enabled by default.

They look like this

They should be all in one row

Im try it using this url https://shadowmere.akiel.dev/api/sub to ShadowSocks and https://shadowmere.akiel.dev/api/b64sub/ to V2Ray and nothing happens

The project is very poorly tested and therefore could be broken easily.
Add more tests to improve resiliency against changes.

Helps in identifying from the huge list