You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At first you need to create a broker. Broker is an object that can communicate to workers using distributed queues.
37
37
38
-
We have differet brokers for different queue backends. For example, we have a broker for [NATS](https://github.com/taskiq-python/taskiq-nats), [Redis](https://github.com/taskiq-python/taskiq-redis), [RabbitMQ](https://github.com/taskiq-python/taskiq-aio-pika), [Kafka](https://github.com/taskiq-python/taskiq-aio-kafka) and even more. Choose the one that fits you and create an instance.
38
+
We have different brokers for different queue backends. For example, we have a broker for [NATS](https://github.com/taskiq-python/taskiq-nats), [Redis](https://github.com/taskiq-python/taskiq-redis), [RabbitMQ](https://github.com/taskiq-python/taskiq-aio-pika), [Kafka](https://github.com/taskiq-python/taskiq-aio-kafka) and even more. Choose the one that fits you and create an instance.
Copy file name to clipboardExpand all lines: docs/framework_integrations/faststream.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ order: 3
4
4
5
5
# Taskiq + FastStream
6
6
7
-
[FastStream](https://faststream.airt.ai/latest/) is a library that allows you to write consumers and producers for different message brokers almost like taskiq. But the differense is that taskiq is more focused on tasks for a specific project and more like celery but async, while FastStream is more focused on events and defining how different systems communicate with each other using distributed brokers.
7
+
[FastStream](https://faststream.airt.ai/latest/) is a library that allows you to write consumers and producers for different message brokers almost like taskiq. But the difference is that taskiq is more focused on tasks for a specific project and more like celery but async, while FastStream is more focused on events and defining how different systems communicate with each other using distributed brokers.
8
8
9
9
If you want to declare communication between different projects you can use taskiq, but it might be a bit more complex than using FastStream.
Copy file name to clipboardExpand all lines: docs/framework_integrations/taskiq-with-fastapi.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,7 @@ async def app_shutdown():
101
101
102
102
```
103
103
104
-
And that's it. Now you can use your taskiq tasks with functions and classes that depend on FastAPI dependenices. You can find bigger examples in the [examples repo](https://github.com/taskiq-python/examples/).
104
+
And that's it. Now you can use your taskiq tasks with functions and classes that depend on FastAPI dependencies. You can find bigger examples in the [examples repo](https://github.com/taskiq-python/examples/).
Copy file name to clipboardExpand all lines: docs/guide/cli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ The number of signals before a hard kill can be configured with the `--hardkill-
112
112
-`--log-level` is used to set a log level (default `INFO`).
113
113
*`--max-async-tasks` - maximum number of simultaneously running async tasks.
114
114
*`--max-prefetch` - number of tasks to be prefetched before execution. (Useful for systems with high message rates, but brokers should support acknowledgements).
115
-
*`--max-threadpool-threads` - number of threads for sync function exection.
115
+
*`--max-threadpool-threads` - number of threads for sync function execution.
116
116
*`--no-propagate-errors` - if this parameter is enabled, exceptions won't be thrown in generator dependencies.
117
117
*`--receiver` - python path to custom receiver class.
Copy file name to clipboardExpand all lines: docs/guide/scheduling-tasks.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ Every time we update schedule it gets task from the source and executes this fun
74
74
Sometimes, you want to be specific in terms of time zones. We have you covered.
75
75
Our `ScheduledTask` model has fields for that. Use these fields or not, it's up to the specific schedule source.
76
76
77
-
Taskiq scheduler assumes that if time has no specific timezone, it's in [UTC](https://www.wikiwand.com/en/Coordinated_Universal_Time). Sometimes, this behavior might not be convinient for developers.
77
+
Taskiq scheduler assumes that if time has no specific timezone, it's in [UTC](https://www.wikiwand.com/en/Coordinated_Universal_Time). Sometimes, this behavior might not be convenient for developers.
78
78
79
79
For the `time` field of `ScheduledTask` we use timezone information from datetime to check if a task should run.
80
80
@@ -85,7 +85,7 @@ an offset of the cron task. An offset can be a string like `Europe/Berlin` or an
85
85
86
86
By default, when you start the scheduler it will get all tasks from the schedule source and check whether they should have been executed in this minute. If tasks should have been executed, they will be executed.
87
87
88
-
This behaviour might be not convinient for some developers. For example, if you have a task that should be executed on every minute, it will be executed once you start the scheduler, even if it was executed a few seconds ago.
88
+
This behaviour might be not convenient for some developers. For example, if you have a task that should be executed on every minute, it will be executed once you start the scheduler, even if it was executed a few seconds ago.
89
89
90
90
To avoid this behaviour, you can pass the `--skip-first-run` flag to the `taskiq scheduler` command. In this case, the scheduler will wait until the start of the next minute and then start executing tasks.
91
91
@@ -163,7 +163,7 @@ Each of these methods return you an instance of the `CreatedSchedule` class. Thi
163
163
await schedule.unschedule()
164
164
```
165
165
166
-
Or it can be done manually, by calling `delete_schedule` on schedule source providing it whith`schedule_id`.
166
+
Or it can be done manually, by calling `delete_schedule` on schedule source providing it with`schedule_id`.
0 commit comments