#cant deploy Postgres S3 Backup template
100 messages · Page 1 of 1 (latest)
Project ID: 948196f9-27d3-44cd-bdd2-e50d7b67c7ef
948196f9-27d3-44cd-bdd2-e50d7b67c7ef
please link to the template
I'm not even seeing a save config button, can you clear cache and try to open the template again?
clear cache browser you mean?
same thing
is there a recommended backup template? i thought this was the "official"
it is the official, there are plenty others that do just as good of a job though
I just don't know why you are getting a different UI than me
I tried both ways too
always got the same UI and never saw the save config button
what browser?
safari
when installing from the template link i get a new project created
that seems to have worked (at least started deploying)
that's good
i was adding it as a service inside another project
I see
how do i reference ${{Postgres.DATABASE_URL}} (of the project i wish to backup) if i deploy on a different project?
you can't, it needs to be in the same
let me see if I can reproduce, I haven't tried deploying it into an existing project
save config, then click deploy
deploy button doesnt enable
can you do a full video?
does a redline in a variable mean "validation error"?
show me?
the only way I can get that button to not enable for me is if i don't fill out everything
yes
i tried a different templame, same problem.
and you have filled out everything the template asks you for?
here i'm supposed to put a fresh name, right? a new repo will be created on my github for each deploy of the template
yep
oh, i think i found the problem
I don't know what to tell you, I just can't reproduce this
but i cant leave it blank
i filled in some random data in there and the deploy button enabled
does the deploy button appear if you did fill it out
it is a required field, there is an asterisks
previous screenshot was of another template i was testing, this video is from the template linked previously.
its a required field
why does this have an asterisk lol
that was another template. deleted to avoid confussion
here is the full flow
@past hare non required variable is being treated as a required variable in the beta in-project template deploy flow
thx
sorry it took so long to raise, this was confusing me too
no prob, thank you for the help
thats a far better name for the problem than what i came up with
I'd guess this will be picked up and fixed early next week.
ok, thank you
should I just try or will this post be updated when de bug is fixed?
We assigned this yesterday but hasn't been picked up yet.
I'll drop a message here once this is fixed.
great, i'll wait
This is very confusing. Will be fixed tomorrow!
I am facing exactly the same issue. 😢
btw you can fill s3 endpoint yourself for now s3.<region>.amazonaws.com
example: s3.us-east-1.amazonaws.com
Funily enough i just encountered the same problem... What worked for me was to delete the BACKUP_CRON_SCHEDULE then hitting submit created the service... Weird
for the time being i'm using:
s3.${{AWS_S3_REGION}}.amazonaws.com
this didnt work but what did work was AFTER deployment, simply deleting the variable
The core issue here should be fixed now.
thx
Hey everyone 👋 I believe I'm encountering somewhat of a similar issue with the same template.
When I fill anything in the AWS_S3_ENDPOINT variable, I get a greyed out "Deploy" button and nothing every happens.
However, when I leave it blank, it becomes available.
I tested this out on both Brave (with and without the blockers enabled) as well as Firefox, on a Linux machine.
Let me know if there's anything else I can help you with, and thank you for your work!
For anyone having the same issue, I believe you can keep this variable empty, create the deployment, cancel it right away, and set it up afterwards 😉
if I remember correctly, railway dev fixed this issue
that s3 endpoint is optional
I understand that it is optional, but I need to fill it in as I'm using Scaleway S3 instead of Amazon S3; and the deployment of the template is not working when providing anything other than an empty value in that variable.
I tested this a week ago, and 5 minutes ago; both had the issue 🙏
thanks for explain, I'm not sure how the Scaleway S3 work, but this template uses aws SDK under the hood, so I guess I accept only AWS endpoint https://github.com/railwayapp-templates/postgres-s3-backups/blob/main/src/backup.ts
No, it works with other S3 compatible storages, that's seems to be a Railway bug
@safe valley do you think it's a bug brody?
I've only used it with cloudflare r2
Can you reproduce it on your machines? I believe these would be the steps:
- create a new service from inside the Railway project (not via "Deploy with Railway button), based on the template "postgresql S3 backups"
- fill in all the fields with (fake) data
Result:
Filling anything in the AWS S3 ENDPOINT variable makes the "deploy" button unclickable
Also, the save button doesn't do anything.
Expected:
The deploy button is available, and the "save config" button creates the service
you can just leave beta via your account settings, then you'd be back on the old template deploy menu without this issue
Oh I don't mind the bugs, just wanted to report it in case anyone has the same issue 😉
my bad, this is definitely a known issue
this is my slightly modified template https://github.com/orenaksakal/backup-cron-railway one time backup script which you can set to run through railway cronjob to run for cost optimization (almost 0 cost). Also you can name your backups like db name so its easier to distinguish if you hold multiple db backups at the same bucket
Contribute to orenaksakal/backup-cron-railway development by creating an account on GitHub.
great! could you put required ENV vars in the readme?