Implement functionality to calculate salary.

1. If fetched salary is net, transform it to gross.
2. If fetches salary is gross, transform it to net.
3. Also there are cases there salary is provided by hourly rate.
4. Check if there are any yearly rates.

Provide full salary information for user.

1. Create job application and restructure functionality according to it.
2. Rename tasks.py according to scraped website.
3. Move renamed scraper file to newly created directory (e.g. sites/modules)

Scrap cvbankas job offers by category.

Implements back-end functionality for search boxes.

• Add category field for searching.
• Add Lithuanian cities

Move parsing from tasks.py to some other file - "parser", "processor"?
Implement all code from functional to OOP?

Create cv.lt scraper

Write unit tests for salary calculation service.

• Swap prints with logging.
• Add additional logging.

ref.: https://docs.djangoproject.com/en/5.0/topics/logging/

Sort job offers by:

1. Date
2. Salary

Add new page with chart of job offer count in each category.
Use chart.js

Add type hints to codebase.
Install django stubs.

Scrape cvmarket job offers.

Right now scraped data is saved to list as elements of dict.
After each iteration of data it is saved to database.
Need to create objects first and save it as bulk_create.

Reference: https://stackoverflow.com/questions/64046422/django-save-multiple-objects-at-once

Remake current "cvbankas" scraper to work asynchronously.

Currently cvbankas 1 page is scraped in ~40second synchronously:

[2024-01-18 22:21:50,890: INFO/ForkPoolWorker-3] Task job.tasks.scrape_and_save_job_offers[487ce137-6724-4198-90c6-6e8f1cfd2d58] succeeded in 39.70813476400508s: None

Run celery task: celery -A darbas24 worker -B -l INFO

Warning:

[2024-01-31 11:53:40,249: WARNING/MainProcess] /usr/local/lib/python3.12/site-packages/celery/worker/consumer/consumer.py:507: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
whether broker connection retries are made during startup in Celery 6.0 and above.
If you wish to retain the existing behavior for retrying connections on startup,
you should set broker_connection_retry_on_startup to True.
  warnings.warn(