Technically three* mount points (unless we just want to mount /var, which would be kind of insane)

Template repo: https://github.com/vergissberlin/railwayapp-gitlab

@vergissberlin Apologies for the ping, but if you have any advice here as well, that would be incredible.

Railway only supports one mount point per volume right now:

Read more on caveats here

The logs and config folder probably don't need to be mounted though!

@Mykal can we deploy from a repo's compose that manually sets up the additional volumes?

We'd need to store the config though 🤔

The logs I agree with, but I'm not sure how else to have gitlab read persisted config

Got an idea- let me type it up for you

could you do something like:

 
FROM gitlab/gitlab-ce: 

# copy over config (would need to check out what config looks like)
COPY config /etc/gitlab

and then have railway use that dockerfile?

A little more boilerplate but then you have version control around config too (may be desirable for you depending on your usecase)

Ah that would be pretty clean yes

And we'd fall back on the repo as the source for the config

Makes sense thank you 🙂

Yessir!

I have done similar things for a few of my templates 🙂

so yeah would try

1. start up container locally with volume mount, pull out default config into your repo and push it
2. writeup the dockerfile above and push it as part of the repo
3. point railway at your dockerfile
4. volume mount the /var/opt/gitlab folder for data persistence
5. follow gitlab setup steps
6. redeploy / restart and check if data is persisted 🙂

lmk if you run into any issues- best of luck <:salute:1137099685417451530>

@Mykal This worked well by the way! Thank you for your assistance 🙂

For future reference, is there a technical limitation to why Railway doesn't support multiple mount points or multiple volumes? Or is it just planned work that hasn't been picked up yet?

Hey! really glad to hear that worked for you

Can't speak to the technical limitations; but I know it's been talked about for years so I am sure it's on the teams radar.