peter-lam / climbr Goto Github PK

Replace requirements.txt and pip setup with poetry to manage dependencies. Set up nox to manage linters, saftey checks etc.

Also fix any linting issues

When a user books through RGPro, can a log file be automatically generated and filled with the location and date? Maybe something to read emails?

Since all containers now run off 1 docker-compose file, there is not longer a need to have a seperate env variable for docker vs non. Use localhost:xxx instead of http://host.docker.internal:

ValueError: invalid literal for int() with base 10: 'Full. Please make a different selection.'
Session info successfully retrieved! See information at '/workspace/data/output/bookings.json'

Also, if it's the last session of the day and it's full, then it will skip to the next day

On a fresh clone, poetry lock isn't present so there is a error when running docker-compose. Need to find a better solution than this and also duplicating the pyproject.toml....

Instead of having to change the input logic when something changes, like the booking from (capacity gauge VS reservation), convert the Booking dictionary to class and standardize the inputs/outputs

Create a dashboard to summarize the climbing year. Things that would be useful

• Climber count, who did you climb with the most this year?
• Breakeven: Did you break even for your membership? Did other climbers?
• Hardest grade
• Mostly climbed location

Since "Logs" and "Output" directories are ignored by git, the app needs to make these directories if they don't exists. Currently a fresh install results in an error like:

PS E:\GitHub-Projects\climbr-dev-work> poetry run cli export
Retrieving dashboards and related objects...
Exporting Kibana dashboard and objects...
Traceback (most recent call last):
  File "E:\GitHub-Projects\climbr-dev-work\common\common.py", line 383, in export_kibana
    with open(output, "w+") as file:
FileNotFoundError: [Errno 2] No such file or directory: 'E:\\GitHub-Projects\\climbr-dev-work\\data\\output\\climbr_2021-10-25_19-11-35.ndjson'

During handling of the above exception, another exception occurr

A list of climbers should be used to populate all templates. Maybe leave this in the config file

Run Nox in Github Actions to check linters, safety on every commit. Prevent merge if doesn't pass tests

Combine webscraper and main project docker files and docker-compose files. These should sit at the top odf the directory,
To restart the webscraper specifically, use: docker-compose restart webscraper or to rebuild the 1 service use: docker-compose up --detach --build webscraper

Since other gyms in Montreal and Toronto use RGPro, try to see if the webscraper is robust enough to support other gyms without major maintenance.

Helps with easily reading jobs and making edits when gyms change their schedules: https://stackabuse.com/scheduling-jobs-with-python-crontab/

How many hours of climbing did I do in the past month? week? year?

Currently hard to tell what exactly the error is

Add fields and support for workouts when logging a climbing session

If the user runs "demo" command first and then starts to populate their own data. Runing the "Update" command should either warn the user or auto delete demo files

Check for *demo.njson in the ES folder if user uses regular "climbr.py update". If present, should prompt user about deletion

As climbing gyms begin to remove capacity limits and reservation systems, create some new and update existing visualizations to give climbers a reference point when going to gyms in the future.

What already exists:

• Popularity by gym & time slot
• Relative to the current capacity
• Booking by weather

What could be helpful for the future:

• Popularity by gym & regular time intervals (every hour)
• Add a field to data points to show the % full based on the capacity of that time
  • For example: 50 bookings in March when the capacity was 50 ppl means 100% capacity, where as now it's like 50%
• Update jupyter graphs for weather trends
  • How do other variables influence how busy a gym is (weather, time of the year, events, lockdown)
• Bonus: Highlight and graph the differences in popularity based on lockdown rules
  • For example: 1st return from lockdown, 2nd ....
  • This would be more accurate if curious on data based on the limit but not 100% needed

Move related files into a subfolder. For example. /common/args should be in the CLI subfolder.

Idea is to clean up the project into sub folders per program:

• Climbr CLI
• webscraper
• Climbr API

Need to send an alert that there are more reservations than the current capacity. Likely the coded capacity has changed

More to enhance readability since os.path can be pretty long and less intuitive to write