.....works well with the way my brain is wired.....
Also, I would love to port openemr, https://www.open-emr.org/ , an electronic health record. However, I am a doctor, not a programmer, hence I would need guidance.
From today, you will be wiring your brain with software development .
it's quite the same : A doctor implants artificial organs, a FreeBSD-Programmer implants code fragments, it's all about copy&paste Ha Ha
get your fork of :
GitHub - openemr/openemr: The most popular open source electronic health records and medical practice management solution.
The most popular open source electronic health records and medical practice management solution. - openemr/openemr
github.com
and follow their instructions to install from source:
Code:
composer install --no-dev
npm install
npm run build
composer dump-autoload -o
FreshPorts -- www/node: V8 JavaScript for client and server (meta port)
Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. Node.js' package ecosystem, npm, is the largest ecosystem of open source libraries in the world.
www.freshports.org
FreshPorts -- devel/php-composer: Dependency Manager for PHP
Composer is a tool for dependency management in PHP. It allows you to declare the dependent libraries your project needs and it will install them in your project for you.
www.freshports.org
now you begin debugging .. you can fix bugs directly in your master-branch
or make a new branch and call it e.g. 'freebsdport' .
if you find bugs in npm/composer/php or elsewhere ,
you'll write a bug-report :
if you have fixed the bug you'll send a git-diff as an attachment to your report.
developers are normally not here in the forum.
Subscribe to your appropriate freebsd-mailing list to get in touch with devs.
but more interesting for your first steps:
I saw you're the author here :
OpenEMR with nginx and php-fpm - OpenEMR Project Wiki
www.open-emr.org
you should talk to those openemr/node/php -devs if you have code-specific topics.
you normally do this in the issues-tab of openemr-upstream :
Issues · openemr/openemr
The most popular open source electronic health records and medical practice management solution. - Issues · openemr/openemr
github.com
you`ll make a git-PR(pull request)
to openemr-upstream if opememr is interested in developing the freebsd-port with you.
the last step for committing a freebsd-port is to send a review to ours Phabricator
after you`ve made your ports-configuration (Makefile etc.), don't think about it for now..
you'll do that if you're finished with getting openemr running under FreeBSD.
But with a little luck there are only few bugs to fix in openemr and you can begin with your ports-configuration-steps...
by the way , I have nothing to do with openemr and never used it but those are the general steps you normally go for a fbsd-port which has its sources on git.
good luck !
Regards
Klaus
--- edit :--
ah, forgot :
if you want, I'll add your port-request to :
https://wiki.freebsd.org/WantedPorts adding your name under : 'Who is working '
.. or you can add it yourself by contacting :
.. oh, one moment, after I took a closer look to your https://www.open-emr.org/wiki/index.php/OpenEMR_with_nginx_and_php-fpm tells me: you got it running under FreeBSD 12.1, great !
I recommend to take a look at e.g. :
https://reviews.freebsd.org/source/ports/browse/branches/2020Q2/www/
to learn of what a port consists.... then try to write your Makefile etc. and subscribe to ports mailing list if you have questions... finally you subscribe to phab and your port will be reviewed. looking to your expertise with openemr/nginx you won't have much problems writing the fbsd-port... so welcome to the bsd-dev- hell ...
normally devs work under FreeBSD 13- current and backport ( called MFC) to lower versions. So if you maintain a port the above said (working with the git-source of openemr/npm etc.)) will probably not change because you will upgrade your port to newer versions and fix bugs, so your git-sources-upstream would/should be the base for your port.... while you can apply patches to your port in the ports-tree...
...
----------