Ref Arch for Github actions for container build (complex) - Deploy to railway.

Question

Hi all, I want to start moving core services to Railway from another cloud provider, and one of the challenges we have is we have a complex docker image that doesn't play nice with Railway's build process.

Right now we have an action that looks similar to this. We have a few submodule dependencies (private and public repos we pull from that aren't always in the package managers depending on branch).

What do you recommend we do in this scenario?

```
name: Prod CI/CD

on:
  release:
    types: [published]

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout main repo
        uses: actions/checkout@v3
        with:
          ref: staging
          submodules: false  # Do not use submodules here

- name: Checkout submodules using GH_PAT
        run: |
          git config --global url."https://x-access-token:${{ secrets.GH_PAT }}@github.com/".insteadOf "https://github.com/"
          git submodule update --init --recursive

- uses: actions/setup-node@v3
        with:
          node-version: 22

- run: npm install --legacy-peer-deps
      - run: npm run build

- name: Set up Docker buildx
        uses: docker/setup-buildx-action@v2

- name: Set up Docker metadata
        id: meta
        uses: docker/metadata-action@v4
        with:
          images: |
            123456789012.dkr.ecr.region.amazonaws.com/company-prod
          tags: |
            type=ref,event=tag

- name: Log in to AWS ECR
        uses: docker/login-action@v2
        with:
          registry: 123456789012.dkr.ecr.region.amazonaws.com
          username: ${{ secrets.AWS_ACCESS_KEY_ID }}
          password: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

- name: Build and push
        uses: docker/build-push-action@v3
        with:
          context: .
          push: true
          tags: ${{ steps.meta.outputs.tags }}
```

🎤｜chit-chat