Cloudflare Pages setup/hookup #145

New Issue

freakoverse · 2024-11-17T17:13:45Z

freakoverse commented

2024-11-17 17:13:45 +00:00

Similar to how we hooked up the gitea repo to github and master gets updated there, we'll do the same thing hook gitea to cloudflare and most likely use that (ddos protection with their CDN and another option in case things go wrong).

Link: https://developers.cloudflare.com/pages/get-started/

Similar to how we hooked up the gitea repo to github and master gets updated there, we'll do the same thing hook gitea to cloudflare and most likely use that (ddos protection with their CDN and another option in case things go wrong). Link: https://developers.cloudflare.com/pages/get-started/

freakoverse added the

Kind/Security

Priority

Medium

labels 2024-11-17 17:13:45 +00:00

freakoverse added this to the Extra Features project 2024-11-17 17:13:45 +00:00

freakoverse commented

2024-11-29 09:51:21 +00:00

Aside from having the cloudflare ages setup, for the purpose of it being the best (presumably) to handle ddos attacks with its CDN, I'm also thinking of if I can have it setup and updated manually, and having it as the public repo for all to see, and not use CI to auto push builds to it to avoid having nostrdev account associated with it / have people discovering it (to avoid nostrdev having to deal with potential attacks).

Thoughts?

Aside from having the cloudflare ages setup, for the purpose of it being the best (presumably) to handle ddos attacks with its CDN, I'm also thinking of if I can have it setup and updated manually, and having it as the public repo for all to see, and not use CI to auto push builds to it to avoid having nostrdev account associated with it / have people discovering it (to avoid nostrdev having to deal with potential attacks). Thoughts?

b commented

2024-11-29 10:29:54 +00:00

am not familiar with using cloudflare for static hosting / repo management, but presumably we could use a dedicated service account

Sign in to join this conversation.