Skip to content
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

Scheduler informationen added #142

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions web/docs/google-cloud/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -267,6 +267,12 @@ The following command should only be used once.

### Scheduler

The Scheduler plays a crucial role in the functioning of the Sync Server within the Tide infrastructure. It is responsible for managing scheduled tasks related to syncing data from the WordPress.org Themes and Plugins APIs. Users may choose to deploy or delete the Scheduler based on their specific needs and operational requirements.

The Sync Server is tasked with consuming data from the WordPress.org plugins and themes API. The Scheduler, as an integral component, orchestrates this data ingestion process. It periodically makes requests to the WordPress.org APIs to determine whether any changes, such as new versions or updates, have occurred since the last scheduled request. When executed, the Scheduler generates messages that are added to a Pub/Sub queue associated with the relevant Report Server. These messages trigger the asynchronous processing of data by the Audit Servers, ensuring the timely update of information related to WordPress themes and plugins.

In summary, the Scheduler is pivotal for keeping the Tide environment synchronized with the dynamic landscape of WordPress.org themes and plugins. Whether deploying it for regular updates or deleting it for more selective syncing, users can tailor the Scheduler's presence to align with their specific requirements and preferences.

Deploy the Scheduler for the Sync Server:

make deploy.scheduler
Expand Down