a month ago
I started a project (clawdbot) over the weekend. Monday night it started having issues with re-deployment, so I left it alone. Now the underlying project has renamed (moltbot) and I know there are issues updating it.
I suspect that the best way for me to get my project up to date would be to actually start a new project with a fresh install. But then I think it would be easiest if I could migrate my existing volume (where /data) lives to the new project.
Is there any way to do this?
I feel like this is cleaner/safer than trying to continue fixing things within the current project.
Pinned Solution
a month ago
You have to transfer your files in /data from your old volume to the new volume in the new project. But the thing is, Railway SSH does not support traditional file transfer methods like SCP, SFTP nor direct file transfer. So you would have to see the suggested workarounds in the docs. If you have a db on the other hand, it's much easier, as you would just run a command like pg_dump to get your data and move it to the new db.
1 Replies
a month ago
You have to transfer your files in /data from your old volume to the new volume in the new project. But the thing is, Railway SSH does not support traditional file transfer methods like SCP, SFTP nor direct file transfer. So you would have to see the suggested workarounds in the docs. If you have a db on the other hand, it's much easier, as you would just run a command like pg_dump to get your data and move it to the new db.
Status changed to Solved brody • about 1 month ago