With this on mind, I'll start tweaking it to make possible a seamlessly integration in the future. Is it ok for you both?

Not a problem here.

 

 

Also, as far as ongoing maintenance for the repositories are concerned, I would like to reiterate a statement I made in the Popular Template Repositories thread to any and all repository authors:

 

If you don't send me a PM when you've created a new repository and I don't notice the announcement thread in the forums, your repository will NOT be part of this list. New containers I don't need to be aware of but I do need any new repositories.

 

Also, there is no provisions in the current XML schema for a <Support> tag.  I am handling the maintenance on the support links on a per repository basis.  In other words, if you don't create a support link for the repository as a whole, there will be no support link listed.  If you have separate support threads for each container (which I believe is the best way to do things), then please create a top-level thread that will in turn link to the individual threads.  Something like this: http://lime-technology.com/forum/index.php?topic=39227.0

I've been working on a guide for v5 users upgrading to v6, and I'm just learning about Dockers myself, and getting into areas of which I cannot speak/write from personal experience.  It appears to me that this plugin would be a good recommendation for them.  In your opinions, would it be a fair statement to recommend that this plugin be one of the first plugins they install, or am I jumping to conclusions here?

 

Concerning that, does the Docker support *have* to be turned on first, before adding this plugin?  I've installed it myself, looks great(!), but didn't want to test it without Dockers turned on, in case of unforeseen issues.

 

Happy to hear any suggestions, to help v5 users make the transition.  (Suggestions should probably not be posted in this thread though, could be off-topic for it, PM?)

A quick remark, the page is loaded conditionally, which means it won't be visible when Docker is inactive.

 

And my personal opinion ...

 

Yes, I believe this should be loaded when people start working with dockers. It simplifies the installation of an individual docker or the addition of a complete repository.

 

Perhaps some online at the top (hint) can be added to get novices started!

 

I've been working on a guide for v5 users upgrading to v6, and I'm just learning about Dockers myself, and getting into areas of which I cannot speak/write from personal experience.  It appears to me that this plugin would be a good recommendation for them.  In your opinions, would it be a fair statement to recommend that this plugin be one of the first plugins they install, or am I jumping to conclusions here?

 

Concerning that, does the Docker support *have* to be turned on first, before adding this plugin?  I've installed it myself, looks great(!), but didn't want to test it without Dockers turned on, in case of unforeseen issues.

 

Happy to hear any suggestions, to help v5 users make the transition.  (Suggestions should probably not be posted in this thread though, could be off-topic for it, PM?)

Docker does need to be enabled for the UI to appear.  For those who don't wish to enable docker or for v5 users they can still check out the thread: http://lime-technology.com/forum/index.php?topic=37958.0 

I think the installed docker containers should be at the top of the page instead of "Community Repositories." "Community Repositories," is just so large you have to scroll down forever to check your installed containers. My 2¢

 

Thanks to everyone involved in the making of this plugin. I feel that this plugin greatly enhances the Docker experience. Great Job!

I think the installed docker containers should be at the top of the page instead of "Community Repositories." "Community Repositories," is just so large you have to scroll down forever to check your installed containers. My 2¢

 

Thanks to everyone involved in the making of this plugin. I feel that this plugin greatly enhances the Docker experience. Great Job!

I believe that is a bug in dockerMan and the fix for it has not been released as of yet by LT.  I had the exact same complaint.  (I wound up switching to tabbed view for that reason)

Thanks Squid for letting me take a place on this Plugin development.

 

Just one minor heads up: if your Docker tabs are not in this order, please don't get mad; it will be fixed in the next Dynamix or unRAID's update, ok?

 

Again, thanks a lot Squid!

Ahh ok thanks Squid.

Docker does need to be enabled for the UI to appear.  For those who don't wish to enable docker or for v5 users they can still check out the thread: http://lime-technology.com/forum/index.php?topic=37958.0

A quick remark, the page is loaded conditionally, which means it won't be visible when Docker is inactive.

 

And my personal opinion ...

 

Yes, I believe this should be loaded when people start working with dockers. It simplifies the installation of an individual docker or the addition of a complete repository.

 

Thanks to both of you.  I've added it to the guide, and recommended it, with a warning about enabling Docker support first.

 

Perhaps some online at the top (hint) can be added to get novices started!

I tried, but my brain was unable to construct a complete thought from this.  Is my brain fried, or is there a word or two missing?

Perhaps some online at the top (hint) can be added to get novices started!

I tried, but my brain was unable to construct a complete thought from this.  Is my brain fried, or is there a word or two missing?

lol I had the same problem and thought about it for a couple of hours and then figured maybe I should add some instructions to the OP - which I did.

Perhaps some online at the top (hint) can be added to get novices started!

I tried, but my brain was unable to construct a complete thought from this.  Is my brain fried, or is there a word or two missing?

lol I had the same problem and thought about it for a couple of hours and then figured maybe I should add some instructions to the OP - which I did.

 

Sorry for all the confusion

 

I meant to say, in unRAID v6 there is the new online help system present, this can be used to give more information to the user.

 

Guys, I'm adding support to two new tags on XML templates: <Overview> and <Support>.

 

<Overview> Should be a nice tagline describing what the application does and, if there's more than one container of that app, what makes it different.

 

<Support> Should be a link to a forum thread.

 

This can make things a lot easier for us and more informative for the users.

 

Thanks in advance for supporting this.

Guys, I'm adding support to two new tags on XML templates: <Overview> and <Support>.

 

<Overview> Should be a nice tagline describing what the application does and, if there's more than one container of that app, what makes it different.

 

<Support> Should be a link to a forum thread.

 

This can make things a lot easier for us and more informative for the users.

 

Thanks in advance for supporting this.

 

what about the idea of a <Instructions> tag to denote any specific instructions with said docker? i got a couple of cases where i have dockers that require fairly specific setup, this could be a nice way of highlighting this to the end user by having it in its own block, separate to the overview/description blocks

Guys, I'm adding support to two new tags on XML templates: <Overview> and <Support>.

 

<Overview> Should be a nice tagline describing what the application does and, if there's more than one container of that app, what makes it different.

 

<Support> Should be a link to a forum thread.

 

This can make things a lot easier for us and more informative for the users.

 

Thanks in advance for supporting this.

 

what about the idea of a <Instructions> tag to denote any specific instructions with said docker? i got a couple of cases where i have dockers that require fairly specific setup, this could be a nice way of highlighting this to the end user by having it in its own block, separate to the overview/description blocks

 

These two tags are still unofficial. I'm trying to change some of the Docker schema, just waiting LT's approval. Maybe an <Installation> tag would be more suitable?

Guys, I'm adding support to two new tags on XML templates: <Overview> and <Support>.

 

<Overview> Should be a nice tagline describing what the application does and, if there's more than one container of that app, what makes it different.

 

<Support> Should be a link to a forum thread.

 

This can make things a lot easier for us and more informative for the users.

 

Thanks in advance for supporting this.

 

what about the idea of a <Instructions> tag to denote any specific instructions with said docker? i got a couple of cases where i have dockers that require fairly specific setup, this could be a nice way of highlighting this to the end user by having it in its own block, separate to the overview/description blocks

 

These two tags are still unofficial. I'm trying to change some of the Docker schema, just waiting LT's approval. Maybe an <Installation> tag would be more suitable?

 

I've started putting the <support> tag in to my xml's

 

 

I've started putting the <support> tag in to my xml's

 

Thanks a lot for this!

Guys, I'm adding support to two new tags on XML templates: <Overview> and <Support>.

 

<Overview> Should be a nice tagline describing what the application does and, if there's more than one container of that app, what makes it different.

 

<Support> Should be a link to a forum thread.

 

This can make things a lot easier for us and more informative for the users.

 

Thanks in advance for supporting this.

 

what about the idea of a <Instructions> tag to denote any specific instructions with said docker? i got a couple of cases where i have dockers that require fairly specific setup, this could be a nice way of highlighting this to the end user by having it in its own block, separate to the overview/description blocks

 

These two tags are still unofficial. I'm trying to change some of the Docker schema, just waiting LT's approval. Maybe an <Installation> tag would be more suitable?

 

I'd echo a tag for installation details, setup details etc.... and reiterating whether container needs another container or app, such as mariadb etc......

New Version Available

 

With an eye towards future features, the folders have been rearranged on this plugin.  The plugin file has also been changed for clarity.

 

For those users who have already installed the version prior to today's release, you must uninstall it before installing this version.

 

Going forward, the URL for the plugin file is now:

 

https://raw.githubusercontent.com/Squidly271/repo.update/master/plugins/community.repositories.plg

 

 

Major New Features:

 

- The list is now no longer the first displayed when you enter the docker tab.  It is now properly displaying 3rd.

- The ability to search containers.  ie: enter "NZB" into the text area, press enter and all of the containers dealing with NZB's will be displayed.  The search term must be a minimum of 3 characters long.

 

 

 

New Version Available

 

With an eye towards future features, the folders have been rearranged on this plugin.  The plugin file has also been changed for clarity.

 

For those users who have already installed the version prior to today's release, you must uninstall it before installing this version.

 

Going forward, the URL for the plugin file is now:

 

https://raw.githubusercontent.com/Squidly271/repo.update/master/plugins/community.repositories.plg

 

 

Major New Features:

 

- The list is now no longer the first displayed when you enter the docker tab.  It is now properly displaying 3rd.

- The ability to search containers.  ie: enter "NZB" into the text area, press enter and all of the containers dealing with NZB's will be displayed.  The search term must be a minimum of 3 characters long.

 

I'm not sure of the correct term, but this latest iteration "scales" better in my browser, before if there was a long description for a docker it would make the page wider than my browser window and i would have to use the horizontal slider to see all the info, this version doesn't do that.

A purely cosmetic thing this, would it be possible to have the repo authors names indented a little from the left edge ?

 

@Squid , @gfjardim , @limetech

 

At the bare minimum could you make the Community Repositories to be Collapsable?

 

Any chance you could please relocate the Community Repositories to be under the Docker Settings section when Tabbed display is not enabled? It's a hassle to have to scroll past a section I hardly use just to get to a section that I use more often.

 

I can understand you putting it where you did because it's underneath the official repositories, but I use the Docker Settings far more often than either of the Repositories section.

 

Thanks.

 

A small issue, the Update Repositories button is insisting it still belongs in the number one position, creating a little conflict.  Could you convince it to join its crowd in third position?

@Squid , @gfjardim , @limetech

 

Any chance you could please relocate the Community Repositories to be under the Docker Settings section when Tabbed display is not enabled? It's a hassle to have to scroll past a section I hardly use just to get to a section that I use more often.

 

Thanks.

 

Already done in this version.

 

PS: Ok, my bad. Docker Settings got moved away from the Docker menu in the latest version of Dynamix. Because of that we don't fix it.

 

I will release an update soon.

 

A small issue, the Update Repositories button is insisting it still belongs in the number one position, creating a little conflict.  Could you convince it to join its crowd in third position?

 

Already addressed this, will release an update soon.

Guys, I'm adding support to two new tags on XML templates: <Overview> and <Support>.

 

<Overview> Should be a nice tagline describing what the application does and, if there's more than one container of that app, what makes it different.

 

<Support> Should be a link to a forum thread.

 

This can make things a lot easier for us and more informative for the users.

 

Thanks in advance for supporting this.

 

Got this on my list.. should get to it shortly....

hi gfjardim, all done on my end, for the time being i have just duplicated what i had in the description tag and put it in the new overview tag as im assuming we will need both until all users are using one or the other.

hi gfjardim, all done on my end, for the time being i have just duplicated what i had in the description tag and put it in the new overview tag as im assuming we will need both until all users are using one or the other.

 

Thanks binhex. Sent you a Pull Request of minor layout fixes.