The source of the OpenRoberta Lab is stored in the Github repository 'openroberta-lab'.
The steps below explain how to get started with the sources. If you just want to run the server locally, please have a look into the Wiki - Installation. If you want to contribute, please get in touch with us, see Wiki - Community, before you start.
After a fresh git clone you get the openroberta-lab project folder. It includes almost everything you need to setup and extend your own openrobertalab server. License information is available in the docs folder.
Things you need on your computer:
- Java >= 1.8
- Maven >= 3.2
- Git
- Web browser
If you would like your local server to compile code for the different systems, you need to install additional software (crosscompilers, libraries, ...):
on Ubuntu:
- Arduino based robots
sudo apt-get install libusb-0.1-4
sudo apt-get install binutils-avr gdb-avr avrdude
- install avr-gcc
- NXT
sudo apt-get install nbc
- Calliope
sudo apt-get install srecord libssl-dev
- install the latest gcc-arm-none-eabi
- micro:bit
pip install uflash
(to install pip runsudo apt install python-pip
)
- EV3 c4ev3
sudo apt-get install g++-arm-linux-gnueabi
- Edison
sudo apt-get python
(Python 2 is needed, it is calledpython
for Ubuntu 18.04)
- Bionics4Education
- install xtensa-esp32-elf
on Windows:
- Arduino based robots
- install avr-gcc
- Calliope
- install gcc-arm-none-eabi
- install srecord
- micro:bit
- install Python 3
pip install uflash
- Edison
- install Python 2
- Bionics4Education
The crosscompiler needs resources to work properly (header files, libraries, ...). These resources change little over time and are stored in the 'ora-cc-rsc' repository.
Please clone that directory. When the openroberta-lab server is started, you have to supply the path to these resources (see below). If the resources are not available, everything works fine (writing programs, import, export, creating accounts, etc.), but running programs on real robots doesn't work, because the crosscompiler will fail.
Please also check our wiki for detailed installation instructions, development procedure, coding conventions and further reading. We also use the github issue tracking system. Please file issues in the main project openroberta-lab.
git clone https://github.com/OpenRoberta/openroberta-lab.git # get the repository
cd openroberta-lab # cd into repository
mvn clean install # generate the server
Might take some time. The last lines of a successful build looks like:
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:16 min
[INFO] Finished at: 2018-01-07T13:05:00+02:00
[INFO] Final Memory: 60M/540M
[INFO] ------------------------------------------------------------------------
If you have a fresh clone of the server, make sure that the OpenRobertaServer folder has a subfolder db-embedded with the database inside. If you don't have a database, you can create an empty database with
./ora.sh create-empty-db
If you try to create a new database, but one exists, the old one is not changed and the command has no effect. The new database is found in the folder OpenRobertaServer/db-embedded.
./ora.sh [-oraccrsc <optional-path-to-crosscompiler-resources, defaults-to '../ora-cc-rsc'>] start-from-git
Start your browser at http://localhost:1999 That's it!
Often you want to run an openroberta installation of a fixed version for a long time. This is easy. Lets assume, that you want to use the (non-existing) directory /data/my-openroberta.
mvn clean install # generate the server in the git repo
./ora.sh export /data/my-openroberta gzip # export to the target directory. gzip compresses the static web resources fpr better performance.
cd /data/my-openroberta
./admin.sh create-empty-db # create an empty db at ./db-server - of course you may copy an old database to that location
./admin.sh start-server # spawns two processes: a database server and the openroberta jetty server
The following administrative commands are useful:
./admin.sh backup ./admin/dbBackup # create a backup in the folder given as parameter. Copy the tgz-file to another machine (cron will automate everything)
./admin.sh shutdown # shutdown of the database. The openroberta jetty server continues to run, but database access will fail, of course.
# get the pid of the server using **ps** and execute a **kill <pid>** to stop the server
./admin.sh sqlgui # access the database concurrently with the server. Be careful not to block the server, e.g. by an update without commit
# the database server must be running, of course.
./admin.sh sqlguiEmbedded # if the database server is stopped, this allows to access the database. The access is exclusive. Terminate the sql client
# before you start the openroberta installation again.
This kind of installation is useful for small productive systems (e.g. an a RaspberryPi). Large productive systems,
- if you want to run many servers (maybe of different versions) concurrently,
- if you want to use continous deployment based on incoming git commits
- ...
needs more support as available with the scripts ora.sh and admin.sh. We deploy our openroberta installation using docker. It is described in detail in file Docker/README.md. Inside the Docker directory everything is contained which is needed to create images and start them. You can try it. If there are problems, you can contact us.
OpenRoberta needs a database to store user accounts, programs, etc. It uses HyperSQL. Other database systems (MySql, Postgres, ..., oracle, db2, ...) would work, too. There are no special requirements on the database, that would exclude one. Only a Hibernate binding and a full transaction support is needed.
As described above either db-embedded or db-server is the name of the directory, in which the database files reside. Sometimes the database must be upgraded, e.g. new tables or new columns for new features. The java class DbUpgrader is responsible for detecting the need for an upgrade and executing the upgrade (once and only once) when the database is openend at server startup. If a database needs more than one upgrade, this is no problem. They are executed one after the other.
There is no need for the developer to care about database upgrades. But note, that is not possible to upgrade databases with versions before 3.1.0. As this a very old version, this should never be necessary. If this is needed, please contact the OpenRoberta team.
You can also import the project into IDE's such as Eclipse and IntelliJ!
You can follow the test status here.
Development happens in the develop branch. Please sent PRs against that branch.
git clone https://github.com/OpenRoberta/openroberta-lab.git
cd openroberta-lab
git checkout develop
The project OpenRobertaServer contains the server logic, that accesses
- a database with Hibernate-based DAO objects
- plugins for various robots which are supported in OpenRoberta
- services for browser-based clients
- services for robots connected to the lab either by Wifi or USB
The server is made of
- an embedded jetty server exposing REST services
- the services are based on jersey
- JSON (sometimes XML or plain text) is used for data exchange between front, robots and server
Furthermore, the project OpenRobertaServer contains in directory staticResources for the browser client
- HTML and CSS
- Javascript libraries based on jquery and bootstrap for the frontend
- assertions (DBC), ajax-based server calls (COMM), logging (LOG) and
- javascript resources for blockly
- controller and models written in Javascript, which implement the GUI
To run tests, use mvn test
. Running mvn clean install
will make a stable, reproducible build with all unit tests executed.
To run the integration tests you have to supply an additional flag: mvn clean install -PrunIT
.
We use Blockly, it is located in a separate repository. The build of the blockly is only done in the OpenRoberta/Blockly project and then copied to the OpenRobertaServer/staticResources. You can not build Blockly in OpenRobertaServer project directly.
We use BrowserStack for Cross-Browser Testing
Build status: