Everything posted by Joly0
-
[Plugin] FolderView3
Because VladoPortos, unlike you, has a GitHub account with actual projects he (atleast from looking at it) built and the changes he did to Folder.View2 were to this day 23 commits in a timespan of a few months, compared to your 104 in a few weeks. Don't get me wrong. I am not trying to talk down the work you have done so far. As I said initially, it's good that this project is taken care of by someone. It's just that people (me included) could be or are concerned that you don't quite know what you are doing if you just approve claude's work and that this project could be left alone in the foreseeable future and will again need a new dev. Of course there is a reason I created that PR and don't use that option, because it doesn't make sense. That update column (atleast in my opinion) serves a helpful purpose and especially when having mixed folders (which I do as you can see in my PR) that information text from that column is quite useless. Also, as I wrote in my PR, the fix is not solely for the compose plugin (answering one of your questions later here), but for example also the same problem with "container-managing-containers" like nextcloud-aio. Also, just to add to my first point as a good example of what could go wrong in an AI written application that the dev doesn't know what he is doing: https://www.reddit.com/r/selfhosted/s/cYAXggzFoo I am not saying you should stop, or that something like this could happen (I mean, if you don't add hundreds or thousands of useless features, this can't happen at all), but AI written stuff is still far from perfect (and I know that, having to work with AI is my day to day job...). And to add something positive: It's quite honest from you disclosing that you used Claude for this project. Not many are that honest :)
-
[Plugin] FolderView3
Hey Mate. Cool to see the plugin being developed again. Just here asking two things though. First, you mentioned you co-authored using Claude, could you elaborate a bit more what that means in your case? Did you write any code, or did you just approve claude's code? Do you know and can write the programming languages that folder.view(2) is written in? Looking at you GitHub repo it doesn't look like you have much experience in programming at all? How can one make sure you will continue developing this tool? Second, nonetheless to my questions from First I would still like to mention here that I have an open PR over at the folder.view2 repo https://github.com/VladoPortos/folder.view2/pull/21 that I would like to see merged. You mentioned you didn't change that much (although 104 commits indicate otherwise), so it should be pretty easy to bring my changes over to this repo (you should be able to bring over my changes to your repo, without me having to open a pr at your repo). Of course this would only matter if you really want to continue supporting this plugin in the long-term (it's annoying that we already need a v3 here) and if you are even interested in the changes I did in my PR.
-
Home Assistant Unraid Integration
-
Home Assistant Unraid Integration
Hey, i got this message from "Fix common problems" today and noticed that /var/log is over 100MB in size I checked the log folder and noticed this: As you can see, the unraid-management-agent fills my /var/log folder every day with a 5MB file, which in general is not that large, but it adds up and is currently consumes 80MB of /var/log. When i looked into the log files, i noticed that it spammed the same stuff over and over again for thousends of lines. I have attached the latest log file for analysis. unraid-management-agent-2026-01-09T20-02-58.401.log
-
[Plugin] Docker Compose Manager
Hey @primeval_god can you provide a rough timeframe when you will have time to look at my PR? Its been open for nearly 5 months and imo fixes/improves and important part of the plugin.
-
[Plugin] Disk space Management - Mainly for those who use the split-level feature in Unraid.
So i think by smallest and alphabetically should be sufficent for me, in normal order and reversed. Maybe also newest/oldest would be nice aswell. Not sure if random would be of any help (for me), but might be worth implementing aswell if it isn't to hard to add :)
-
[Plugin] Disk space Management - Mainly for those who use the split-level feature in Unraid.
Yes, something like that would be nice. Not sure for the "Other Files" if moving smallest would be the best, some configurability here would be appreciated, but a simple approach would be sufficient as a middle step. Btw, would it be possible (just a general question), to adjust this priority? So I could configure that tv shows are moved first, then other files and last movies or so?
-
[Plugin] Disk space Management - Mainly for those who use the split-level feature in Unraid.
Hey, thanks for the response. So re-configuring the cron schedule seems to have fixed the problem. I am not sure what happened, in the logs I can only see, that the automated run was last time executed 25.07.2025. But it seems to be starting now again properly. Will have to check if my it runs tonight. Another question, is it possible to configure additional paths? Would be nice for more generic stuff to have the option
-
[Plugin] Disk space Management - Mainly for those who use the split-level feature in Unraid.
Hey, i really like the Plugin, but the plugin doesn't run on schedule for me. I still have the same settings as shown in my first post here, so nothing changed, it's still though not working. Tried updating, but nothing either. I just noticed it, because my storage on a disk was filling up over the threshold, and I was wondering, why this happened with the script, and then notices it didn't run automatically since I configured it after first installation
-
Sample plugin
Hey, thanksfor the very comprehensive guide, it is very detailed, well written and will be very helpful If I may ask for something: it would be extremely useful for future plugin devs, if limetech would provide something like a template plugin that one could use with many features integrated and documented, especially now when unraid moves to responsive webui the changes are huge and a "common ground" or "best practice" example would be great. I have started on developing a very complex plugin and at the beginning I had a lot of struggles with basic stuff, because every plugin Dev did it differently (I looked into various github repos of plugins and tried to figure out what is how done and why). So a best practices demo plugin would be extremely useful. So how to align buttons in a dd, how to create tables that are responsive (normal width and wide width), how different menus work, how for example file picker works or can be implemented, how tooltips for options work, dropdown menus, etc. Just a few things off of my head now that I know I struggled with varying degrees. Maybe also how to stucture a plugin according to best practices, etc. Would be awesome. Besides that, you guys are doing a phenomenal job, can't wait for 7.2 release
-
[Plugin] Disk space Management - Mainly for those who use the split-level feature in Unraid.
-
[Plugin] Disk space Management - Mainly for those who use the split-level feature in Unraid.
Hey, cool plugin. I just tried it out and noticed, that the log file is not created nor written to at all. I also checked the script that should move the stuff, but there is nothing either. The variable with the path is initialized at the beginning, but the variable nor the file itself is used anywhere in the script. Otherwise, cool plugin. I like it
-
[Plugin] Docker Compose Manager
So have you had time yet to look at this? Its been a good while and you dont reply on github, therefore i ask here
-
[Plugin] Docker Compose Manager
So, can you merge my PR please?
-
[Plugin] Docker Compose Manager
-
[Plugin] Docker Compose Manager
See here the perplexica path without my patch: As you can see, the stack and the project files are correct, just the plugin expects an docker-compose.yml file, while perplexica ships a file named "docker-compose.yaml".
-
[Plugin] Docker Compose Manager
รhh, no. For example i cloned the perplexica github repo to my array, not the compose manager project directory. I created a new stack on the compose page and pointed the stack directory to the cloned repo directory. Still the compose file that perplexica ships with is not showing up in the compose manager page, because the plugin expects the file with a the name "docker-compose.yml", perplexica uses "docker-compose.yaml". My patch fixes this.
-
[Plugin] Docker Compose Manager
Hey @primeval_god could you take a look into my pr https://github.com/dcflachs/compose_plugin/pull/33 and maybe merge it? Would be great to have this implemented. Currently i have to apply my changes manually after reboots on one of my servers
-
Server name is not updated in Dashboard
Thanks, worked, but tbh not a really "elegant" solution ๐
-
Server name is not updated in Dashboard
Hey, i have a server that i registered with unraid connect before i changed its name. Now the name is not updated in the unraid connect dashboard
-
Mover bugged for certain file names
Hey guys, i noticed, that the mover stucks itself, when trying to move certain files. For example it stucks when moving files named "lock" or "haltcode". I tried running the mover through terminal and tthrough webui, with and without mover tuning installed, with reboots in between uninstalling mover tuning and so on and so forth, it always gets stuck on those files. And just to get ahead of questions: - Yes, i know i dont need to or shouldnt move the docker folder - Yes, docker and vmยดs are disabled - I move the folders so i can reformat and add more drives to my cache - Yes, i know i could just remove the docker folder and just recreate all my dockers, but i do not want to go through the hassle of recreating the docker networks and also nextcloud-aio takes forever to backup and it NEEDS a backup because it stores everything in docker volumes, rather than mounts, so i need the docker folder so i do not need to create a backup Also moving the docker folder through file manager worked no issue, its just the mover thats having this issue. Not sure if it is handling those file names in weird way. tower-diagnostics-20250202-1937.zip
-
[PLUGIN] ZFS Master
There is actually. Some dockers (for example nextcloud-aio) and various dockers i created using docker compose plugin use volumes and not mounts (mounted to /mnt/cache/appdata for example) and therefore to be safe, i keep it for the time being
-
[PLUGIN] ZFS Master
Hey guys, i did a similar question a long while back ( i think just a few days after this plugin came out) on how to use the dataset exclusion patterns for the docker share when it is under /mnt/cache/docker and sitting on a zfs formatted pool. I now had to switch from the zfs backend driver to overlay2 due to various issues and renamed the old share from "docker" to "docker-old" and created a new share called "docker". When i run "zfs list" i get this: cache/docker-old/wolhvhslvf29k8t3pivzaxgeo 304K 318G 1.05G legacy cache/docker-old/wveaw68gkv2pva12ry251lvvw 288K 319G 1.30G legacy cache/docker-old/x4szq66lf0kxs1hjvyli9vvcp 160K 319G 1.05G legacy cache/docker-old/x9rtcl22u2gv15xsca2kn73vc 328K 318G 679M legacy cache/docker-old/xuwh6qbuz8q154w33lqsskxtw 1.86G 318G 2.99G legacy cache/docker-old/y5n8i1wbdw946rl40gdp7hhlg 572M 318G 1019M legacy cache/docker-old/y6crl33ldujwb9jfcyeb97hly 19.0M 318G 626M legacy cache/docker-old/y9nro0dg7tbovdah2z0k38x4r 304K 318G 1.05G legacy cache/docker-old/ygpppknipp372joltaaefqpql 541M 318G 1.14G legacy cache/docker-old/yiretnbh62p6135tcgtjtnj8a 100K 318G 100K legacy cache/docker-old/yko1q8i6q99g2asu9ogy0b2rl 304K 319G 1.33G legacy cache/docker-old/ykuwgidf4wn57ynrtgbbqyefj 541M 318G 1.14G legacy cache/docker-old/ynvwhtzlynd8w4kca5iun3k5m 160K 318G 1.05G legacy cache/docker-old/ypqwyhi8ch1gmi8qqdomph5g1 448K 318G 2.95G legacy cache/docker-old/yvbxcyaq33rtsfg38w9l1wyv6 288K 318G 626M legacy cache/docker-old/zal6250uewuv703rtmyirivb2 384K 318G 463M legacy cache/docker-old/ztajorcy58sr9k0k8sdhhcsto 19.0M 318G 626M legacy cache/docker-old/zumi4wozbdoy2czeysshijf5t 160K 318G 1.33G legacy cache/domains 9.80G 318G 9.80G /mnt/cache/domains cache/system 968K 323G 968K /mnt/cache/system etc The problem is, that after renaming the share, the zfs master plugin wont hide it anymore. I had the exclusion pattern previously set to "/docker/.*" (without the ") and now i changed it to "/docker-old/.*" (also without the "), but for some reason, the datasets are not hidden anymore and the main page takes ages to load. What could be wrong? It worked previously I could probably delete the old share, but as i might have forgotten to move something, i want to make sure and keep it for a while, until i am 100% certain i didnt miss anything
-
[Support] Josh5 - Steam (Headless)
Hey, unfortunately i wasnt able to solve this problem
-
[SUPPORT] GRTGBLN - DOCKER TEMPLATES
Skipping virtualenv creation, as specified in config file. [Main][2025-01-07 16:29:50,264][INFO] = LOG LEVEL: INFO Traceback (most recent call last): File "/code/main.py", line 24, in <module> db = Database(logger) File "/code/DapsEX/database_cache.py", line 13, in __init__ self.initialize_db() File "/code/DapsEX/database_cache.py", line 23, in initialize_db with self.get_db_connection() as conn: File "/code/DapsEX/database_cache.py", line 17, in get_db_connection conn = sqlite3.connect(Settings.DB_PATH.value) sqlite3.OperationalError: unable to open database file Running main.py as 1000:1000 Did not help either unfortunately