Symbolic links not resolved when building with Nixpacks?
project
8093f881-dd83-4250-b725-dd87c94a218e
service c4c15496-00f3-4369-a0e6-212cfedc8913
Railway builder: Nixpacks
Build tool: Gradle
Language: Kotlin
The source directory of one of my modules ({module}/src/main/kotlin) is a symbolic link to a sibling module's source directory. The link is correct and checked in to version control - GitLab CI builds this project without any issues using the same build command.
During Railway builds, however, the symbolic link isn't resolved, the module which owns the symlink reports NO-SOURCE and compilation of dependent modules fails due to unresolved references.
Is there anything I can do to fix this?
I suppose instead of a link I could copy the sibling module's source code during setup phase?3 Replies
Project ID:
8093f881-dd83-4250-b725-dd87c94a218eI solved this by copying the directory in Nixpacks install phase.
FWIW I found out that the symlink file is missing during the build on Railway. Somehow it's not checked out? I can see it in the GitHub repository though, so this must be something on Railway's side.
Railway won't resolve submodules, that's correct.