Public | Automated Build

Last pushed: 2 years ago
Short Description
Full Description



To get a working development environment:

git clone --recursive
cd openexplorer
chmod 777 application/cache
chmod 777 application/logs
cd vagrant
vagrant up

Add the IP to your hosts file:     precise64

If you are not yet an admin for OpenExplorer:

  • go to and log in with the username/pwd that you use for OE
  • click your user picture top left and select Settings
  • view the source of this page (In Chrome its Ctrl-U)
  • look for the USER_ID that's what you need.
  • add your user id to: application/config/admins.php
  • If you tried to login to your local instance before, you shoud clear you chache as some information is stored in the session

Setting the environment up

Your database is not populated with approved expedition(s), so we need to go and set it up.

  • go to http://precise64/admin and log in
  • create a new expedition with a background post
  • go back to http://precise64/admin
  • your expedition should be on the top, check all the 3 check boxes Approved, Featured on Map and Main Feature

Visit http://precise64/ to view the site.

To access the vagrant environment from the terminal, change to the vagrant directory and type

vagrant ssh


Pushing to the master branch will auto deploy the application to the development / staging server.

Pushing to the production branch will auto deploy to the production server (

Since our deploy process is very simple, trying to keep master and production in sync is a good idea. If you are testing on staging (and not just local), you should let the team know not to merge your changes into production. The only time you should need to do this is if there is something you absolutely cannot test on your local machine. This development / staging server acts as a sanity check before pushing to production.

Docker Pull Command
Source Repository