Language Forge and Scripture Forge represent different websites, but have the same code base stored in seperate repositories for the purpose of version control and issue tracking. Since they are related repos it is easy to merge from one to the other.
Our recommended development environment for web development is Linux Ubuntu GNOME. Choose either the Vagrant VM Setup or the Local Linux Development Setup. Even though the Vagrant VM Setup is definitely easier because it always installs from a clean slate on a new virtual box, we recommend doing development on your local development machine. This approach will make your page loads approximately 50 times faster. In my tests 100 ms (local) vs 5000 ms (Vagrant / Virtualbox). The reason for this is that Virtualbox gives access to the php files via the VirtualBox shared folder feature. This is notoriously slow.
Clone this repository to your host machine and and vagrant up
the Xenial box. We intentionally postpone provisioning on initial boot so the Virtualbox guest additions
updates don't interfere with the provisioning process.
git clone https://github.com/sillsdev/web-languageforge web-languageforge --recurse-submodules
cd deploy/xenial
vagrant up --no-provision
Once the shell notifies the Virtualbox guest additions have been updated, power down the Xenial box.
Now, vagrant up with provision to install and deploy
vagrant up --provision
Proceed to Language Forge Configuration File and follow the rest of the steps in this README.
Start with the Ansible-assisted setup described here to install and configure a basic development environment.
After creating your Ansible-assisted setup, clone this repository from your home folder...
mkdir src
cd src
mkdir xForge
cd xForge
git clone https://github.com/sillsdev/web-languageforge web-languageforge --recurse-submodules
The --recurse-submodules
is used to fetch many of the Ansible roles used by the Ansible playbooks in the deploy folder. If you've already cloned the repo without --recurse-submodules
, run git submodule update --init --recursive
to pull and initialize them.
If you want to run an independant repo for scriptureforge, clone its repo also...
git clone https://github.com/sillsdev/web-scriptureforge web-scriptureforge --recurse-submodules
Otherwise just create a symbolic link between languageforge and scriptureforge...
ln -s web-languageforge web-scriptureforge
Change the variable mongo_path: /var/lib/mongodb in deploy/vars_palaso.yml
. Set it to a location where MongoDB should store its databases.
- Vagrant VM Setup: uncomment line 6 and comment line 5
- Local Linux Development Setup: uncomment line 5 and comment line 6 (or whatever is appropriate on your system, its best to have Mongo store databases on your HDD rather than SSD). Make sure the
mongodb
user has permission to read and write to the path you specify.
Run the following Ansible playbooks to configure Ansible and run both sites.
cd web-languageforge/deploy
ansible-playbook -i hosts playbook_create_config.yml --limit localhost -K
ansible-playbook -i hosts playbook_xenial.yml --limit localhost -K
If you run into an error on the ssl_config : LetsEncrypt: Install packages
task, run the playbook again and that task should succeed the second time it is run.
Install node_modules used to build Sass files and run E2E tests
cd web-languageforge
npm install
gulp sass
Manually edit the Language Forge config file
sudo gedit /etc/languageforge/conf/sendreceive.conf
and modify PhpSourcePath to
PhpSourcePath = /var/www/virtual/languageforge.org/htdocs
Install Oracle Java JDK 8
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer oracle-java8-set-default
Download the Eclipse installer, extract the tar folder and run the installer.
tar xvf eclipse-inst-linux64.tar.gz
cd eclipse-installer
./eclipse-inst
From the installer, select Eclipse IDE for PHP Developers
Create a launcher shortcut from your home directory
gedit .local/share/applications/eclipse.desktop
Replacing your USERNAME, paste the content below and save
[Desktop Entry]
Name=Eclipse
Type=Application
Exec=/home/USERNAME/eclipse/php-neon/eclipse/eclipse
Terminal=false
Icon=/home/USERNAME/eclipse/php-neon/eclipse/icon.xpm
Comment=Integrated Development Environment
NoDisplay=false
Categories=Development;IDE;
Name[en]=Eclipse
Even though we no longer use Eclipse for web development, we install the MonjaDB plugin for browsing and updating MongoDB.
Once the MonjaDB plugin is installed, access MonjaDB
from the Eclipse menu and select Connect
. Set the database name to scriptureforge
(both sites use the same database). Keep the other default settings and click OK
and you should see the contents of the database.
Download PhpStorm, extract the tar file and install. You may need to modify newer version numbers accordingly...
tar xvf PhpStorm-2016.2.1.tar.gz
sudo mv PhpStorm-162.1889.1/ /opt/phpstorm
sudo ln -s /opt/phpstorm/bin/phpstorm.sh /usr/local/bin/phpstorm
# launch
phpstorm
LSDev members can contact their team lead to get the SIL license information. PhpStorm also has an option Evaluate for free for 30 days.
Download the PhpStorm plugin for EditorConfig and then install:
File --> Settings --> Plugins --> Install plugin from disk
This uses the .editorconfig
file at the root folder to enforce coding standards.
Also enable JSCS:
File -> Settings -> Languages & Frameworks -> JavaScript --> Code Quality Tools --> JSCS
Set the Enable checkbox
Set Node interpreter to usr/local/bin/node
Set JSCS package to /usr/local/bin/jscs
Set Search for config(s) radio button to .jscsrc or .jscs.json
Set the Code style preset dropdown to Airbnb
Modify /usr/local/lib/node_modules/jscs/presets/airbnb.json
and change "requireTrailingComma": { "ignoreSingleLine": true }
to
"disallowTrailingComma": true,
Launch PhpStorm.
Click Create New Project from Existing Files. Leave the default option (Web server is installed locally, source files are located under its document root) and click Next.
From the Create New Project: Choose Project Directory dialog, browse to the web-languageforge
directory, then mark it as Project Root (using the Project Root
button in the toolbar) and click Next.
From the Add Local Server dialog set
Name: languageforge.local
Web server root URL: http://languageforge.local
--> Next --> Finish
Ansible will have installed Xdebug, but you still need to manually edit /etc/php/7.0/apache2/php.ini
and append the following lines:
[Xdebug]
xdebug.remote_enable = 1
xdebug.remote_port = 9000
xdebug.idekey=PHPSTORM
For more detailed installation instructions, reference the Xdebug wizard
Setting PHP Interpreter from PhpStorm
File --> Settings --> Languages & Frameworks --> PHP
From the dropdown to PHP language level, select 7
For Interpreter, click "..." to browse, then "+"
Name: PHP 7
PHP executable: /usr/bin/php
Adding Servers from PhpStorm
File --> Settings --> Languages & Frameworks --> PHP --> Servers Click the "+" to add the following Name & Hosts:
- default.local
- languageforge.local
- scriptureforge.local
Restart apache2
sudo service apache2 restart
Install the Xdebug helper extension which adds a bug icon to the top right area of Chrome extensions.
Right-click to select Options and set IDE key
PhpStorm PHPSTORM
When it's time to Debug, check that the bug icon is green for Debug.
Then, from PhpStorm, click the telephone icon near the top right for Start Listening for PHP Connections.
Reference for Integrating Xdebug with PhpStorm.
Install the LiveReload extension.
Then from PhpStorm, click View->Tool Windows -> Gulp
When you want LiveReload running, double-click the reload Gulp task. Then in the LiveReload chrome extension, left click to enable it. A solid dot in the circle means the plugin is connected. Now when an applicable source file is changed and saved, it should trigger an automate page reload in the browser.
Unit testing currently uses PHPUnit which was already installed by composer.
File -> Settings -> Languages & Frameworks -> PHP -> PHPUnit
Under PHPUnit Library, select Use Composer autoloader
option
For Path to script
browse to web-languageforge/src/vendor/autoload.php
Under Test Runner
Select Default configuration file and browse to web-languageforge/test/php/phpunit.xml
Select Default boostrap file and browse to web-languageforge/test/php/TestConfig.php
To run tests, browse to the project view, right-click test/php
and select Run php
.
Note: at least one test will fail if the LFMerge (send/receive) program is not installed and available. This is OK as long as you are not testing Send/Receive functionality.
From the web-languageforge
directory
npm install
gulp test-e2e-webdriver_update
From the web-languageforge directory, start webdriver in one terminal:
gulp test-e2e-webdriver_standalone
Then to run languageforge tests in another terminal:
./rune2e.sh lf
To run scriptureforge tests:
./rune2e.sh sf
To test a certain test spec, add a parameter --specs [spec name]
. For example,
./rune2e.sh lf --specs lexicon-new-project
will run the the lexicon-new-project.spec.js tests on languageforge.
To add more verbosity during E2E tests, add a parameter --verbosity true
(For installation of npm see https://github.com/nodesource/distributions)
Install gulp dependencies by running from the repo root (where):
npm install
To install the mongodb databases locally, run:
gulp mongodb-copy-prod-db
If you want to start over with your mongo database, you can use the factory reset script like so (this will delete all data in the mongodb):
cd scripts/tools
./FactoryReset.php run
After a fresh factory reset, there is one user. username: admin password: password
Occasionally developers need to update composer, bower or npm. If something isn't working after a recent code change, try to update the dependencies:
In src/: bower install
In the root folder: npm install
In src/: composer install