52 minutes ago, chodeus said:

I don’t use compose so I apologise for my ignorance.

I see a few different compose managers, do they all overwrite the Unraid docker container start up? Do they fundamentally function the same and just appear different?

From the screenshots I’ve seen it looks like the compose managers almost do what folderview does as far as organising the containers.

Are you wanting folderview2 to ignore the container start up order if compose is installed?

Correct if they are labeled compose man

The. The folder view plug should not touch docker start stop and only be a gui cosmetic display.

There are other orchestration layers. Idk them all and this is what I've used per post and past support on compose.

They all handle dockers differently.

If compose down is ran the images are removed out right (images exist on disk) and can cause an empty folder...

It's more what the unraid webunis programed, the compose plug-in is programed and what this plugin is/will do based on that data.

unRAID emhttp web server is weird to begin with. It why I haven't made plugins. And each time I atemp and want to I remind myself that 1 I don't want to support nor try to follow the emhttp

2 I don't have a good way to explain share and go over

3 integration to it would not be the same

Where I would ultimately probably rewire a lot of it for a different page.

This is where other project for a home page comes in like hemidal to group things together....

Folder view has (for me) always been a cosmetic display issue with Dockers.

Where other projects like protainer can shine for access to the docker sock and 1 location to mange/control...

As portainer can support multi types of compose/ca images etc...

As a lot of dockerman stuff is unraid specifically labeled for display cosmetic control...

CA will eventually support docker compose it's in the works. I'm waiting on that to write new compose files for ca to have a 1 click install and done for quite a few docker stacks...

As we can then go full self host with got pulls and run compose that builds the docker granting users full control and edits.

The docker web UI and the plugin has always been a cosmetic thing...

Since I'm modifying Vlado's folderview2 and making it functional, I'll see what I can do about having it ignore docker autostart order if composeman is being used. My issue is, I have little interest in loading a compose manager to test it. If I can implement it I'll keep it as a beta until someone is brave enough to test it.

It has been a while since I was on Unraid v6+ but I believe scolcipitato's folderview plugin's autostart procedure modified Unraids container start order as per the positioning of the container in the folder. I don't think this works with Vlado's version but I can also look at this too.

This is where I have got to with my version today. Can’t imagine there’ll be any drastic changes in the next week as I’ve got family staying with me.

I’ve started looking at the container start order working as per the folder order and container order in each folder.

And I’ve started looking at folder view2 ignoring containers with the label ‘composeman’

Again, if anyone is willing to try out my stable/makn fork of folderview2 you can find it on page 14. As it’s vibe coded, I’m trying hard to ensure I don’t make any breaking changes which is why I’m being careful with the container startup and composeman integration.

I’m really lucky because the original folderview that Vlados folderview2 was forked off was written pretty well!

8 hours ago, chodeus said:

I’m still surprised to read that not all users are on Unraid v7+.

Yep that sad but it seems double work to support old versions also :)

Like in mover tuning plugin as example I need now to fix broken webui for old version befor 7.2 that not support responsive Webui, that I don't have time for it now... :)

1 hour ago, chodeus said:

was forked off was written pretty well!

Yep @scolcipitato made amazing work and was one of the best...

On 2/6/2026 at 9:56 AM, chodeus said:

Mine auto updates so yes yours should too. I’ll make that fix and repackage and update tomorrow sometime! Nice work.

Your heading of the column is missing.

I was not aware that you forked foder.view2 and that you are heavily improving it. Thanks for your work. I just installed your version of fv2 and I am happy to help you testing with compose if you need it. I am currently migrating my containers to use compose for everything.

It would be great to have folder.view2 behave like this:

• If labels "net.unraid.docker.managed: 'composeman'" and "folder.view2: 'phpipam'" are set for the container, create the folder with this name and sort the container into it.

• Add another label "folder.view2.icon: 'https://path.to.icon.png'" to make sure the automatically created folder gets an icon.

folder.view2 already sorts the container into the folder given with the folder.view2 label if the folder was manually created before compose up.

Kicking a compose down will result in having an empty folder which is not a huge issue I guess and I think it is not an option to remove the folder on compose down because all folder settings set manually later after auto-creation will be removed as well.

Just some thoughts and let me know if I can help you with that.

9 minutes ago, UnKwicks said:

I was not aware that you forked foder.view2 and that you are heavily improving it. Thanks for your work. I just installed your version of fv2 and I am happy to help you testing with compose if you need it. I am currently migrating my containers to use compose for everything.

It would be great to have folder.view2 behave like this:

• If labels "net.unraid.docker.managed: 'composeman'" and "folder.view2: 'phpipam'" are set for the container, create the folder with this name and sort the container into it.

• Add another label "folder.view2.icon: 'https://path.to.icon.png'" to make sure the automatically created folder gets an icon.

folder.view2 already sorts the container into the folder given with the folder.view2 label if the folder was manually created before compose up.

Kicking a compose down will result in having an empty folder which is not a huge issue I guess and I think it is not an option to remove the folder on compose down because all folder settings set manually later after auto-creation will be removed as well.

Just some thoughts and let me know if I can help you with that.

Oh awesome! Please let me know if you notice anything broken in the stable, that is my priority.

I’ll be doing some tweaking to get things looking how I feel they should look but it won’t be anything drastic, just minor OCD things now that everything appears to be working.

Once I’m ready for testing the compose addition I’ll let you know. I’ll 100% take on the suggestions you have just provided. I hope to include proper compose support and container auto start sequencing as per what is visible (and this setting off for those using compose).

9 hours ago, chodeus said:

Oh awesome! Please let me know if you notice anything broken in the stable, that is my priority.

I’ll be doing some tweaking to get things looking how I feel they should look but it won’t be anything drastic, just minor OCD things now that everything appears to be working.

Once I’m ready for testing the compose addition I’ll let you know. I’ll 100% take on the suggestions you have just provided. I hope to include proper compose support and container auto start sequencing as per what is visible (and this setting off for those using compose).

while a bit on the side programing we could use html comments <!-- -->
and a check of docker ps to see if dockers in teh folder are in the docker ps and if not to coment of the fodler to not be dispalyed.. idk somethign like that.

Like, I will galdly assit and test but i'm limited on time anymore theses days.

with compose we can add all kinds of lables and test things. we can also add -l folder.view2.icon: 'https://path.to.icon.png'"
to extra parm in a unraid tempalte to add adatainl things to teh exisitng unraid temaptle so not a compose only feature...

Most lables are harmless and are usualy used with conjuntion with other dockers. example watch tower has a label settings


-l com.centurylinklabs.watchtower.enable: "true"
then wath towe will use the lable.

Tailscale with tsdproxy has label settings Example my immich:

like, labels read from the folder view is the correct way to interpret what is doing what.

and can be interchanged using compose to docker run and docker run to compopse.

docker run to compose https://www.composerize.com/

compose to docker run: https://www.decomposerize.com/

Ten having a unified label that the other dev have already made. dockerman for CA composeman for Compose plugin...

we just have to have documentation of lables is all.

11 hours ago, chodeus said:

Oh awesome! Please let me know if you notice anything broken in the stable, that is my priority.

I’ll be doing some tweaking to get things looking how I feel they should look but it won’t be anything drastic, just minor OCD things now that everything appears to be working.

Once I’m ready for testing the compose addition I’ll let you know. I’ll 100% take on the suggestions you have just provided. I hope to include proper compose support and container auto start sequencing as per what is visible (and this setting off for those using compose).

I am having an issue on the unraid dashboard when adding the containers to the folders via labels. The dashboard shows the folders with "x/x started" but also each container of the folder as well again. When I view the folder settings I can see that the container got automatically added to folder via the label but somehow shows up again below those. On the Docker tab they are only shown within the folder. But on the Dashboard tab folder and additional containers are showing.

Edited February 8Feb 8 by UnKwicks

7 hours ago, UnKwicks said:

I am having an issue on the unraid dashboard when adding the containers to the folders via labels. The dashboard shows the folders with "x/x started" but also each container of the folder as well again. When I view the folder settings I can see that the container got automatically added to folder via the label but somehow shows up again below those. On the Docker tab they are only shown within the folder. But on the Dashboard tab folder and additional containers are showing.

Just to be clear, you're on the main/stable branch?

Have you got this toggled on in folder settings?

I believe the dashboard behavior may have been changed previously so that ALL containers appear on the dashboard, I think previously only Folders + containers in folders when expanded appeared on the dashboard.

6 hours ago, chodeus said:

Just to be clear, you're on the main/stable branch?

Have you got this toggled on in folder settings?

I believe the dashboard behavior may have been changed previously so that ALL containers appear on the dashboard, I think previously only Folders + containers in folders when expanded appeared on the dashboard.

Yes I am on the stable branch of your fork.

I got the toggle and tried both, on and off.

I can give you more details on how it behaves.

My scenario: I have 3 folders created manually. I added labels to some containers to sort them into the 3 folders. All other containers are not labeled or sorted into a folder.

On the Docker tab everything is like expected. Labeled container are being sorted into the folders, not labeled containers just get listed below.

On The Dashboard tab I can see the folders and the containers. But the wrong containers are being sorted into the folders. E.g. immich contains 5 other (not labeled) containers and not the immich labeled containers. When I click "expand" on the folder I can see the wrong containers getting expanded.

Could this be a caching issue with the old plugin? What do I need to do to start over completely fresh (deleting all previous folders, icon and so on currently generated and maybe cached)?

So I have read through all the pages and found some mentions but no definitive answer for my question. Using V2025.04.13 Unraid V7.2.3

WEB UI link broken

Hover over Container and select WEBUI result is new page with about:blank#blocked

Hover over World Icon and enter result is new page with about:blank#blocked

Select Folder Arrow to reveal the containers and result is fine....

Any other items outside of folderview2 are fine also

3 hours ago, UnKwicks said:

Yes I am on the stable branch of your fork.

I got the toggle and tried both, on and off.

I can give you more details on how it behaves.

My scenario: I have 3 folders created manually. I added labels to some containers to sort them into the 3 folders. All other containers are not labeled or sorted into a folder.

On the Docker tab everything is like expected. Labeled container are being sorted into the folders, not labeled containers just get listed below.

On The Dashboard tab I can see the folders and the containers. But the wrong containers are being sorted into the folders. E.g. immich contains 5 other (not labeled) containers and not the immich labeled containers. When I click "expand" on the folder I can see the wrong containers getting expanded.

Could this be a caching issue with the old plugin? What do I need to do to start over completely fresh (deleting all previous folders, icon and so on currently generated and maybe cached)?

Masterwish is having same issue as you and I’m currently investigating it.

It’s hard for me though because I don’t have this issue.

However, I did backup my vm.json and docker.json like Vlado recommended and uninstalled his version and installed my version, copied/imported my vm and docker.json back in and as you can see in my screenshot above, everything appears to work like normal.

Would you like to try uninstalling the plugin and installing my version from fresh? Just backup anything you’ve modified including your docker.json and vm.json.

36 minutes ago, crazyc said:

So I have read through all the pages and found some mentions but no definitive answer for my question. Using V2025.04.13 Unraid V7.2.3

WEB UI link broken

Hover over Container and select WEBUI result is new page with about:blank#blocked

Hover over World Icon and enter result is new page with about:blank#blocked

Select Folder Arrow to reveal the containers and result is fine....

Any other items outside of folderview2 are fine also

It’s a common fault with that stable version. There’s a beta linked in the first post where this is fixed (I think).

@chodeus thanks for that, bit late at night here to do so will look at tomorrow. New to Unraid. so what is best practice to remove or update this plugin to the beta version. I I cant see an export function. The first page one has manual install instructions which i guess appears as a downloaded plugin when done.

1. Copy the folder.view2.plg file to /boot/config/plugins/ folder.

2. Copy the latest 'folder.view2-.txz' archive to /boot/config/plugins/folder.view2/ folder.

3. In Unraid webui go to Plugins -> Install Plugin tab, click on the folder config -> plugins -> folder.view2.plg and press install button.

4. Use the Import to import the setting you exported...

Thanks in advance for the advice

Edited February 9Feb 9 by crazyc

Yeah that’s the process.

I’d recommend backing up docker.json and vm.json and saving them somewhere else, manually removing the plugin, then install the beta files like he suggests in the first post.

Or… you can try my forked of Vlados plugin which fixes these https://github.com/chodeus/folder.view2

It’s not 100% problem free though.

@Masterwishx and @UnKwicks want to test this version I've just pushed before you remove the plugin for a fresh install?

If this doesn't resolve your issue - I'll strongly suggest backing up your vm.json and docker.json and removing the plugin entirely and installing my version fresh.

This has been difficult for me to test because mine has worked fine this whole time. The only thing it seems I did different was, I removed Vlado's folderview2 before installing mine.

2026.02.09.1

• Fix dashboard showing wrong containers in folders

26 minutes ago, chodeus said:

@Masterwishx and @UnKwicks want to test this version I've just pushed before you remove the plugin for a fresh install?

If this doesn't resolve your issue - I'll strongly suggest backing up your vm.json and docker.json and removing the plugin entirely and installing my version fresh.

This has been difficult for me to test because mine has worked fine this whole time. The only thing it seems I did different was, I removed Vlado's folderview2 before installing mine.

2026.02.09.1

• Fix dashboard showing wrong containers in folders

You are awesome! I removed the plugin and installed your new version. To be sure I start from scratch I did not import my folders but created them again manually.

Now the folders appear correctly on the Dashboard containing the correct containers. Thanks!!

Probably the biggest improvement from today is now the container auto start order now updates when you move them in the folder settings page and click "submit."

If you want more detail in what was changed you can browse the changelog on my github.

Until now folderview didn't actually change the container start order, only the folder start order. It didn't matter where those containers were in the folder, it started as per Unraids predefined start order.

Now I've got this sorted I will look at the dockers compose side of things and having this order ignored.

@chodeus thanks my friend. have reconfigured with your fork using manual add and started again fresh. All is working as it should. When you update does this auto update or is it manual again. i see the folder view app is now set to reinstall only from the apps tab. But looks fine when going settings and click the entry..as i said new to the nuance of Unraid

9 minutes ago, crazyc said:

@chodeus thanks my friend. have reconfigured with your fork using manual add and started again fresh. All is working as it should. When you update does this auto update or is it manual again. i see the folder view app is now set to reinstall only from the apps tab. But looks fine when going settings and click the entry..as i said new to the nuance of Unraid

Auto update will work perfectly fine.

Once I finalise the compose compatibility, I’ll need to look at a plugin name change/update and then get it added to the Community Apps

19 hours ago, chodeus said:

2026.02.09.1

• Fix dashboard showing wrong containers in folders

Thanks, now on version 2026.02.10, I see all fine in dashboard for containers order in Folders

Update to main branch, this should be automatically available for you.

If you notice any bugs let me know and I can take a look at them after the weekend.

I added a custom URL option for the folder, mainly for the compose users.

Compose containers can be added if the user manually creates the folder first as per the upstream version. I trialled automatic folder creation but it’s messy and didn’t work the best.

Thankyou @bmartino1 for helping me test this.

There’s one small bug I’ve noticed when deleting containers and I need to update the readme to provide a summary and instructions of what my fork does but as always, each commit is clearly detailed in the changelog on my repository so feel free to browse that.

I’m away until after the weekend so there won’t be any updates until I get back and I’ll be slow to respond here.

Edited February 11Feb 11 by chodeus

13 minutes ago, chodeus said:

Update to main branch, this should be automatically available for you.

If you notice any bugs let me know and I can take a look at them after the weekend.

I added a custom URL option for the folder, mainly for the compose users.

Compose containers can be added if the user manually creates the folder first as per the upstream version. I trialled automatic folder creation but it’s messy and didn’t work the best.

Thankyou @bmartino1 for helping me test this.

There’s one small bug I’ve noticed when deleting containers and I need to update the readme to provide a summary and instructions of what my fork does but as always, each commit is clearly detailed in the changelog on my repository so feel free to browse that.

I’m away until after the weekend so there won’t be any updates until I get back and I’ll be slow to respond here.

Thank you very much sir! This is awesome.