arionmiles/diomedes

Email alerts for your favorite movies about to hit theaters

diomedes's Issues

BMS Trending Movie suggestions

Use BMS Trending/Quickbook to suggest similar named movies (ask region before showing add-movies view, store it in cookie and pass to the model form)

Limit the input to the suggestions only.

Create Footer

Footer should contain link to the repository, etc.
Put more stuff here when you think of it.

A new database model (Reminder) to allow selection of specific theaters in the locality.

Migrate database to PostgreSQL first.

Use the ArrayField to store Venue Codes of the selected theaters.

On the web form, allow users to add theaters (show them Venue Names, instead of Venue Codes), add the corresponding venue code of the theaters selected by them.

Improve Search criteria (Remove search_count field)

Instead of searching N number of times, search until we're past the date set by the user.

find_movies()

if task.search_count > config.SEARCH_COUNT_LIMIT: 
# timezone.localdate() > task.movie_date

Also, when selecting unfinished tasks, use:
find_movies_job()

unfinished_tasks = Task.objects.filter(task_completed=Fale, dropped=False, movie_date__gte=timezone.localdate())
# test timezone.localdate() on production machine first

This should remove the search_count field from the model Task.

This feature will remove the following dependency:

• django-constance

Improve Job Scheduling setup

Current setup uses django-rq along with Redis and works as a Django management command.

monzo/response runs their cron jobs like this:

1. Create an endpoint which runs the job function on receiving a request.
2. Run cron in a container which hits that endpoint at whatever interval you want.
   https://github.com/monzo/response#quick-start

This setup will remove the following dependencies:

• django-rq
• rq
• rq-scheduler
• redis

And remove the Redis container, replacing it with cron container, and make it a whole lot easier, certainly less convoluted.

Additionally, create a model which stores results/exceptions of every job run for inspection later, when something goes wrong (which it will...)

Take a look at the Dockerfiles in the response library for reference.

Use Caddy instead of Nginx

Caddy has automatic HTTPS with LetsEncrypt, can also serve static files.

Current Nginx-Certbot is very tiresome, the script init-letsencrypt.sh is not very reliable, since the links to TLS parameters change very often.

Using Caddy container with a custom Caddyfile would be the best solution.

Integrate Telegram social login

Telegram Social login will allow us to send notifications on telegram to the user.
https://telegram.org/blog/login

django-allauth supports Telegram login: https://django-allauth.readthedocs.io/en/latest/providers.html#telegram

Social login will allow the bot to communicate first to the user.

Can use telegra.ph to form the message with showtimes info, allowing telegram users to see the data with Telegram's Instant View.

Figure out a way to know if a user logged in via telegram or email, store this info in the database, and appropriately direct the notification to the corresponding platform. Maybe even generate the email/telegraph depending on the method of login used.

Any/All Dimensions option

Allow users to get reminders for any dimensions available.