Skip to content
Snippets Groups Projects
Select Git revision
  • q-based-learning-progress
  • customization/univie-dev
  • 2.x protected
  • sst-cleanup
  • 2.7 protected
  • master default protected
  • content-group-updating
  • ldap-and-sso-auth-endpoints
  • api-proxy-path-handling
  • account-activation-reset
  • pac4j-saml-npe
  • fix-motd-npe
  • pac4j-saml
  • dev-docs
  • spring-message-to-stomp-adapter
  • publish-room-access
  • pwd-reset-mail-with-key
  • ci-docker
  • lms-caching
  • 2.6
  • v2.7.4 protected
  • v2.7.3 protected
  • v2.7.2 protected
  • v2.7.1 protected
  • v2.6.4 protected
  • v2.5.10 protected
  • v2.7.0 protected
  • v2.6.3 protected
  • v2.5.9 protected
  • v2.6.2 protected
  • v2.5.8 protected
  • v2.6.1 protected
  • v2.6.0 protected
  • v2.5.7 protected
  • v2.5.6 protected
  • v2.5.5 protected
  • v2.5.4 protected
  • v2.5.3 protected
  • v2.5.2 protected
  • v2.5.1 protected
40 results
Blame History Permalink
README.md 9.59 KiB

ARSnova

ARSnova is a modern approach to Audience Response Systems (ARS). It is released under the GPLv3 license, and is offered as a Software as a Service free of charge. Head over to arsnova.eu to see it in action.

ARSnova

ARSnova consists of two projects: the mobile frontend and the backend. This repository contains the backend code. You will find the frontend at thm-projects/arsnova-mobile. However, you do not need to download both repositories in order to get started.

Build Status

Getting Started

The most convenient way to get started developing ARSnova is by using our Vagrant environment, found at thm-projects/arsnova-vagrant. Use your IDE on your host machine to make changes to ARSnova, while the build process is completely handled by the Vagrant box. You will not need to install any development tools.

arsnova-vagrant sets up a virtual machine for both development and production use. The basic usage is vagrant up, which will start the development environment. If you wish to start production as well, use vagrant up production.

Once any machine has been started, all required ARSnova repositories are automatically cloned from GitHub, so that you can start coding immediately.

To connect to your development machine, type vagrant ssh. After that, you can start ARSnova inside the machine by running ./start.sh. You can then access ARSnova from your host machine by opening http://localhost:8080.

QA Private Build

arsnova-vagrant also sets up the build environment we use internally at THM, which consists of Jenkins and SonarQube. The former provides a QA pipeline that builds, tests, analyzes, and finally deploys ARSnova to the production environment. SonarQube is used for the analyzation phase and provides a drill-down into many quality aspects, including technical debt.

While the development environment is running, Jenkins and SonarQube are available at:

QA Public Build

We also leverage the cloud provided by Travis CI and Sauce Labs to build and test ARSnova. Travis first builds and unit tests the software, then it instructs Sauce Labs to run smoke tests on different browsers and operating systems. This ensures that the basic features of ARSnova work across browsers and platforms. See this example to get an idea.

Our official build status provided by Travis CI:

  • Build Status for ARSnova Backend
  • Build Status for ARSnova Mobile

Development

This is ARSnova's main repository. Almost all dependencies are managed for you by Maven.