Getting Started
Last updated
Last updated
To get started as developer or contributor to the Elentra Platform you are required to have:
An active GitHub.com account
An approved Elentra Contributor Agreement
A suitable developer workstation
You should also be setup with:
Access to our Slack Team at and the #developers
channel
Access to our Jira tracker at
Subscription to our and mailing lists
If you do not already have an account on GitHub.com, or you would like a separate work-specific account, then please visit and sign up for a new account.
Regardless of whether you would like to use your existing account or create a new one, it is important that you know your correct GitHub.com username and that have you provided your full name within the section on GitHub. Failure to do this may result in delays of approval.
You must have in order to join the ElentraProject
GitHub organization.
While there is no required workstation configuration for Elentra Platform development, there are a number of technologies used by Elentra Consortium developers that dramatically increase productivity and reliability, and promote consistency. The vast majority of these applications are available for macOS, Windows 10+, and Linux workstations.
The elentra-developer
Docker environment is a lightweight, developer-friendly, virtualization layer that should be used to provide a local development environment that closely mimics your production Elentra environment.
While you could install and configure your own local version of Apache, MariaDB, and PHP, this Docker environment is intended to expedite the setup process for most developers and provide a consistent developer experience across macOS, Windows, and Linux workstations.
Category
Software
macOS
Windows
Linux
Virtualization
X
X
X
SCM
X
X
X
Git Client
X
X
Git Client ($)
X
X
X
MariaDB GUI
X
MariaDB GUI
X
X
X
Text Editor
X
X
X
API Client
X
X
X
JavaScript Runtime
X
X
X
Visual Diff
X
X
X
Visual Diff ($)
X
X
Diagram Designer ($)
X
X
X
macOS users can enjoy an expedited Highly Recommended Software Stack setup by running the following commands in Terminal:
While Google Chrome will automatically route *.localhost
DNS requests to your local host, other supported browsers such Firefox, Edge, and potentially Safari may not.
You should add the following Elentra Platform hostnames to your hosts
file, and potentially other Branded Edition hostname's as well (e.g., medtech-1x-me.localhost
).
If you do not already have a 4096 bit SSH key on your workstation then you will need to generate one. Using either Terminal or Git Bash on your host desktop, run:
The defaults provided by ssh-keygen should be fine, including the default ~/.ssh/id_rsa
storage location and an empty passphrase (providing your workstation is properly secured).
If you run ssh git@github.com
from within Terminal or Git Bash and it fails to authenticate with GitHub, then you have a problem.
The Elentra (Admissions, ME, and CPD) source code is obtained via Git source control management from GitHub once your access request has been granted.
Are you running Windows? Before you clone our repositories you must disable Git's autocrlf feature for automatically converting line endings. If you don't do this, your container will not start successfully.
Run the following within Git Bash:
git config --global core.autocrlf false
Using either Terminal or Git Bash on your host desktop, clone the elentra-developer
repository into a directory within your home directory (e.g., ~/Documents
).
Using either Terminal or Git Bash on your host desktop, clone the elentra-1x-me
repository from your Institutional Fork into the ~/Sites
directory, and add the Elentra Consortium as an additional Git remote.
Next, clone the elentra-1x-api
repository into the ~/Sites
directory:
Next, clone the elentra-2x-js
repository into the ~/Sites
directory:
Start the Elentra Developer Docker environment by running the developer setup command within the elentra-developer
Docker directory:
That should be it. Installation of the initial container may take a little while, but when it's complete you can connect to the bash shell of your container by typing:
The following directories are automatically mapped for you in elentra-developer
:
Host Directory
Container Directory
~/Sites
/var/www/vhosts
./elentra-developer/resources/services/elentra/etc/httpd/vhosts.d
/etc/httpd/vhosts.d
./elentra-developer/resources/scripts
/root/.bin
~/.ssh/id_rsa
/root/.ssh/id_rsa
Are you running Windows? Unfortunately, you're going to have an issue with that last one. To work around this Windows permissions issue you will need copy your SSH key into the container by executing the following commands within the container bash shell:
If you are not using our Docker environment make sure that:
You have created the databases on your host database server, and also created a user account with privileges to these new databases.
You have configured your Apache installation with the appropriate local virtual hosts.
Authenticating your elentra-developer
Docker container, and possibly your host computer as well, is necessary in order to install the dependencies used by the Elentra Platform.
Once you have obtained your Institutional Authorization Token, please run the following command (replacing dcdeef40...
with your actual token) within your Docker container:
Within your elentra-developer
Docker container, ensure that you have the develop
Git branch checked out and that you are up to date:
2. Optionally, if you have cloned the elentra-1x-api
repository and want to use this development version instead of the production version, then create a new file named composer-api-dev.json
in your elentra-1x-me
root directory:
Add the following lines to this new composer-api-dev.json
file, if you have created one:
3. Install the Composer dependencies:
4. Optionally, to use the local elentra-1x-api
, use composer update just for that package and then reset changes to the composer.lock
file:
Run the following in the elentra-1x-me
directory, to compile the vite bundle (again in the docker shell):
Elentra Developer Docker Environment
Before gaining access to our source code repositories you must review and sign an . This agreement provides fall-back legal protection for the Elentra Consortium relating to any potential contributions you may make.
Please where you will be asked for your full name, the institution you belong to, your e-mail address, and your GitHub.com username. Once your contributor request has been approved you will receive an invite from GitHub.com to join the organization.
Make sure that you have completely installed the listed above, otherwise a lot of this won't make sense.
Warning: This step can be painful to explain to new developers, so please bear with us. On the plus side it will eventually go away thanks to a that has already been adopted by Google Chrome.
Next, you must add your SSH public key to your GitHub profile in the section. Using either Terminal or Git Bash on your host desktop, run:
Please make sure your SSH Public Key (~/.ssh/id_rsa.pub
) has been added to GitHub's section before proceeding.
Your development environment meets the
As of Elentra Admissions 0.9, Elentra ME 1.13, and Elentra CPD 1.1 our Composer dependencies are managed and installed through a commercial service called Private Packagist - . This service mirrors our dependencies from their original location and provides a reliable, redundant, and consistent dependency source for our deployment processes.
Elentra 1.26 introduces a bundle containing JavaScript dependencies such as jQuery and Bootstrap, which uses NPM to ensure that these libraries stay up-to-date.
If all went according to plan you can now visit this local Elentra ME installation using Chrome, Firefox, Safari, or Edge to proceed with the web-based setup:
provides a consistent and reliable methodology that lets you deploy and roll-back new releases to your servers from your command line or from a CI/CD server.