JohnTsang
CDCloudflare Developers
•Created by JohnTsang on 2/21/2025 in #workers-help
wrangler deployment overwrites env vars in the worker
@Walshy | Workers/Pages
thanks for your reply.
way 1 : now I made a wrangler.toml.example file to record those placeholder values to indicate and set up all the vars and secrets in wrangler.toml got git ignored.
But I found that doing in this way won't trigger cicd properly when I connect my github repo to the worker because the wrangler.toml file is git ignored, so I have to manually run the deploy cli command everytime.
is it a good practice?
way 2: like you said, just make comments for those secrets and hardcode the insensitive vars, and allow wrangler.toml file by git commit and push to the repo. Before first deployment, run wrangler secret put command, but I'm not sure whether it would need me to do it again when I deploy next time or maybe the worker would just keep it there.
By contrast, I think this way could do the cicd properly when we connect the github repo to the worker.
which one do you recommand?
7 replies
CCConvex Community
•Created by JohnTsang on 11/23/2024 in #general
`_creationTime` not guaranteed to be monotonic over time
OK. I see. Thank you.
5 replies
CCConvex Community
•Created by JohnTsang on 11/23/2024 in #general
`_creationTime` not guaranteed to be monotonic over time
Now I add an index for the field called "statusUpdatedAt", and do the descending order on it rather than on the _creationTime, which solves my problem now.
So, I'd like to know whether it's not a very good practice to do descending order on the _creationTime field if the order of data really matters. @RJ
5 replies
CCConvex Community
•Created by JohnTsang on 11/23/2024 in #general
`_creationTime` not guaranteed to be monotonic over time
OK, I'll check it out later
5 replies