Description
Parbin is currently only taking suggestion for events as manual entries, meaning that it relies heavily on either the admin, event promoters, or normal users to keep a list of tech events up to date.
In order lift some of the responsibility to these parties, many options have been brain stormed so far, and the project will start with a scraper that gathers event info from curated sources and suggests them to the admin in order to appove or reject them. This scraper is meant to run on an agnostic cron job provider.
Proposed solution
A playwright scraper is being considered, this solution will be allocated into a new root level dir called jobs (to be expanded upon later) and will include the steps to be self installed and executed standalone from the rest of the project (understanding that the backend must be available in order to send the event and gather exclusions as to not repeat past suggestions)
Description
Parbin is currently only taking suggestion for events as manual entries, meaning that it relies heavily on either the admin, event promoters, or normal users to keep a list of tech events up to date.
In order lift some of the responsibility to these parties, many options have been brain stormed so far, and the project will start with a scraper that gathers event info from curated sources and suggests them to the admin in order to appove or reject them. This scraper is meant to run on an agnostic cron job provider.
Proposed solution
A playwright scraper is being considered, this solution will be allocated into a new root level dir called jobs (to be expanded upon later) and will include the steps to be self installed and executed standalone from the rest of the project (understanding that the backend must be available in order to send the event and gather exclusions as to not repeat past suggestions)