Installed duplicate docker app ophaning existing app. Old app unavailable from templates or Previously Installed

[Bondfire]

Ok, so I made a pretty big mistake tonight and I installed a duplicate docker image (same name from a different repo, hatio vs linuxserver) which instantly orphaned my existing app. 

 

Seeing my mistake I read through several posts here and saw that it is ok to delete and image and either add a new container from the my-templates dropdown or to add from the community 'previously installed' section. 

 

So I deleted both the new app and the orphaned app, however since this app was the same name, only the new app (which I do not want) is available in 'previously installed' and the same thing in thing in the template dropdown when adding a container.  All the config is for the new app.  I can easily tell because they each have slightly different configs.  

 

At this point I'm concerned that the new app overwrote everything from the old and I'm totally screwed.  Please tell me that's not the case! 

 

FYI - i'm not specifying the app name here because i'm not sure if it against forum terms to name apps, but they were both installed via community apps.

[Squid]

It's how the system works.  If you pull an app named "Plex", the template is called "my-plex"  If you pull another app named "Plex", it overwrites the existing template.  If it was Plex vs PlexMediaServer then there's no problems

 

But, the important stuff is all within the appdata share, so just install the app you want, set it up again with the appropriate paths etc and you should be good to go.

[Bondfire]

Squid you are awesome.  Thanks for being so active on this community.  I also did this last night, but was afraid it might overwrite something.  Just tried now and it worked perfectly.  

 

Any thoughts to giving a warning of some kind when adding an app that has a name conflict?  No need to respond here, just a thought.  Thanks again!