What is the best way to handle this?

Do we deploy once so the image is live, then while there is no data, we shell into the box that is hosting the image and shell into the container. From there we log into the postgres cli and create username and password with appropriate rights and lock down db access from anywhere else.

Then the data should be set on that server because it's volume bound to the image and from there on out we set everything to the creds we just assigned to that new user when we connect for production.

Am I overthinking this?

Can we set this stuff in a config somewhere instead, or in the docker-production.yml file or something?

@AlphaRecon19 @DominicWatts @dstuessy @Decad

Rewrite front-end collapsible table behavior.

Needs to be responsive.
Cannot have gap at bottom.
Has to adjust to content amount (as in, no unnecessary gaps).

Would be good in login form

Create a blog page within medley where we can make announcements and keep track of other repo-related things.

Chrome & FF

Switching between users in index vue resets track index.

To solve store track and recalculate index on user switch. Like that tracks will keep playing as before.

Will increase load a little bit so if there is a better way of doing this please suggest.

I'm thinking people should be able to add to their own lists as they want.

But since user lists point to track table, we can't just immediately add their stuff.

I suggest creating a temptrack table where users see their stuff as soon as they add it.
But other users don't see temptracks -> and then we cronjob some process where admins approve the submission - making sure that the video is a song, the artist and song name as well as the genre is correct.

Then once approved, remove from temptrack, add to track, and job done.

This will not scale indefinitely but I don't censorship ever does without making tons of assumptions.

Shuffle needed

Error in initial load

Feel like I've inadvertidely missed a step