Issues with sub module folder

a year ago

I'm unable to run tthe staging backend since I added a shared folder (src/shared) which is a github submodule and its contents are required to run the pro ject.

Could you help please?

$10 Bounty

1 Replies

brody

EMPLOYEE

a year ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody • about 1 year ago

colinrm000

HOBBY

a year ago

Your new src/shared folder is a Git sub-module.

That means it isn’t real code in your repo, just a pointer to another repo.

If you don’t pull that pointer, the folder is empty and the backend can’t find the shared code.

How to fix (everywhere you run the project):

1.First-time clone

   git clone --recursive <repo-url>

2. Existing clone, Dockerfile, CI step, Railway build, etc.

   git submodule update --init --recursive

Railway shortcut: set

RAILWAY_GIT_CLONE_FLAGS="--recursive --depth 1"

so it always pulls sub-modules.

Once those commands run the src/shared files are on disk and the staging backend should start normally! 🙂

Welcome!