If you have several OTRS instances like "testing", "staging" and "live" where "testing" is the instance for developer, "staging" for QA and "live" for public, InstanceAsRepository can be a great module for you. You can configure "testing" to be a module repository for "staging" and "staging" as a module repository for "live".
When you install a new module on "testing" with version 3.3.1 and your testing were fine, you can approve that module. From now on the "staging" instance can see that module in the Package Manager. When you install 3.3.2 on "testing", "staging" can still see only 3.3.1 until you approve 3.3.2. When you find an error in 3.3.2 before you installed in on "staging", you can revoke the approval and "staging" can only see 3.3.1 then.
http://opar.perl-services.de/dist/InstanceAsRepository
New Module: InstanceAsRepository
-
- Znuny guru
- Posts: 5018
- Joined: 13 Mar 2011, 09:54
- Znuny Version: 6.0.x
- Real Name: Renée Bäcker
- Company: Perl-Services.de
- Contact:
New Module: InstanceAsRepository
Perl / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de