#newbie yaml clarification

1 messages · Page 1 of 1 (latest)

stray frost
#

So, I just joined the PMM family recently and have been playing around with it. I am running unraid/docker, watched ibracorp video for pmm many times. Also tried to dig through most sections on the main site. I actually built up a full yaml several times, then also deleted a few collections and started over just to see how things work. I currently have everything in the config.yml did i misss something on the site that shows examples or a tree of what how the yml info should be separated? like what all separate yml files are best practice?

btw, love the script so far.

fallen lagoonBOT
#

Welcome @stray frost!

It looks like you have not yet completed #938455615741775902, this will allow us to help you quicker.

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

flat whale
#

hmmm... sometimes I wonder if teh ibracorp video helps more than hurts

#

so... have you done our walkthrough yet?

#

thats teh unraid one

#

its really good at walking you through a lot of this

#

and then i would start looking at the defaults as you can easily pick and choose items you want to include in your config.yml file and not have anything to do with external yml files that you need to maintain... we handle the defaults which are quite vast

#

using a good editor is recommended

subtle obsidianBOT
#

We highly recommend to use a decent editor software to manage PMM's .yml files.

Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that PMM cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
PMM requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in PMM.

This can save a lot of time and headaches.

Visual Studio Code (Windows/Mac/Linux, Opensource & Free)
Website

Notepad++ (Windows only, Opensource & Free)
Website

Sublime Text (Windows/Mac/Linux, Paid)
Website

For further details and a short list of highly recommended extensions, you can also take a look here.

flat whale
#

personally, VSC with indent-rainbow plugin is fantastic

#

finally, dropping your meta.log file in here will have the luma bot scan it to provide some recommendations and help with some basic stuff.

fallen lagoonBOT
#

Would you like more information on how to provide a log file?

#
Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯_(ツ)_/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

stray frost
#

yeah, i have kinda used the vids loosely as most of his and space invaders are kinda older, and the docker aps have changed quite a bit. i did see that page, based on that is it recommended for just a config and library.yml? or is that just so you kinda get to know them, and then start breaking them out even further?

#

i use sublime

#

dang, bots are that good now?

fallen lagoonBOT
#

📝 Great! Let's start to review and make recommendations, sydeburnz... 📝

#

📝 If you want to review this again, sydeburnz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**People Poster Scan Results**

Missing People (No TMDB Image)

These are people found in the attached log we do not have a pre-made poster for and we cannot detect a TMDB image to use as a source for creating a poster:

  • James Foley
    ✉️ People Poster request sent on your behalf to: #1110266071849652335 ✉️
stray frost
fallen lagoonBOT
#

📝 Great! Let's start to review and make recommendations, sydeburnz... 📝

#

📝 If you want to review this again, sydeburnz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**User Info**

Author of Linked Message: sydeburnz
Person who Invoked the Command: sydeburnz
File Name: meta.log

Table of Contents

Page 01: User Info
Page 02: PMM Info
Page 03: PMM Config.yml YAML Validation
Page 04: WIP - PMM Config.yml Schema Validation
Page 05: People Poster Scan Results
Page 06: Plex Configuration - Section 1
Page 07: Plex Configuration - Section 2
Page 08: Plex Configuration - Section 3
Page 09: Plex Configuration - Section 4
Page 10: Rec 01 - 💬 CONVERT ERROR
Page 11: Rec 02 - 💥 INTERNAL SERVER ERROR
Page 12: Rec 03 - ❌ OVERLAYS BLOAT
Page 13: Rec 04 - 💡️PLEX DB CACHE ADVICE
Page 14: Rec 05 - 🚫 PLEX LIBRARY ERROR

stray frost
#

cant seem to get a letterboxd collectin to show up

#

this is what i changed it to based on uploading my meta.log and the 'recommendations'

flat whale
#

So the internal server error is gonna be tricky…most of the time.

#

Pg 12 and 13 should be easy fixes

#

Pg 14 likely has ideas about why there is a library error.

#

That image is inside your config.yml?

#

Let me rerun luma logscan on the last log you submitted

fallen lagoonBOT
#

📝 Great! Let's start to review and make recommendations, bullmoose20... 📝

#

📝 If you want to review this again, bullmoose20:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**Rec 05** - 🚫 **PLEX LIBRARY ERROR**

🚫 PLEX LIBRARY ERROR
Your configuration contains an invalid Plex Library Name.
PMM will not be able to update a library that does not exist.
Check for spelling case sensitive and ensure that you have show_options: true within your settings within config.yml
For more information on configuring the show_options, `https://metamanager.wiki/en/latest/config/settings.html#show-options]
4 line(s) with PLEX LIBRARY errors. Line number(s): 938-939, 941, 33776

flat whale
#

Line 68-102 don’t belong there as far as I recall plus these lines as well. You would put that in a file called… let’s say sideburnz.yml and from your config.yml file, you call it. That being said, before you do that, see if you are getting what you need from the defaults and then try to understand “why” you want this external file…what does it give you over and above the defaults?

#

Set this to true

#

playlist_files:
- pmm: playlist
  template_variables:
    libraries: Movies, TV Shows

  playlist_files:
  - pmm: playlist                # This is a file within PMM's defaults folder
    template_variables:
      libraries: Movies, TV Shows   # list of libraries that you want the PMM Defaults playlists to look at

And your options are: [2023-10-20 15:06:45,334] [config.py:967] [ERROR] | Plex Error: Plex Library 'playlist_files' not found. Options: ['Concerts', 'Documentaries', 'Movies', 'Movies (4K)', 'Stand-up', 'Docuseries', 'TV Shows', 'Electronic', 'Mixes', 'Akoya Slideshow', 'Photos', 'Home Movies'] |

#

So that library error is a little peculiar… I would have thought that all is ok. Are your Movies and TV Shows libraries filled with some media?

#

Got it! Move each of these lines, two spaces to the left

flat whale
#

@stray frost , this one and our other thread are very similar... I think you have 3 in total.. may want to consider closing this one down since we are already discussing this elsewhere.