lyoko 4mo ago • 100%
I have the same problem with navidrome so I've written a new Opensubsonic server in Rust with a permision model. You can check it out here: https://github.com/vnghia/nghe
lyoko 6mo ago • 100%
Sorry to make you feel that way. You are the first commenter and the first star on github so I am really appreciate it. "Nghe" could be decompose into two parts: "ngh" and "e". The "e" part sound like "eh" but the "ngh" part is just "difficulty level: asian" so I put a video here: https://www.youtube.com/watch?v=ttA8ukm8lwI ("ngh" and "ng" have the same pronounciation). Thank you very much!
lyoko 6mo ago • 100%
Thank you! I just want to make my server as much cross-platform as possible :D
lyoko 6mo ago • 100%
Not sure what do you mean by filtering but this is my Symfonium UI
lyoko 6mo ago • 100%
In the opensubsonic response there will be two fields for artist, one is artistid with only one artist (this is for compatible with old subsonic) and the other is artists with a list of artist ids. The server only sends back the list of artists ids and only these two clients read that field.
lyoko 6mo ago • 100%
I am trying adding a FreeBSD CI. Will let you know later if it is working or not
lyoko 6mo ago • 100%
Thank you! Please give it a try and give me some feedbacks XD
lyoko 6mo ago • 100%
Thank you very much for your kind word! I've seen that scanner already but decided to reimplement anyway because I want to choose a different design from the start and have the flexibility to add some new features myself (some kind of ML integration like immich and S3 integration). At worse case, I will still use this so no problems :D
lyoko 6mo ago • 100%
Is Rust that much better than Go?
IMHO, rust and go are two differents things. The reason I choose Rust is because it is fast and calling C code from rust is supported really well since Rust's goal is to become a system language. Navidrome is just calling the ffmpeg binary. While in my project, I've compiled the neccessary parts of ffmpeg myself (thanks to vcpkg) and call the function directly from Rust. It leads to smaller and fully static final binary (because no ffmpeg bin) as well as faster transcoding time since we don't have to wait for the ffmpeg binary to finish transcoding the whole file before load the result from the filesystem to the memory.
Would it have been impossible to submit your changes to Navidrome as pull requests?
You can see here. This is the biggest reason why I've decided to start my own implementation. Beside, I share my server with several friends so I want a mechanism to prevent mixing musics from different people.
Does this import the Navidrome database?
This could be a feature request in the future. I could add a python script to import users/songs/playlists/playcount/etc from Navidrome.
lyoko 6mo ago • 100%
I see. Indeen I gave up teaching people pronounce my name correctly long time ago and told them just to call me by my family name so you coulld pronounce whatever you like. If you know a Vietnamese guy around just ask them to teach you and give them a headache
lyoko 6mo ago • 100%
Never thought about it. Is there an inside joke am i missing @@
I am selfhosting Navidrome for sometimes but its lacks of support for multiple values really bugs me. Since I am having some free time, I've decided to write an opensubsonic server in rust (why rust? [you guess](https://github.com/ansuz/RIIR)). The notable features are: - In-memory transcoding with ffmpeg c api. Faster transcoding with no ffmpeg binary required and no need for pre-configurated transcoding profile. - Multiple values for artists/album artists/etc. - Permission models music folder per user. It is still actively developped and lacks some Opensubsonic features (playlist/starr) and some external integrations like lastfm. However I would like to post it get some feedback about it. Thank you very much!
lyoko 11mo ago • 100%
In my experience, I found that rclone mount
a crypt
remote is not as stable as a direct mount. But I will try to do it again. Thank you very much !
lyoko 11mo ago • 66%
I found something for AWS here but not sure about the rest https://www.reddit.com/r/aws/comments/hxfjwl/does_aws_ever_scan_s3_buckets_for_known_copywrite/
lyoko 1y ago • 100%
I usually try different custom ROMs and have to format my phone frequently. Will that eSIM survive that format or not ?
lyoko 1y ago • 100%
How do you keep your Spotify recommendations update ? Don't you have to listen to songs on it to get updated recommendations ?
lyoko 1y ago • 100%
That sounds like what I need. Thank you very much !
lyoko 1y ago • 100%
so you are also generating the docker-compose from code. I think I am looking for something that aware of both templating and docker-compose deployment because right now, at the end of the day, I am still have to run docker-compose up -f ...
while helm
can do both templating and deployment.
Maybe this is a little bit off-topic. I would like to ask how you manage your dockerfile. I have a git repo hosting my configurations (docker-compose, traefik, etc). Then, I have a python script that reads data from JSON, renders the placeholder inside these files (the `{{replace_me}}`) by an actual value and outputs them to another directory. Finally, I `cd` to that directory and run `docker-compose up -f ...`. (This approach takes inspiration from the `terraform` `templatefile`) That JSON file is generated by some terraform code, along with terraform code for other stuffs (storage bucket, vps, dns, etc). It works well for me so far. Especially for: - templating `traefik toml` configuration (I like it a lot more than the label approach). - secret in the docker env file (so my docker.env file has the form of `secrect={{secret}}`. I know most templating docker part can be replaced by directly interpolating with environment variables but I don't really like it because it seems environment variables are not persistent. Do you have any suggestions for my workflow ? I am always feel a litte bit off about this approach. Edit: Thank you for your suggestions. I will try `k8s` for edge computing and if it does not work really well, I will stick with my current approach.