![]() Better marketing to raise awareness of plugins and dispel these sorts of perceptions, I believe, is what is also required for the iocage-based plugin system to become truly successful. whether it's true or not, is that plugin developers are 'invisible' and operate at arm's length to the forum. There's no fanfare when a new plugin is made available. I just had a look at the current set of plugins and noticed some new plugins that I had not seen before. It's also not altogether clear, when you look at the collections, who the plugin developers are, or how to get in touch with them. Yes, I'm aware that there is a plugin sub-forum, but it doesn't appear to marry up nicely with the plugins that are currently available in the Community and IXsystems plugin collections. There is a discussion area associated with each resource where community members can contact him directly for advice, or to seek advice from, or share experiences with, other users of the resource. Compare this, for instance, with the scripted resources that has made available for community use. On the flip side, I have to say that it isn't obvious to the casual user how to contact the plugin developer to report issues, suggest improvements, or seek advice. Just to add to the discussion, missing features are just one side of the coin. With jails, I need to enter the jail's IP address and advertised application port in a browser to do the same. What I do miss about plugins is the ability to access the application through the plugin. This action does not affect existing client metadata and backup data.Ĭlick to expand.Thank you, Jurgen, for your insight and balanced viewpoints on the world of plugins. At this stage, if a new version becomes available, it's easy enough to destroy the jail and run the script again to acquire the new version. When I have some time, I'd like to add in a check for, and automatically update to, newer versions of rslsync. This scripted version addresses these limitations. Using the rslsync plugin made it cumbersome to deal with these issues. The issue was finally resolved when 2.7.0 was released (we're currently at v2.7.2). The workaround at the time was to revert to v2.6.1. I recall there was an issue with syncing files larger than 4GB in v2.6.3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |