-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add instructions to enable paid workers plan #104
Conversation
Workers plan is required to enable queues
As a note, this kinda makes a huge difference in the appeal of running Wildebeest without a bit more info. Images being set-tier pricing means I don't have to worry about suddenly surprise bills when Elon Musk drives a ton more traffic to the fediverse at random. Adding a requirement of a pay-as-you-go offering is a huge impact. I'm interested in potentially using Wildebeest, but I do not have spare funds for experiments, so I probably need at least a good faith expectation of how much running it will cost me. Perhaps some of the CF employees running it in production can provide enough numbers to estimate the consumer cost? |
@jonikanerva did you intend to close this? |
Ah no! I forgot I still had this PR open and deleted my fork. 🤦 |
FYI, Images is PAYGO pricing after your included usage - there is no cap, it'll be the same model as a Workers paid plan. |
I don't think anyone said this would be free as in beer. You are consuming resources that must be paid for by someone. Overtime it will be interesting to see what actual costs are for a single user instance. |
Sure - I was just saying that 'Images being set-tier pricing means I don't have to worry about suddenly surprise bills' is incorrect. |
@AndyNortrup Definitely not concerned about paying for hosting, am just concerned about cost control/predictability. |
Since the README has been rewritten is that change still needed? |
Workers plan is required to enable queues