I'm sure yall have already run into this, but, that thing with gitea where you can't change the env vars on teh docker-compose and let it recreate the contianer. you have to actually go into the config file and edit the config file itself
Tales from Co-op Cloud Tech channel:
> maybe you could set up a handler that matches the .../raw/... URL pattern and then in that handler, put Access-Control-Allow-Origin: *
> so the problem looks like https://cors-container.herokuapp.com is down? its returning 503
> looks like gitea now has a config for it?
https://docs.gitea.io/en-us/config-cheat-sheet/#cors-cors
> I'm sure yall have already run into this, but, that thing with gitea where you can't change the env vars on teh docker-compose and let it recreate the contianer. you have to actually go into the config file and edit the config file itself
> here is a quick ez guide which shows an example config 💯 https://tesh.at/blog/gitea-cors/
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On this instance https://recipes.coopcloud.tech/ all the links to find out more produce an error 'unable to load app data'
Thanks for the report @samuk! We'll look into it ASAP. I suspect some issue with the dodgy CORS proxy we're using 😬
Tales from Co-op Cloud Tech channel:
It's fixed! 🎉