Hello everyone!
I’m thrilled to be back here again! In case you’re not familiar with YAMS, YAMS (Yet Another Media Server) is a powerful script that simplifies the installation of a comprehensive media server. It includes all the essential *arr apps, along with exceptionally detailed documentation. In just a few minutes, you can have a fully functional media server with Sonarr, Radarr, Jellyfin, qBittorrent, and more! To learn more, you can visit the following links:
- Reddit thread: YAMS on r/selfhosted
- YAMS Website (featuring its cool documentation): YAMS Website
And now, I’m excited to announce the release of YAMS v2!
What’s New in YAMS v2?
- YAMS v2 introduces a new command: yams upgrade, which allows YAMS to upgrade itself.
- Adding custom containers is now easier. You can find a step-by-step tutorial here: Add your own containers.
- On the code side, the documentation has seen significant improvements. If you’re interested in how YAMS works under the hood, you can explore the full code documentation here: YAMS Code Documentation.
Upgrading to YAMS v2 is entirely optional! YAMS v1 will continue to work and receive support.
Starting now, every new YAMS installation is automatically YAMS v2!
In other news, I’ve also established a dedicated forum for all things YAMS related! After noticing that many users were encountering similar issues, we concluded that a forum would greatly enhance troubleshooting, making it more accessible, searchable, and enjoyable.
Feel free to visit the new forums at YAMS Forum. Don’t hesitate to drop by and introduce yourself!
For those interested in YAMS, there’s a comprehensive tutorial on how to configure all the services together: Services Configuration Tutorial. The tutorial is designed to be platform-agnostic, so even if you’re not using YAMS, you might find it useful!
Thank you for taking the time to read this, whether you’re already a loyal YAMS user or are considering becoming a new YAMS enthusiast! Your feedback and insights are highly valuable to me, and I’m eager to hear what you think!
Its called “yet another media server” but it isnt a media server? But a collection of script to setup *arr stack and jellyfin for example? Sure thats useful to many, its great! But odd namechoice :D
To me, all these collection of software are what make a great Media Server, and that’s what mostly everyone in the community uses. Also, “YAMS” is a funny name lol. Thank you for your feedback though!
I mean, if a media management suite + media server cant be called a ‘media server’ then what exactly are the criteria?
Uhm a “media server” is called a “media server”, simple?
A suite or collection of tools is not a “media server”.
Yes the title is a bit misleading, it should be “yet another install script for media server”
Cool, thanks for the info!
Thanks! If you encounter any issues, please let us know in the forum or the Matrix chat!
Did you make yammm for windows media center?
Couple of things would be great to see.
A reverse proxy setup for remote connections.
A custom format explanation/setup for radarr, and maybe going with sonarr v4 to also get custom formats. Perhaps using recyclarr to import custom formats from trashguides. Currently the setup only goes over adding a download client and media renaming. Would be nice to explain to people how to grab the quality of movie or show that they want.
A usenet download client/setup like sabnzb.
A qbittorrent setup for people who use private trackers and need to seed. And a setup that includes hardlinks so radarr/sonarr can move and rename without messing up seeding.
I know you can add your own container, but a setup for request app like jellyseerr or overseer would be great as well.
Have you looked into using buildarr, to deploy the arr stack? It can be fed a default setup so people wouldn’t have to touch a thing, it would be ready out the gates? Especially if recyclarr was incorporated to import custom formats.
Someone on this thread mentioned my project, which is very rough around the edges, but was definitely inspired by yams. I’m currently working on a massive revision, but I’ve got some life things going on that have stalled progress, but it will incorporate all the things I listed above plus a little more ideas i got brewing. Working on a powershell gui at the moment to switch away from .bat scripts. Thanks u/Rogergonzalez21 for the shoutout.
YAMS is fantastic. I’ve tried so many and the best communities are YAMS and CosmOS. Very passionate group that go way beyond helping you out.
YAMS rocks! Always reliable and simple.
Thank you! I’m really glad you like YAMS. If you have any suggestions and/or feedback! Please send it my way!
I want a cool YAMS sticker for my laptop. I have a spot for it between Crowdstrike and Splunk (swag!!).
I was thinking about making some stickers… Maybe that can be done later? 🤣
does the way folders are set up by yams support auto moving/deleting duplicates /renaming torrents from the torrent client client without duplicate files (sonarr /qbitorrent)
i would love to set and forget .let anime download and watch it in jellyfin
i always strugle with sonarr and qbitorrennt not liking me folder structure
This is actually one of my use cases! So it definitely works.
I configured YAMS as usual and then used TRaSH Guides to configure it for Anime, you can check it out here: https://trash-guides.info/Sonarr/
Any way to get the script to run on Raspberry Pi Bookworm? Seems to fail with: “Error response from daemon: Get “https://lscr.io/v2/“: EOF
YAMS needs a 64bit OS to run. Are your running Raspbian 64 bits?
YAMS rocks, best community ever!
YAMS all the way!
Yeah! YAMS all the way! Haha
Great work! Didn’t have the time to create a PR for it so I’ll write it here: In the docker compose file you generate, the qbittorrent environment name for the port seems to be wrong, it’s supposed to be WEBUI_PORT not WEB_UI_PORT.
Oh, nice catch! Would you mind creating a new issue in Gitlab? If not don’t worry, I can create it late it later! Thanks for the feedback!
I created one, thanks for the great work again!
Why do you call it a media server (on the homepage) when it’s actually just an install script for a media server? You call it an install script truthfully here
Have you considered pasting this entire description on your website? As it stands, there’s only a one line description, and then installation instructions, but nothing about what the software is, what kinds of problems it can help with, and why a potential user should care. Thanks!
Also, you can read what YAMS is here: https://yams.media/install/description/
But I’ll add a link to it in the homepage!
Ok, this is actually a good idea! Thanks, I’ll do that later today! Thank you for your feedback!
It’s just a script that throws a handful of preconfigured config files together, but that should really be (honestly, too) written on the page
I’ll do that. Thanks for the suggestion!
The only minor issue that I have day to day is endemic of a monolithic yaml. making small changes to the .yaml file needs to restart the entire stack. Also Some errors will stop the entire stack from deploying.
YAMS v2 fixes this issue! Now new containers go in their own docker-compose file, and there’s some new instructions on how to do that here https://yams.media/advanced/add-your-own-containers/
Why don’t you allow external contributors in the repo?
I do accept external contributions, and as a matter of fact, I encourage it! I’ve merged others people’s code! For example, Lidarr and Readarr where added by people in our community.
Merge Requests are always open for YAMS. To contribute, just fork the APP to your Gitlab account, make changes and create a MR into YAMS, like any other open source app.
I should create a guide on how to collaborate. Thanks for the idea!