No for compose containers you would usually update them by running "update stack" on the compose manager site. I don't think you can apply an update to compose containers from the normal view. Also in the folded out view it does not show the "apply update" for compose containers - as you see here:

All the paperless containers are compose containers, and for some reason, it is showing updates available for 3 of them, when in reality there are none.

Just looking at the screenshot now, I noticed that the ones that are indicating an update are from dockerhub, whereas paperless-ngx is from ghcr.io. Might have something to do with that....

Awesome screenshot, I think I have an idea which is a partially what @Joly0 suggested.

If you run my fork, you might see a changelog in the next stable relating to this.

I try to thoroughly check and test everything in beta before I push to stable.

If I understand everything correctly now, in FolderView3 the default container order Autostart is replaced by what you see in FolderView3. For Example:
Pre-Folder View
- Container 1
- Container 2
- Container 3

Would start 1, 2, 3

In FolderView3
- Folder A
-- Container 1
-- Container 3
- Folder B
-- Container 2

Would start 1, 3, 2

Is that correct or is the Unraid Container order still setting the autostart settings? I asked because some containers need to start before others since they are dependent upon each other.. mainly databases.

7 hours ago, chodeus said:

I've got 2 questions for you too.

1. Why did you not ask VladoPortos of FolderView2 the same thing, it seems you are perfectly happy running FolderView2? The only difference between what he had done and what I have done is I disclosed the tool I used to help achieve a working plugin.

2. Is there any reason you prefer the approach of your PR instead of using the "hide update column" toggle? Afaik most compose users toggle this as it is irrelevant information to them. I'm happy to entertain feature requests once the bugs are ironed out (which they should almost be) but I'm not too keen on blending plugins for individual users. The compose side of things I'll look at because scolcipitato has it somewhat built in already but I would like to know why hiding the update column doesn't resolve your issue.
   Also the reason for so many commits is because of everything that needed fixing and yes I made a few visual improvements too https://github.com/chodeus/folder.view3/blob/main/CHANGELOG-fixes.md

   

1. 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.

2. 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 :)

8 hours ago, chodeus said:

This was simple, it will be in the next stable release.

Unsorted containers will appear in alphabetical order on the folder settings page.

Thankyou for the suggestion!

Huge. Thank you!

I would also like to add another thing to the input i am giving here:
You cannot just add your license to the codebase and call it a day. That license is not legally binding and infact its not even allowed (would count for me aswell as i did the PR) per copyright law. Infact folder.view and folder.view2 are "all rights reserved" projects (wasnt even allowed for VladoPortos to fork it in the first place).

There are only 3 options you have that would make the license hold:
1. You have fully rewritten the code and no original code is left in there, than you can re-license the code
2. You add a notice that only your own code (and contributions) are covered by the MIT license.
3. You ask all original creators and contributors for permission to change the license (so scolcipitato, VladoPortos and all the contributors).

Just wanted to tell you that, as i just saw you added a license. Was in a same situation a while ago and just wanted to share what i know.

48 minutes ago, Joly0 said:

I would also like to add another thing to the input i am giving here:
You cannot just add your license to the codebase and call it a day. That license is not legally binding and infact its not even allowed (would count for me aswell as i did the PR) per copyright law. Infact folder.view and folder.view2 are "all rights reserved" projects (wasnt even allowed for VladoPortos to fork it in the first place).

There are only 3 options you have that would make the license hold:
1. You have fully rewritten the code and no original code is left in there, than you can re-license the code
2. You add a notice that only your own code (and contributions) are covered by the MIT license.
3. You ask all original creators and contributors for permission to change the license (so scolcipitato, VladoPortos and all the contributors).

Just wanted to tell you that, as i just saw you added a license. Was in a same situation a while ago and just wanted to share what i know.

You claim to have read my repository but somehow you missed this on my readme which makes me less inclined to read all of your posts.

Also Vlados fork was written with AI. I’m not going to keep going on about it because I don’t have an issue with what Vlado did. He also has this repository. Just because someone manually pushes the commit button doesn’t mean they wrote the code. Again, not something I have an issue with, I just have no shame in letting Claude push the commit button after I’ve reviewed the commit.

The main reason why I created my own fork was because there was no one maintaining FolderView2. There hadn’t been a stable release since August and Vlado had been MIA since October and no other user was willing to pickup the plugin.

The fork was intended for my private use but it worked so well and users were still posting issues in the FolderView2 support thread I thought it would be rude not to share it.

If you’re worried in any way and you have the ability and time to maintain this plugin I am more than happy to close this thread and let you fork the plugin. I’ll keep using my version privately.

Side note, I have no interest in bloating this plugin. I want to keep it minimal, it is meant to be a visual tool, not a docker and VM management tool. The only bit of docker management I added was the autostart order feature because with folder view you had minimal control over the autostart order of individual container.

3 hours ago, Biff Bojangles said:

If I understand everything correctly now, in FolderView3 the default container order Autostart is replaced by what you see in FolderView3. For Example:
Pre-Folder View
- Container 1
- Container 2
- Container 3

Would start 1, 2, 3

In FolderView3
- Folder A
-- Container 1
-- Container 3
- Folder B
-- Container 2

Would start 1, 3, 2

Is that correct or is the Unraid Container order still setting the autostart settings? I asked because some containers need to start before others since they are dependent upon each other.. mainly databases.

That is correct. What you see on your screen and have toggled on via the autostart toggle is the start order.

Top folder first and then containers left to right, then next folder.

The wait time in advanced view can also be used if you need more time for your DB containers to start. You might want to use this because during my testing everything started almost all at once anyway.

You can check and verify with cat /var/lib/docker/unraid-autostart

1 hour ago, chodeus said:

You claim to have read my repository but somehow you missed this on my readme which makes me less inclined to read all of your posts.

Also Vlados fork was written with AI. I’m not going to keep going on about it because I don’t have an issue with what Vlado did. He also has this repository. Just because someone manually pushes the commit button doesn’t mean they wrote the code. Again, not something I have an issue with, I just have no shame in letting Claude push the commit button after I’ve reviewed the commit.

The main reason why I created my own fork was because there was no one maintaining FolderView2. There hadn’t been a stable release since August and Vlado had been MIA since October and no other user was willing to pickup the plugin.

The fork was intended for my private use but it worked so well and users were still posting issues in the FolderView2 support thread I thought it would be rude not to share it.

If you’re worried in any way and you have the ability and time to maintain this plugin I am more than happy to close this thread and let you fork the plugin. I’ll keep using my version privately.

Side note, I have no interest in bloating this plugin. I want to keep it minimal, it is meant to be a visual tool, not a docker and VM management tool. The only bit of docker management I added was the autostart order feature because with folder view you had minimal control over the autostart order of individual container.

I did not claim anything, i just noticed, that you added a license, but all good if you have already added a notice. Its not liek i am scanning your repo 24/7.

Also, it appears to me, that you might have misunderstood my initial questions or i might have asked them in a way that you could interpret as rude. Just to clarify, this was not and is not my intention and i am sorry if my questions were not well written and i apologize for it.
I am not against you or the project that you are trying to take over. I am also not against you vibe-coding this project to continue developing it. I just wanted to clarify that maintaining an open-source project is more than just prompting an ai to do stuff and it makes a difference if you know how to code from the beginning and use ai to help you code or if you have zero to low knowledge in any programming language and use ai as your only source of truth. So my initial questions wasnt against you or against vibe-coding in itself, but just wanting to know what experience you have in coding in general and maintaing an open-source project.

Latest update:

@msalad the alphabetical sorting is in.

@Joly0 and @satchafunkilus I believe I have improved the Compose and 3rd Party awareness. @Joly0 I took a leaf out of your PR and modified it slightly as I didn't like the whole "mixed" thing. The orange update text will nolonger appear for 3rd Party and Compose containers. The useless autostart toggle for 3rd party and compose containers has been removed from the folder line preview line.

Only a compose container = Compose label

Mixed 3rd party and compose = Labeled both

If theres a dockerman container in the folder the Version column goes to default.

Note: You may need to delete your browsing history/cache for some of these changes to appear properly.

Edited February 24Feb 24 by chodeus

Will it be available on CA?

10 minutes ago, PilaScat said:

Will it be available on CA?

I have completed the form for it to be added to CA.

From what I have seen these things take longer than 48 hours to process but I am checking every day.

Just updated to the latest version. The docker compose changes work nicely, from what I can tell. Thanks a lot for fixing this!

13 minutes ago, satchafunkilus said:

Just updated to the latest version. The docker compose changes work nicely, from what I can tell. Thanks a lot for fixing this!

Awesome glad you’re happy! Please let me know if you encounter any bugs I may have missed during testing.

On 2/24/2026 at 6:24 AM, chodeus said:

Latest update:

@msalad the alphabetical sorting is in.

@Joly0 and @satchafunkilus I believe I have improved the Compose and 3rd Party awareness. @Joly0 I took a leaf out of your PR and modified it slightly as I didn't like the whole "mixed" thing. The orange update text will nolonger appear for 3rd Party and Compose containers. The useless autostart toggle for 3rd party and compose containers has been removed from the folder line preview line.

Only a compose container = Compose label

Mixed 3rd party and compose = Labeled both

If theres a dockerman container in the folder the Version column goes to default.

Note: You may need to delete your browsing history/cache for some of these changes to appear properly.

Looks good by the way

On 2/23/2026 at 6:03 PM, chodeus said:

That is correct. What you see on your screen and have toggled on via the autostart toggle is the start order.

Top folder first and then containers left to right, then next folder.

The wait time in advanced view can also be used if you need more time for your DB containers to start. You might want to use this because during my testing everything started almost all at once anyway.

You can check and verify with cat /var/lib/docker/unraid-autostart

That is super helpful. That was the one thing that always bothered me with FolderView and FolderView2, there was a disconnect with container order in unraid for autostart and the look and feel of folderview. Awesome work with keeping this alive.

3 hours ago, Biff Bojangles said:

That is super helpful. That was the one thing that always bothered me with FolderView and FolderView2, there was a disconnect with container order in unraid for autostart and the look and feel of folderview. Awesome work with keeping this alive.

Yeah it was one thing that really bothered me too! It was really hard to correct the auto start sequence once FolderView(1 or 2) was installed.
Glad you enjoy it! Thankyou for the feedback!

Thanks for this! Held off on 7.2 until I could use FolderView.

Glad to see toggling autostart now actually works consistently, a very nice change!

It doesn't appear to be reflecting the autostart state via the Unraid API however.

I have set most of my containers to autostart, but when I use NZB360 and look at my containers, most have 'A' greyed out and say autostart is disabled. Is this something you'd be able to fix without too much effort?

1 hour ago, SakabaRihiro said:

Thanks for this! Held off on 7.2 until I could use FolderView.

Glad to see toggling autostart now actually works consistently, a very nice change!

It doesn't appear to be reflecting the autostart state via the Unraid API however.

I have set most of my containers to autostart, but when I use NZB360 and look at my containers, most have 'A' greyed out and say autostart is disabled. Is this something you'd be able to fix without too much effort?

Glad it’s working for you!

Have you got a screenshot of how the docker page looks in NZB360 so I can understand it? I don’t use it so I need to do some research and see if this is an NZB360 issue or if it’s something I can get to work but it may not be doable.

Fortunately everything else with FolderView3 appears to be working great so I have the time to do some research!

Edit: I assume nzb360 shows autostart correctly without FolderView installed?

Edited March 1Mar 1 by chodeus

Apologies, I was mistaken.

I set some containers to auto-start, then I installed the plugin.

I was using Unraid 7.1.4 with FolderView2, then installed FolderView3 and updated to Unraid 7.2.4, and noticed the inaccuracies in NZB360 with the auto-start labelling (example screenshots attached).

Upon further checking (which I should have done before my previous post), this is the case even without FolderView3 installed, even after toggling auto-start on and off with FolderView3 uninstalled and clearing NZB360 cache.

For the containers that show in NZB360 as autostart being enabled, disabling autostart and refreshing NZB360 results in the container showing as autostart disabled (correctly), but then toggling autostart back on still results in autostart being shown as disabled.

The bug lies with either NZB360 (most likely) or the Unraid API, not with this plugin.

Thanks for your work on this plugin. Do you plan to maintain it long term?

Also just wondering if you're familiar with coding, or relying on the Claude output and reading over the output, but unsure of how to write the code independently.

AI is a tool, and some people speak overly highly of it and other speak overly negatively, but when used appropriately I don't see an issue with it; I doubt you'd cause a Huntarr level situation 🤣.

18 minutes ago, SakabaRihiro said:

Apologies, I was mistaken.

I set some containers to auto-start, then I installed the plugin.

I was using Unraid 7.1.4 with FolderView2, then installed FolderView3 and updated to Unraid 7.2.4, and noticed the inaccuracies in NZB360 with the auto-start labelling (example screenshots attached).

Upon further checking (which I should have done before my previous post), this is the case even without FolderView3 installed, even after toggling auto-start on and off with FolderView3 uninstalled and clearing NZB360 cache.

For the containers that show in NZB360 as autostart being enabled, disabling autostart and refreshing NZB360 results in the container showing as autostart disabled (correctly), but then toggling autostart back on still results in autostart being shown as disabled.

The bug lies with either NZB360 (most likely) or the Unraid API, not with this plugin.

Thanks for your work on this plugin. Do you plan to maintain it long term?

Also just wondering if you're familiar with coding, or relying on the Claude output and reading over the output, but unsure of how to write the code independently.

AI is a tool, and some people speak overly highly of it and other speak overly negatively, but when used appropriately I don't see an issue with it; I doubt you'd cause a Huntarr level situation 🤣.

Thankyou for feeding that back, if you notice any potential bugs or issues please let me know ASAP so I can look at it.

I am familiar with coding and have played around with code and different languages over the past 20 years but I am no longer familiar enough to write something myself start to finish. I don't know if it was my university tutor or what but I just never really enjoyed coding, I found it tedious. So I am relying on Claude + user submissions to keep this plugin alive. I plan to maintain this plugin until it gets adopted into Unraid OS but if I find I can no-longer keep up with the issues or life gets in the way I'll request support in this forum and hand the repository over someone that has the time and the ability to keep maintaining it.

Because my level of coding/programming isn't where it once was, I wouldn't use AI to build something from the ground up. However, I'm confident in my ability to verify Claudes output (and submissions from other users for that matter) for anything that may cause other issues, unnecessary bloat, OS instability etc. For any change I consider major I load it to a beta branch and test it on my live media server before I push it to everyone else running stable.

AI can be a great tool but you shouldn't trust it blindly, check and verify with absolutely everything as if it were a person handing you work/information. Also, I don't think Claude would've been as successful as it has been so far if the base code wasn't written by a human. My fork of FolderView2 was originally just a bit of fun to see what Claude was capable of but it worked so well I couldn't not share it with other users.

BUG:🐛

When setting the folder name with a 'slash' it fails to display it in the Docker page;

Will not work:

• " Syncing / Duplication "

Works:

• "Syncing Duplication

Images Attached to display the difference.

Other notes:

Just Upgraded from FV2 to FV3 here, so yeah, that was seamless and other than this visual issue, flawless :D

11 minutes ago, CyberBlade said:

BUG:🐛

When setting the folder name with a 'slash' it fails to display it in the Docker page;

Will not work:

• " Syncing / Duplication "

Works:

• "Syncing Duplication

Images Attached to display the difference.

Other notes:

Just Upgraded from FV2 to FV3 here, so yeah, that was seamless and other than this visual issue, flawless :D

I think it's a width issue with the table but it's weird because it works for me.

What Unraid version are you using, what unraid theme and are you using any custom folderview themes?

EDIT: Can you try delete your cache + browser history and reload the page?

Edited March 2Mar 2 by chodeus

Now available in CA!

Great news! Thankyou for getting it there!