#Auto-deploy on Github not working
26 messages · Page 1 of 1 (latest)
Project ID: a21be923-5623-4bcf-bae3-7fa0d2379288
a21be923-5623-4bcf-bae3-7fa0d2379288
Hello,
Services deployed from templates do not auto deploy.
You would want to disconnect the source, and then reconnect your desired repo.
This wasn't created from a template, it was created with the Deploy from GitHub Repo command.
If it has the Check for updates button, it was deployed from a template.
Does having a railway.toml file count? https://github.com/jherr/railway-start-simple/blob/main/railway.toml because all i'm doing in there is just setting the start command.
I will take a look at your service and advise shortly.
Yes this service was deployed from a template, this button only appears for services deployed from templates.
So this advice stands 🙂
i genuinely didn't do that. i really did just deploy from a github project. but that project does have a railway.toml.
the deploying ... section shows when i deploy a different project from a template. but does not appear in the railway-start-simple case.
Please try the advise I gave and let me know if it works!
Yeah, that works, but that's a terrible flow.
If I have a railway.toml that defines the start command:
- Deploy from github project (no I didn't use a template)
- Disconnect from the github project for no reason
- Reconnect to the same github project for no reason
- Rebuild and re-deploy no changes
If I don't have a railway.toml file:
- Deploy from github project (no I didn't use a template)
- Watch it deploy what will be a non-functional setup
- Alter the start command and re-deploy (requires an entire rebuild)
- Try to push to github and auto-deploy and ... it doesn't work So back to step 2 above where I have to disconnect again
Yeah, so it's not even an issue with their being a railway.toml file at all. This just seems to not-auto deploy unless you disconnect/reconnect to the same repo.
A railway.toml file has no involvement in this flow.
no I didn't use a template
I'm not sure I understand why you don't think that's the case, you deployed your own template -
that was a DIFFERENT project. I was just showing the different between a template generated project and one deployed from a github repo.
Here is a project I just generated from a repo: fd684663-de1c-41fb-bf22-0c3842bb6aaa
here is a screen capture (edited for time) that shows that's deployed from a repo and still has "Check for Updates"
Railway probably thinks that you do not own that repository (it thinks it's a public repository from someone else). Instead of copying the entire URL, search for your repository name in the search bar and wait until it pops up as an option.
Ok, thanks.
If it is what I said, I would recommend opening a #1157406325593096264 thread about that.
Yep thalles is correct, you are deploying your repo as if it was a public repo, thus deploying it as a template service.
well, he left
!s