Railway•10h ago

Deploy from connected image not triggering?

I have my deployment connected to an image in ghcr.io. The first time I deployed, it worked fine; however, I just published a new image a few minutes ago, and Railway hasn't picked it up. Does it just take some time? 12fe90d4-42ca-4704-980b-e16da59696c0

33 Replies

Percy•10h ago

Project ID: 12fe90d4-42ca-4704-980b-e16da59696c0

Brody•9h ago

we unfortunately do not monitor for newly published images, simply because there is no good way to do that, with GitHub repos, GitHub sends a webhook, but that doesn't happen when new images are publishing

tiltowait•9h ago

Oh, that’s a shame. What’s the recommended workflow?

Brody•9h ago

Well I'd first have to ask, why not simply attach the GitHub repo to the railway service and let railway build and deploy the image?

tiltowait•9h ago

I liked the idea of deploying on tag creation vs a push to a branch

Brody•9h ago

fair enough i assume you have a gh action to build an image right?

tiltowait•9h ago

Yes

Brody•8h ago

does this action create an image with a different tag every time it builds an image?

tiltowait•8h ago

Yes, but also updates latest

Brody•8h ago

would you settle for deploying the service from latest when a new image is published?

tiltowait•8h ago

Tbh that’s what I thought I was doing, or at least attempting

Brody•8h ago

well if you are okay with that, you could call railway redeploy in an action? in an action that runs after a successful image has been built that is

tiltowait•8h ago

Ah, sure, I can do that Thanks

Brody•8h ago

youd just need the project token - https://docs.railway.app/guides/cli#tokens and then railway redeploy -y --service <service_id>

tiltowait•8h ago

Thanks. I’ll look into it!

Brody•8h ago

let me know if you get stuck!

tiltowait•5h ago

Would this be correct?

deploy:
  needs: build
  runs-on: ubuntu-latest

  steps:
    - name: Use Node 22
      uses: action/setup-node@v4
      with:
        node-version: 22.x

    - name: Install Railway
      run: npm i -g @railway/cli

    - name: Deploy
      run: railway redeploy -y --service <service_id>
      env:
        RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}

deploy:
  needs: build
  runs-on: ubuntu-latest

  steps:
    - name: Use Node 22
      uses: action/setup-node@v4
      with:
        node-version: 22.x

    - name: Install Railway
      run: npm i -g @railway/cli

    - name: Deploy
      run: railway redeploy -y --service <service_id>
      env:
        RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}

Brody•5h ago

i honestly dont know the syntax for github actions off the top of my head, but id use the docker image for the cli and an environment variable for <service_id>

tiltowait•5h ago

Okay, wasn't sure if the service ID should be secret or not

Brody•5h ago

nope, its just a uuid

tiltowait•5h ago

the docker image for the cli

Do you mean my docker image, or is there a Railway image?

Brody•5h ago

this one - https://github.com/railwayapp/cli/pkgs/container/cli

tiltowait•5h ago

deploy:
  needs: build
  runs-on: ubuntu-latest
  container: ghcr.io/railwayapp/cli:latest
  env:
    SVC_ID: <blah>
    RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}

  steps:
    - name: Deploy new image
      run: railway redeploy -y --service ${{ env.SVC_ID }}

deploy:
  needs: build
  runs-on: ubuntu-latest
  container: ghcr.io/railwayapp/cli:latest
  env:
    SVC_ID: <blah>
    RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}

  steps:
    - name: Deploy new image
      run: railway redeploy -y --service ${{ env.SVC_ID }}

Brody•5h ago

do you still need runs-on if you are providing the image? I genuinely don't know, and I'd still use a GitHub secret for the service id, while it's not sensitive, I'd image updating the service id via there GitHub UI is going to be easier / more efficient than editing the action file

tiltowait•5h ago

the example had the runs-on