Hey! 🐻 I have an "upload server" project called **rustypaste**: https://github.com/orhun/rustypaste I'm trying to deploy it to shuttle and I actually managed to do it: https://rustypaste.shuttleapp.rs However, since I don't exactly know how shuttle works, I'm curious how it happened out of the box. For example, now you can upload files like this:

curl -F "file=@Cargo.toml" https://rustypaste.shuttleapp.rs

Internally, are they uploaded inside an isolated container? If so, is there any disk/memory/cpu limits? Is there any documentation about this? Thank you for this great project!

hmm. Docs list the RAM and CPU count, but not more details that I can see rn

where exactly that is stated?

Your project runs in a docker container, but writing to the file system is not recommended, since the container is wiped when you do

cargo shuttle project restart

(which you do when upgrading shuttle version, or when things break). For persistent storage, you want to use some form of database. You can check the supported ones on the docs, but there are also more of them in the works.

thanks for your answer @gentle-ice-1561 I'm planning to auto-expire the files after one hour or so would you recommend using the filesystem in this case? also, is there a disk usage limit?

Yeah, for that use case it works fine then I guess 😄

alright

It uses a Docker volume, but I'm struggling to find if there is any limit set.

Yeah I don't think it's persistent - it would be much better to just use some kind of r2/s3 bucket then have an API key system for retrieving images

it seems like the disk space available to the docker containers can be limited via

--storage-opt

option

With the blog post out, rustypaste seems ready for #968836095821373441 😉

hmm, seems to be working on my end

Ah, worked now upon refresh 👌

I think that happens when the service wakes form timeout 😕