56cafcfa-394c-46c9-a811-dc3207bad3dc

Hey, may I ask your usecase for more than 10 volumes per project?

Can't have more than 10 services with volumes then?

correct

we have about 10 services in our environment, 6 of which have a volume (some DBs, redis etc.). we duplicate this environment once for staging, and once for development. and then we also have PR envs that automatically get generated when a new PR is open and clone the dev environment.

Now we need to add one more stateful service (a meilisearch instance), and this is blocking us.

It also seems a incosistent — we already have way more than 10 volumes right now across all the envs in this project. Seems like when you duplicate an env or a PR env is created automatically, it doesn't enforce the limit?

iirc it's 10 volumes per environment to be technically correct

don't think so, just tried in this particular env which has only 4 volumes

interesting, I'll bump it for you, just wanna hear back from OP

OP and I are on the same team 😄

ah, just thought you were someone else with the same issue

how many volumes would you say you need to have safe margin from getting that error again?

if it were per environment, we'd be definitely fine with only 10 at least for a while

if it's per project BUT automatically generated PR envs don't count, then I suppose 30 so we could duplicate an environment with 10 volumes 3 times.

if it's per project and automatically generated PR envs also count, i guess the number would have to be much higher, maybe 50 or so? it'd be pretty hard to predict then, would be a bummer if someone gets blocked from deploying something new just because a bunch of PRs happen to be open

curious though whether generally this is a plan-based limitation or there's a technical reason for it? like, we pay for storage over time afaik, so why is such a relatively low limit needed?

the reason for it would be far above my understanding, something about we want users to reach out to us and talk to us about what they're using the platform for, but that's at the cost of temporarily blocking the team given it is such a low number (same number for hobby) so I'm just going to bump it to 50 (it's a workspace level setting)

got it, so i guess it's an artificial entry point for the enterprise plan sales funnel then 😄

thank you very much, that'll keep us going for a good while at least 👍

something like that I guess, hasn't worked as far as I've seen, we've always just been like "yep they aren't doing anything suspicious, here's more volumes"

I'll let you know when I've bumped it

bumped

That's great, thank you!

no problem!

!s