Deploy with Workers - deploy_to_cf_workers e2e.yml skipped
I cant seem to figure out why, I entered my account & API token but each time I try to deploy using the templates repo the deploy_to_cf_workers task skips the e2e.yml action. Thus the whole job skips. Any ideas?
https://github.com/danner26/workers-sdk/actions/runs/8887591310
GitHub
deploy_to_cf_workers · danner26/workers-sdk@c4d034a
⛅️ Home to Wrangler, the CLI for Cloudflare Workers® - deploy_to_cf_workers · danner26/workers-sdk@c4d034a
11 Replies
What exactly are you trying to do? That repo is for wrangler’s source code
If you’re trying to deploy your own workers, start at https://developers.cloudflare.com/workers/get-started/guide/
Cloudflare Docs
Get started guide · Cloudflare Workers docs
Set up and deploy your first Worker with Wrangler, the Cloudflare Developer Platform CLI.
Sorry should have led with that
I am trying to use this
https://github.com/cloudflare/workers-sdk/tree/main/templates/worker-prospector
GitHub
workers-sdk/templates/worker-prospector at main · cloudflare/worker...
⛅️ Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk
(for future learning, that job has an if condition that is checking for repo owner and such in the definition)
ahh
I guess that is why it says it is for internal use lol
not what you want eitherway though, did you try the steps outlined in that for deployment?
looks like the first command is wrong
npx wrangler generate my-project worker-prospector instead of prospector, but the rest looks ok?I was just trying the deploy button before I started digging into how everything works, which is explained well in this article: https://blog.cloudflare.com/how-we-built-an-open-source-seo-tool-using-workers-d1-and-queues. I just wanted to check if there was something obviously wrong on my end or if it was a bug
Yeah if you want to use that template you’ll have better luck manually pulling it out or trying the generate command as Chaika said
The deploy button stuff really isn’t set up to handle repos like this and should probably just be removed
Okay, thanks for the information. I will dig deeper into it but you can close this then. I appreciate your time
If you're looking for something easy I would look elsewhere, this example might be usable as a pure code example/to help guide you to your own, but the tutorial is really lacking, you'd have to have knowledge of wrangler/workers & mailchannels to get this working really
in specific:
it's telling you that you can name the db anything but it really has to be
keyword-tracker-db for the hardcoded migrations to work
the migrations script is unix only (although you can just copy out the commands and do them one by one if you are mindful of the limitation above)
it's using mailchannels to send which was chosen for convivence but mailchannel's security and such is questionable: https://discord.com/channels/595317990191398933/779390076219686943/1152689451374477483, it also doesn't tell you how to whitelist it at all, nor are there really any good examples in the docs
code itself is questionable