Module installer envisions giving the community the option to install enhancements as compartmentalized code in order to help maintain and manage installations. Thus enabling contributors to release features as modules which users can opt to use without hindering the basic structure and direction and the common project.
This enables developers to release features without effecting the core structure of the OEMR project and mitigating risks only to their individual installations. This would enable different installations to have multiple solutions on the same installation and implement solutions to real business problems faced by their practices only ie users will have the ability to implement a calendar which has a certain feature or look that is not viable to any other practice.
This gives the community a flavor of multiple solutions; of which some can be eventually be made of the main source code when the project leads have time to complete their testing and review. This is could also lead to vendors allowing third party modules made available to individual users for a price thus increasing the acceptance of the product leading to similar scenario like the app marketplace.
Two documents are also attached to help with installation and working:
1. Module Installer - Installation Guide
2. Configuring Modules from OEMR
Git HUB Path:https://github.com/zhhealthcare/openemr/commit/07470e70c79663883a910dd466fa73e1cc767363
Attached Module Installation guide
Hi,
Would be much better to separate this commit into the following:
1. A commit that brings in the standard ZEND framework.
2. A commit with your work to integrate it.
Otherwise a code review is going to be very difficult (2000+ files).
thanks,
-brady
OpenEMR
Also,
On quick testing, there is no icon in the Modules left nave menu and when I click on the Manage Modules link (only link there), I get following error:
Not Found
The requested URL /openemr/interface/modules/zend_modules/public/Installer was not found on this server.
-brady
OpenEMR
Hi brady,
We will commit it soon.
Regarding the error, there is a set of system requirements that needs to be applied for the proper working of the zend. Please check the following link for details.
https://sourceforge.net/p/openemr/code-review/_discuss/thread/28a7e409/5358/attachment/Module%20Installer%20Installation%20Guide.pdf
Hi,
Committed new branch
ModuleInstaller_V1
to git hub. This branch have two commits first one for Zend libraries and second commit for the Module Installer.Git Hub Path:https://github.com/zhhealthcare/openemr/commit/ModuleInstaller_V1
Thanks And Regards
ZHHealthcare
www.zhservices.com
We don't want all of Zend duplicated in the distribution. Can't you do this in a way that begins with a normal installation of Zend as commonly distributed? Also since the changes to existing OpenEMR are minimal and the requirements including PHP 5.3 and Zend are a major departure, I think better for this to be distributed as a separate package.
Hi,
It's been awhile and I want to get back to this review. Do we have it on recent codebase. Also, can we get code to review for the currently supported modules.
thanks,
-brady
Hi Brady, i'm having the same issue, have you managed to solve this?
Can you paste here the apache2.conf lines you've put in?
thanks
Hi,
If you are not using alias's in apache, then should work by just configuring Zend rewrite and allowoverride:
http://www.open-emr.org/wiki/index.php/Zend#Configuring_Zend
A problem I ran into with the ubuntu openemr packages where a alias was used, required migrating the .htaccess Zend file into the apache config and hardcoding the entire path for the RewriteRule setting:
https://github.com/openemr/openemr/blob/master/contrib/util/ubuntu_package_scripts/production/openemr.conf
Note here is the Zend .htaccess file:
https://github.com/openemr/openemr/blob/master/interface/modules/zend_modules/public/.htaccess
-brady
Many thanks friendo, i'll go over it.
Have a great day :)
On Thu, Mar 24, 2016 at 8:29 AM, Brady Miller bradymiller@users.sf.net
wrote:
Related
Code Review: #220