Scalable volume size for template project deployment?
Hey, I was just curious whether the volume size could be automatically scaled depending on necessary volume quantity when creating a project. For example, if I created a Wordpress template and published it, most of the contents folders and other persistent files are stored in the volume, possibly exceeding the default quantity of 100mb. If I created one, does the size cap at the max for the plan but waits for first deployment to set or could a template feature be introduced with a configurable value?
26 Replies
Project ID:
N/AN/A
Following this. Just tried deploying a docker image of Wordpress and got no luck. I've managed to launch wordpress with persistant storage on wp-content but not on the root. Have you managed to get it up and running correctly with the bigger volume size?
I’m assuming I definitely can, only problem and worry on my part is default volume size with templates; I can check though.
You can but there's issues with css and ftp access to write new files.
Ah, that’s true. Should be fine with the volume though, no?
The volume limitations for the hobby plan are 10GB each. You are charged by 0.25/GB
you have nothing to worry about
That’s not my question.. I know that.
what’s your question then? it’s not clear
Is the max size of a volume scalable on first deployment or per value in template to ensure complete deployment?
that’s still not clear, please elaborate
Cause if I make a template with a service that deploys its core files in the volume as necessary but its larger than the default maximum size of 100mb, will it auto scale or prevent the deployment/installation from completing?
the amount provided in each volume is dynamic
that has nothing to do with the volume sizes. Railway’s deployment storage will handle all of this
the default maximum is 10gb, so you will have no problems
I’m not clear on what your problem is
is this theoretical or practical?
All volumes are created with a default maximum of 100mb and can be scaled up but not down, per documentation, am I wrong?
That’s just the limit for each plan and scaling towards, not the default maximum for each volume..
Or was this changed?
you’re not wrong, but the price is no different
so it really doesn’t matter
I know, just worried that the build wouldn’t complete and error the deployment if it needs more than the default maximum allocated when not specifiable in the template.
I’ve seen pictures of size increasing earlier, but now seeing different things different places.
I don’t think you have anything to worry about
this is something you can test yourself
From my testing, I couldn't get it to work, even with the volume mounted at any size. Wordpress kept asking for ftp write access, even after mounting at /wp-content. I don't think it's possible unless railway allows for root mount in the future.
Got it! Expect a template release soon hopefully!
Amazing work. Testing it now!