• Header with different buttons available .
• #6
• #5

Storing large binary files, such as font files, directly in a version control system like Git is generally not recommended. Git is optimized for handling source code and text-based files, and large binary files can significantly increase the repository size, slow down cloning and fetching operations, and make the repository more challenging to manage.

Here are some alternative approaches you can consider:

External Hosting:
For large binary files like font files, it's common to use external hosting services. You can host your font files on a CDN (Content Delivery Network) or a dedicated file hosting service. Then, in your web project, you can link to these external resources using URLs.

Package Managers:
For frontend projects, you might consider using package managers like npm or Yarn to manage your dependencies, including fonts. Many fonts are available as npm packages, and you can include them in your project using package.json.

Git LFS (Large File Storage):
If you need to keep binary files in your Git repository, consider using Git LFS. Git LFS is an extension to Git that handles large files separately. It replaces large files with text pointers in your repository, and the actual binary files are stored on a Git LFS server.

To use Git LFS, you need to install the Git LFS client and enable it for your repository. Then, you can add and track large files using git lfs track before committing.

Here's an example of using Git LFS for a font file:

bash
Copy code

Install Git LFS (once per machine)

git lfs install

Track a specific file type (e.g., .ttf)

git lfs track "*.ttf"

Add, commit, and push the changes

git add .
git commit -m "Add font files using Git LFS"
git push origin master
By using one of these methods, you can manage large binary files more efficiently and avoid bloating your Git repository. Choose the approach that best fits your project's needs and constraints.

• Filter on country
• Quality (SD, HD, FULL HD)

Create a simple website for uploading playlist.
List (m3u-file) should be uploaded to a database and then be accessible with some kind of authentication for the user on the TV.

There are errors if playlist is not found and navigation gets fucked up

• Write error messages on inputs if user is doing something wrong
• Write error messages when uploading playlists if something goes wrong + no connection