Online editing: Upload assets to s3 bucket

[wen-templari]

Currently when upload image at editing, the image was uploaded to repo. This will cause repo size increase after there are many images. I suggest we separate those images from repo, upload to external storage when edit and only keep a reference.

Suggested implimentation

Since we already using Cloudflare worker to host this page, I suggest we continue to use Cloudflare R2 storage for storing images. After edit save, upload image to R2 storage, keep a reference to that uploaded asset, and sever it directly or via worker.

[m1ngsama]

Thanks for raising this — I agree, and long term the repo is the wrong place for uploaded images.

Some context on why it works this way today: when I built the upload path, I had no information about what storage infrastructure we already have, so I followed LazuliKao's suggestion and compressed the images into the repo instead. They're converted to WebP in the browser before being committed, which keeps the size down for now, but it doesn't address the growth you're pointing at.

Would you be willing to take this part on? I'm asking for two reasons: I have neither access to nor knowledge of any bucket infrastructure, and I'm still undecided on a number of design questions in the editor component — I suspect it would turn out better in your hands 😄

[wen-templari]

In this case, I prefer to keep this open as a 'good first issue' for new contributors.

For storage, I suggest we use R2 storage for now since we are already hosting this on Cloudflare and change to use the aliyun s3 bucket later if needed.

Thanks for raising this — I agree, and long term the repo is the wrong place for uploaded images.

Some context on why it works this way today: when I built the upload path, I had no information about what storage infrastructure we already have, so I followed LazuliKao's suggestion and compressed the images into the repo instead. They're converted to WebP in the browser before being committed, which keeps the size down for now, but it doesn't address the growth you're pointing at.

Would you be willing to take this part on? I'm asking for two reasons: I have neither access to nor knowledge of any bucket infrastructure, and I'm still undecided on a number of design questions in the editor component — I suspect it would turn out better in your hands 😄

[wen-templari]

E2E test failed after merging #181 (#181 (comment)), waiting for the fix.