mahadana / pujas.live Goto Github PK

will want to make a scroll speed control in some form or another.

Also, might as well consider having a "default audio file" associated with each chant so if you want, you can have the audio play as it scrolls

When playing a video or browsing a list of recordings, the modal state does not modify the browser history so the back/forward buttons do not work as expected.

We would like to add contextual routes for these modals.

should find a good "brown" forest image too!

We would like to add a feature where specific recordings can be selected for a channel and would be made public in the home page "Livestreams" list.

(abhayaparisa, portland friends of dhamma, etc)

Add a worker check functionality that will send an email if exceptions persist for > 1 day.

We have a curated list of recordings but it would be good to surface the latest recordings captured by the automation.

Occasionally one of the unit tests fails. See the following:

  ● channel › services.find(_sort=_activeStreams)

    expect(received).toEqual(expected) // deep equality

    - Expected  - 1
    + Received  + 1

      Array [
        "3",
    -   "1",
        "2",
    +   "1",
      ]

      52 |     expect(_.map(result, "title")).toEqual(["1", "2", "3"]);
      53 |     result = await strapi.services.channel.find({ _sort: "_activeStreams" });
    > 54 |     expect(_.map(result, "title")).toEqual(["3", "1", "2"]);
         |                                    ^
      55 | 
      56 |     done();
      57 |   });

      at Object.<anonymous> (tests/channel.strapi.js:54:36)

A channel removed its activeStream for a short period of time. At around 7:02pm, the assigned activeStream went to null, then recovered about five minutes later.

The following was found in the worker logs:

worker_1    | Pass 2: get YouTube video ids from channels
worker_1    |   channel id = 1, title = Abhayagiri Daily Evening Puja livestream
worker_1    |     ytChannelId = UCFAuQ5fmYYVv5_Dim0EQpVA
worker_1    |     videoId = _zQBnKs6fgI

Then...

worker_1    | Pass 2: get YouTube video ids from channels
worker_1    |   channel id = 1, title = Abhayagiri Daily Evening Puja livestream
worker_1    |     ytChannelId = UCFAuQ5fmYYVv5_Dim0EQpVA
worker_1    |     videoId = false
...
worker_1    | Pass 4: update channels with latest data
worker_1    |   channel id = 1, videoId = false, title = Abhayagiri Daily Evening Puja livestream
worker_1    |     removed activeStream from channel id = 1

Then, 3 minutes later...

worker_1    | Pass 2: get YouTube video ids from channels
worker_1    |   channel id = 1, title = Abhayagiri Daily Evening Puja livestream
worker_1    |     ytChannelId = UCFAuQ5fmYYVv5_Dim0EQpVA
worker_1    |     videoId = _zQBnKs6fgI

Some code is shared between backend, frontend and worker. It would be good if there was a way to DRY-up this code.

Currently the database and uploads in production lives in Docker volumes. It would be good if this data were backed up somewhere.

youtube video: https://www.youtube.com/watch?v=jSegDnC7-ww

We would like to capture plausible events for additional user actions:

• opening a livestream
• opening a chanting book

also capture the straight chanting book page

ideally good visual skills with web ui/ux background

Caddy is easier to configure vs. Nginx.

day 5 chanting starts at 57 minutes. Not right. Jeff to handle. Anapanasati also not working, maybe not embeddable

Having overridable data in curated recordings adds unneeded complexity. Let's move skip from curated recordings to recordings table, remove optional title, description from curated recordings.

The worker log is buried in docker and it would be nice if this log (and other logs) could be made more publicly available.

help users understand

Currently the worker job that updates the YouTube automated recordings and channels is limited to processing 50 YouTube videos. At some point (soon) this will result in breakage.

The recent recordings is showing livestreams as well as curated recordings. We want remove those from the list.

help the user know which are embeds, which are not

We would like groups to automatically hide after some amount of time has past without any updates by the group owner.

One possibility is to add a worker task to check updated_at on a group. If it’s older than a threshold (e.g., 1 week), then send an email to the group owner, and ask them to do something (e.g., click on the edit group link), otherwise, the group will automatically hide after a second threshold (e.g., 2 weeks).

add "Recorded Pujas -- [monastery name]" in title
make image/row smaller
use image from recording instead of default image (or default to channel image if no image)

Currently information about the upcoming stream can only be viewed by going to the stream. We would like to add a preview of the upcoming title (just a few words with an ellipse), then if you click on that you get a popup with a fuller preview of the upcoming stream including thumbnail, title, description, and date/time.

We would like to add an optional field to add a skip time (in seconds) to curated recordings.

i think it might just be because they "stream" them in the background, but don't actually livestream them