mstrhakr

Okay, I will try setting this up this weekend to see if I can experience the same bug.

Delete is in the context menu at the bottom, on stable click the stack icon to open the Up/Down/Etc context menu, on the beta, you can right click anywhere on the stack row for this menu.

Yea, i think I agree that it makes more sense to attempt to support individual git based stacks instead of using git for backup/restore of the projects folder. We have a backup feature already do adding git into the mix, while it would be nice for some, would be too much imo. Keeping this plugin simple is a goal for me, specifically keeping it inline with what unraid native would do if they were building this. That means no wild features and nothing that breaks expected behaviors. If the goal is for unraid to integrate this eventually, i need to build it in a way they CAN integrate it someday. So yea, I think I agree that backup/restore via git doesn't work here and git based stacks is a more important feature.

This seems like a compose file issue and not a Compose Manager Plus issue. Does this work from the command line, if you run compose up -d from the folder with the compose file?

I like this, especially for the backup/sync. If we have a project level repo how to we deal with individual compose from a separate repo? I know some software like Komodo support individual git based compose files/setups, is there a standard way to do this? Maybe we could force git based in another folder, and allow using git for main project folder as a separate thing? I have to think about it. If anyone has a good idea let me know. I'm interested for sure though.

This is available in the latest beta, please try it out!

To be clear, I would use this backup in addition to getting the app data backup plugin. When I get a chance I'll look it up for you.

I have not experienced this as I don't have any stacks setup this way. Could you provide a sanitized version of that setup so I can try it out and make sure it works?

This is a backup of the compose / project files, not the project app data.

Ah, I will look into this, thanks. Interesting thanks for the feedback, I will check this out. Do please try to do a hard refresh, just in case. [CTRL]+[SHIFT]+[R]

Try uninstall from Plugins tab, then Install from Apps tab.

I would love this, i was just thinking basic/advanced mode need more, advanced should almost be the default view with more added on top. I hope I can just reuse the cpu/mem display from the docker tab.

What version of unraid, and what other plugins do you have.

Awesome, sorry for all the trouble. Beta users will need to uninstall -> install to get the fix as the -dev tag breaks the update sequencing and it thinks that IS newer that the new naming scheme.

Its looking like this is all due to bad package naming. Slackware expects a certain format and I had a hyphen in a place that caused issues. Its most likely that the plugin failed to install due to this. This is being fixed in dev right now.

This is strange as they should essentially be the same package. I will investigate what differs between the packages. Sorry for the trouble guys.

What do you see. Does the section still show up but doesn't list any stacks? Stacks show on the beta but not on the main release? It sounds like the plugin install failed. Glad things are working again.

Seems like its from the PLG Url Mismatch I caused. It doesn't explicitly say it was blacklisted for that but I can't imagine another reason.

Dev PLG now correctly points to the last beta instead of stable.

My fault. CI was breaking the package url when reassigning the branch in the plg url. Fixed and install is working again.

FYI: The beta will be going live today (merged to main) around 6PM EST. If you have any issues let me know before then.

Yea I fixed it from my side in the beta also. just name-spaced escapeHtml to composeEscapeHtml to avoid potential issues in the future. Also that FolderView Plus setup wizard is super cool lol.

I have done work on the dev branch specifically to fix a bug that interfered with that plugin. The beta branch has that fix already. With that said, the beta is closing tomorrow and the changes will be merged to main. I JUST fixed a but that interfered with Folder View Plus so that should also be compatible with the latest beta.

Safest will always be: Compose down on everything. Back up all the compose files and env files. Uninstall current plugin Install new plugin With that said, I have done in place upgrades from the original the the new one with no issues. Going down for all is still safest though.

Check out the beta, it has auto updates, background actions and many bug fixes. Although if everything goes well I'll be merging it tomorrow.