tgambet/musicalypse

A modern audio player built with Web technologies.

musicalypse's Issues

Enhancement Request - Add option to start with Album view

The current view of ARTIST>>ALBUM>>TRACKS works well but when albums are compilations of various artists, it breaks up the album, so all of the tracks are split up by Artist.

An option for a view of ALBUM>>TRACKS would resolve issue.

Where can I find server installation documentation?

I am trying to install the server version on an local Ubuntu server, and I cannot find any documentation? Please advise...

Joao

auto starting musicalypse in a server enviroment

I am having the toughest time trying to setup Ubuntu 18.04 server to auto start musicalypse, any suggestions?

Adding MP3 gives error server install

If I add mp3 files for the library, it gives this error:

I have tried many different files and same issue... if I remove the mp3 files all is well, this

Musicalypse don't load library when starting

Hello!
I use Musicalypse with snap on Gallium OS.

• The music folder has been added in settings (it's an external hard drive : /mnt...)
• The first scan was OK
• But after reboot, Musicalypse don't load this folder. He just memorizes the last song played.

How to fix it please?
(and : thanks for this beautiful design)

Continuing to set up server :-)

First and foremost, thank you for project, it is fantastic, and I will do what I can to promote your project!

The main thing that appealed to me was the server setup and I really like the way it works, I have a couple of issues that I still need to resolve, plus I would like to explain how I have it set up now.

I created a VPS on Digital Ocean (they call it a Dropplet). Ubuntu 18.04
I created a user "joao" which will be used to configure system using sudo. It is also where I downloaded the server file, it resides in /home/joao/bin/musicalypse/bin/

I installed apache2 and added Let's Encrypt SSL.

I added a A Record on my server pointing to the VPS, the domain name is audio.machado-family.com

accessing the server at: http://audio.machado-family.com:8080 works just fine.

I then decided to setup a proxy reverse/proxy to serve port 0.0.0.0:8080 to the domain https://audio.machado-family.com but all I get is a spinning loading graphic, although it looks like it is Musicalypse trying to load.

The other issue is that I can't seem to figure out a way to start Musicalypse on server boot, but right now that is secondary.

The server is up and running, the links above should be good, if it is down, I am probably restarting the server.

Please provide AppImage for download

Please provide an AppImage for download.

Providing an AppImage would have, among others, these advantages:

• Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
• One app = one file = super simple for users: just download one AppImage file, make it executable, and run
• No unpacking or installation necessary
• No root needed
• No system libraries changed
• Works out of the box, no installation of runtimes needed
• Optional desktop integration with appimaged
• Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
• Can optionally GPG2-sign your AppImages (inside the file)
• Works on Live ISOs
• Can use the same AppImages when dual-booting multiple distributions
• Can be listed in the AppImageHub central directory of available AppImages
• Can double as a self-extracting compressed archive with the --appimage-extract parameter

Here is an overview of projects that are already distributing upstream-provided, official AppImages.

electron-builder can do AppImages easily.
If you have questions, AppImage developers are on #AppImage on irc.freenode.net.

Enhancement Request - incorporate a simple user and password

I would like to request and enhancement, to provide the GUI with the option of simple user and password for the server version, or maybe for all versions. I would leave the default as disabled.

My use case is on the server, once it is setup and running using proxy server with SSL, the apache authentication no longer works, it seems to be a better option to just have it built into the interface.