585b8428-c386-4049-98a8-3d98aef07071

Any help on this would be greatly appreciated as I need to do this ASAP

I'm sorry but we do not provide a way to move services between projects

I understand that - however how should I go about manually moving it then

You'd need to export everything in your volumes and move them to new services in the other project.

And how can i do that?

I'm sorry, but I cannot provide project support at this time. I will let the community involve themselves in this thread to assist you.

Oh right okay

It doesn't seem like there's any way to do this

Not natively, no.

I can take a dump of the database but I can't access the files in the volume

So I'm quite unsure of what to do in this situation

Aha, there's a template to dump a volume

So i've managed to get a dump of the volume but now how can i upload this to the new volume?

@Brody I've managed to upload the tar of the old volume onto the new volume with your filebrowser template, however I need some way to extract it, if i had access to the terminal from filebrowser I'd be able to do this however the user you create in your [start.sh](start.sh) script doesn't have the permission to execute commands, do you think this is something you could quickly add?

I tried to fork it myself but I had an issue where the start.sh script would keep crashing when it went to create the database

Try -

oh insane thats literally what i was looking for give me one sec

Managed to get it done!

Steps:

Managed to get it done!

Steps:

1. take down the old Moodle deployment

2. disconnect the volume from the moodle service

3. create a new service from the dump volume template (https://railway.com/deploy/EBwdAh)

4. attach the old moodle volume to the dump volume template

5. follow the steps on the template to dump the volume

6. in your new project create a filebrowser service from the template and follow the steps. make sure you enable the use volume root flag

7. log into file browser and upload the .tar.gz volume dump

8. use the railway CLI to ssh into the filebrowser

9. decompress the dump using the tar command

10. ensure that the moodle folders have the correct permissions

11. update the config.php to reflect the new database credentials

12. disconnect the volume from filebrowser and reattach it to moodle

13. use pgdump and pgrestore to transfer the database (make sure you wipe the database first using psql to start with a fresh db)

14. restart the moodle container

and you should be good to go!

This process really should be improved, it should not be this long and convoluted just to transfer a service from one project to another

!s