dockerPolice

@Josh.5 FYI, Someone at Datahoarding has created a template for unManic and published this on CA. I believe earlier you had stated that you did not wish unManic to be published as of yet. Is this still the case? Should the template be removed from CA? Ideally though if you would like it in CA it would be better for it to be published within your own repository.

It should be noted that if the same issue occurs again that caused urBackup to be pulled from CA happens again, this app will also get pulled from CA immediately

Never could figure out why you've never wanted it published in CA...

Changed via moderation. If/when the template gets updated, I'll reverse my changes

Is all that's wrong is the container port needs to be 22 not 9022?

Yes. Linuxserver.io is rather hypocritical by having their docker compose file directly reference elasticsearch in it, and yet not publishing a template for unRaid.😡

Since PlexInc never seemed to me to be super receptive on templates, I've unilaterally changed the URL for Plex to point to the root of their support thread. You'll be able to hit it via the Apps Tabs, Installed Apps. @Squid will have to do something about the fact that now the URL listed in the Docker / Dashboard pages are incorrect

Since it's not explicitly mentioned, is it recommended for all users of the old app to now migrate to the new one? Is the old app now deprecated?

Ok I see now that they are the same repo, just different tags will rectify

Seems to me that your container is the better choice. Especially considering the first item, and the fact that you were last on 5 minutes ago I try and look for abandoned projects, hence my suggestion to get in touch with Squid

Fair to say then that the existing container does not work with updated unRaid versions? Why not just PM @Squid and create a new repository for CA. Then we can deprecate fannigert's and replace it with yours.

Aren't you being rather hypocritical then because the docker compose file listed for diskover does have elasticsearch: container_name: elasticsearch image: docker.elastic.co/elasticsearch/elasticsearch:5.6.9 volumes: - ${DOCKER_HOME}/elasticsearch/data:/usr/share/elasticsearch/data environment: - bootstrap.memory_lock=true - "ES_JAVA_OPTS=-Xms2048m -Xmx2048m" ulimits: memlock: soft: -1 hard: -1 redis: container_name: redis image: redis:alpine volumes: - ${HOME}/docker/redis:/data Shouldn't the references to elasticsearch and redis be removed from the yaml for the same reasoning you just gave for not having a template? Isn't fundamentally a yaml a template?

So you published a template that has a prerequisite for which you don't have a template!?!

Yeah, its one thing that I hate seeing some template maintainers do 😡

That's a shame. Probably best course of action though is to deprecate this application (it isn't even the 64 bit executable, so much slower than it should be) and hope to hell that @CHBMB et al feel generous one day and pop out a replacement over their morning coffee one day and help the world one day become a better place.

Probably not

Sparklyballs' old version has now been deprecated in favour of yours.

I concur.

Due to the DMCA now in place on this application, CA has a comment on both the lsio and binhex versions (although Binhex's is still running due to his being a static image). Hopefully someone will let me know if/when this is resolved one way or another.

While I understand why you guys don't do this, as a whole, changelogs on docker templates (the plugin guys are all awesome though at it) not being updated is far and away my biggest pet-peeve. To the point that I'm contemplating removing the date updated text from the description and leaving it only displaying in the popup. Pop up already has this in it:

Did you read the moderator comments? It explicitly states the container is deprecated. Sent from my Nexus 5X using Tapatalk

http://i46.photobucket.com/albums/f109/squidaz/Untitled_zps4w83onkv.png[/img] If you really don't want people to use the template, then it should get deleted from the repository...

If the alleged perp strayed into docker territory, it would have been all over far sooner. As it stands, it was pluginCop (pfft) who, as usual was slow on the draw. http://images.wisegeek.com/arrested-in-handcuffs.jpg[/img]