4 ms·
We've just launched in developed preview, so no pricing yet, but this is coming! A good starting point to answer your other questions is the "getting started"
by achille-roussel 3y ago
We've just launched in developed preview, so no pricing yet, but this is coming!
A good starting point to answer your other questions is the "getting started" section in our documentation https://docs.dispatch.run/dispatch/getting-started https://docs.dispatch.run/dispatch/getting-started
If you have more questions, join our Discord! We're always happy to chat and get feedback on what's difficult to grasp.
- gigatexal 3y agoFor me this is DOA unless it can be run locally without having to call into some hosted API in the cloud. I took a gander at the source I'll wait till/if there's ever a 100% local version of this. But good luck all the same!
- achille-roussel 3y agoI guess this is your lucky day, because you can already run it locally! Take a look at the "Local Testing" section in the README of dispatch-py https://github.com/stealthrocket/dispatch-py?tab=readme-ov-file#local-testing https://github.com/stealthrocket/dispatch-py?tab=readme-ov-f... TLDR: python -m dispatch.test http://127.0.0.1:8000 http://127.0.0.1:8000 This is just a mock implementation but it lets you test your code and experiment with the solution.
- gigatexal 3y agoStill production means sending my data to a hosted cloud black box? I can’t host this myself?
- achille-roussel 3y agoYes, today the deployment model for production is to connect to a cloud service for the scheduling. You still run the code yourself, but the SDK needs to connect to the backend.