[{"_1":2,"_154":-5,"_155":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":11,"_130":-5,"_131":132},"canonicalUrl","https://hub.docker.com/r/dflemstr/qwait/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","dflemstr","reponame","qwait","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2014-09-11T17:47:07.829508Z","description","","is_private","last_updated","2015-11-14T13:52:02.875337Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.distribution.manifest.v1+prettyjws","name","pull_count",1554,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# QWait\n\n[![Build Status](https://travis-ci.org/mvk13ogb/qwait.png?branch=master)](https://travis-ci.org/mvk13ogb/qwait)\n\nThis is QWait, the next generation queuing system for KTH CSC.\n\n# Trying out the application\n\n## Docker\n\nThe application is available in the public Docker registry. Simply\nrun:\n\n docker run -p 8080:8080 dflemstr/qwait\n\nThis is all you have to do, provided that you have Docker installed.\n\n## Manually\n\nIf you want to try out QWait, simply do this:\n\n - Install Java JDK version 7 or later.\n - Install Apache Maven version 3 or later.\n - Enter the `qwait` directory and type `mvn jetty:run` to test the\n application. You can reach it at `http://localhost:8080/`.\n\nNote that unless you have configured LDAP correctly, logged-in users\nwill have names that are not very readable, because the real names of\nusers are fetched via LDAP queries.\n\nIt is also tricky to do anything with this test version of the\napplication, because you will not be an administrator, and only\nadministrators can add queues. It is recommended that you configure a\ndatabase such as PostgreSQL as outlined below, so that you can\nconfigure the initial administrator via the database.\n\n# Deployment\n\nQWait can be deployed in various ways; either continuously via a CI/CD\nsystem, or manually.\n\n## Continuous deployment\n\nThis repository is being continuously deployed. This allows for rapid\ndevelopment since no manual intervention is required while deploying.\n\nThe configuration for this system is in the `.travis.yml` file in the\nrepository.\n\nThe automatic deployment process works like this:\n\n - A commit is made on the `master` branch of this repository.\n - Travis CI picks up the new commit and starts building it. One\n such build looked like\n [this](https://travis-ci.org/mvk13ogb/qwait/builds/25261291).\n Travis runs the following commands in order:\n\n # Fetch the source code\n git clone --depth=50 --branch=master git://github.com/mvk13ogb/qwait.git mvk13ogb/qwait\n cd mvk13ogb/qwait\n\n # Go to the particular commit we want to build (to avoid a race condition\n # where someone might have committed something else in the mean time)\n git checkout -qf \n\n # Download dependencies & build everything\n mvn install -DskipTests=true -B -V\n\n # Run unit tests and integration tests\n mvn verify\n\n - If and only if the exit code of `mvn verify` is `0` will the next\n step be performed. Then, Travis will run the following script:\n\n if [[ \"$TRAVIS_PULL_REQUEST\" == false ]] && [[ \"$TRAVIS_BRANCH\" == master ]]\n then\n mvn -B package cargo:redeploy -DskipTests=true\n fi\n\n The additional check is there to ensure that the `mvn` command\n only runs if it is the master branch that is being built. The\n build configuration is used to build pull requests as well, and\n pull requests should not be deployed.\n\n As can be guessed from the command, it will package it as a .war\n file and deploy the web application using the Codehaus Cargo\n system. The configuration for Cargo is stored in the `pom.xml`\n file in the root of the repository. It might look something like\n this:\n\n \n org.codehaus.cargo\n cargo-maven2-plugin\n 1.4.7\n \n \n jetty9x\n remote\n \n\n \n runtime\n \n qwait.csc.kth.se\n 8080\n admin\n ${env.CARGO_PASSWORD}\n \n \n\n \n remote\n \n\n \n \n ${project.groupId}\n ${project.artifactId}\n war\n \n /\n \n \n \n \n \n\n The configuration says that:\n\n 1. The application should be deployed to a remote Jetty 9.x\n container.\n 2. The container is located at `http://qwait.csc.kth.se`\n listening on port `8080`.\n 3. To authenticate with Cargo, the username `admin` is used. The\n password is stored in the `CARGO_PASSWORD` environment\n variable. Travis knows about this password because of the\n `env[0].secure` line in the `.travis.yml` file in the\n repository, which contains encrypted instructions telling\n Travis to export the `CARGO_PASSWORD` environment variable\n with the right contents.\n 4. The deployer is also running remotely.\n 5. The artifacts to be deployed include our current project in\n the POM, which should be deployed to the `/` (root) context on\n the server.\n\n - On the remote server, Jetty 9.x is installed, with a webapp called\n the `cargo-jetty-7-and-onwards-deployer`. It authenticates the\n deployment attempt and receives the `.war` file. The file is\n renamed to `ROOT.war` (to put it in the `/` context which has the\n special name `ROOT`) and saved in the `webapps` folder of the Jetty\n container, where Jetty picks it up and starts serving it.\n\n## Manual deployment\n\nThe webapp can be manually deployed like so:\n\n - Run `mvn clean verify package` in the source repository.\n - Copy the resulting `.war` file from the `target/` directory onto\n the server machine into the `webapps/` directory of Jetty, for\n example into `/opt/jetty/webapps/`. The name of the file will\n decide the context path, so naming the file `foo.war` will deploy\n it to `http://server.se/foo/`. The special name `ROOT.war` will\n deploy the webapp to `http://server.se/`.\n\n## Caveats\n\nDeploying new versions of a web application without restarting Jetty\nfor a long time might yield Permanent Generation memory issues in\nJetty's JVM. The reason for this is that the web application's\nclasses are reloaded each time the application is deployed, and\nsometimes old classes are not successfully evicted from memory. It is\ntherefore recommended to restart Jetty after each deploy, but this is\nnot necessary most of the time.\n\n## Setting it up\n\n### The easy way\n\nSimply checking out the repository and running `mvn jetty:run` is\nenough to get a fully functional web application up and running,\nlistening to port `8080`. See point 4 below on how to forward port\n`8080`.\n\n### The hard way\n\nTo set up deployment, a few configuration steps are necessary:\n\n 1. Download and install a Java 7 JRE. On Ubuntu, this is simply done\n with:\n\n sudo aptitude install openjdk-7-jre\n\n Then, switch to that Java installation by default with:\n\n sudo update-java-alternatives -s java-1.7.0-openjdk-amd64\n\n To confirm that everything worked, try this and confirm that the\n version is `1.7.0`:\n\n $ java -version\n java version \"1.7.0_55\"\n OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1~0.12.04.2)\n OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)\n\n 2. Download and install a recent version of Jetty or some other\n Servlet container. The webapp has so far been tested with Jetty,\n so your mileage might vary. The container must support the Servlet\n v3.0 specification and the Java Websockets API. For the master\n version at `qwait.csc.kth.se`, Jetty version 9.1.1.v20140108 from\n the 8th of January 2014 was used. Versions of Jetty can be\n downloaded from [here](http://download.eclipse.org/jetty/).\n\n Actually installing Jetty is dependent on your particular\n distribution and the version of Jetty chosen. One way to do it for\n Ubuntu is outlined in\n [this blog post](http://pietervogelaar.nl/ubuntu-12-04-install-jetty-9/).\n\n 3. If you want to use continuous deployment (so that the application\n can simply be deployed with `mvn package cargo:redeploy` from the\n source repository on any machine), download\n `cargo-jetty-7-and-onwards-deployer` from\n [here](http://cargo.codehaus.org/Downloads) under the \"Tools\"\n section, and put it in your Jetty webapps folder\n (e.g. `/opt/jetty/webapps/`). Configure the webapp according to\n [the official instructions](http://cargo.codehaus.org/Jetty+Remote+Deployer).\n\n 4. Jetty listens to port `8080` by default. If the server should\n serve pages on port `80`, it is recommended to either use a\n front-end proxy server such as Apache HTTPD or Nginx, or to\n introduce an `iptables` rule in Linux to forward port `80` to\n `8080`, like so:\n\n /sbin/iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080\n\n Configuring this rule to be applied on each boot is\n distro-specific.\n\n# Configuration\n\nThe default QWait configuration \"works\" but is not optimal. You\nshould change the settings of the application to suit your needs.\n\nThe web application is configured using the Spring settings API. This\nAPI allows settings to be overridden via different sources.\n\n## Before deployment\n\nThe easiest way to change a setting is to modify the file\n`src/main/resources/settings.properties`. This is a simple\n`key=value` settings file, with the additional property that Maven\nvariables can be interpolated with `${...}` syntax. A typical\nconfiguration file for a production environment, along with comments\nexplaining each setting, would be:\n\n # The name of the application to display in various places. Defaults to\n # Whatever this is from the pom.xml file.\n product.name=${project.name}\n\n # The version of the application to display in various places. Defaults to\n # Whatever this is from the pom.xml\n # file.\n product.version=${project.version}\n\n # The driver to use when connecting to a database. Here,\n # PostgreSQL has been configured. Note that a large number of\n # databases are supported, but you need to make sure that the\n # relevant JDBC driver has been added to the in\n # pom.xml (For PostgreSQL, it is org.postgresql:postgresql)\n dataSource.driverClassName=org.postgresql.Driver\n\n # The URL to connect to, which is database specific. In this\n # case, we connect to PostgreSQL on localhost, with the database\n # name qwait.\n dataSource.url=jdbc:postgresql://localhost/qwait\n\n # The user and password to use when connecting to the database.\n dataSource.username=qwait\n dataSource.password=\n\n # Which SQL dialect to use when communicating with the database.\n # Supported dialects are listed here: http://docs.jboss.org/hibernate/orm/4.0/javadocs/org/hibernate/dialect/package-summary.html\n hibernate.dialect=org.hibernate.dialect.PostgreSQL9Dialect\n\n # How to generate the schema for the database. Supported values are:\n # - validate: Don't do anything, just verify that the tables are\n # compatible with the webapp and error out otherwise.\n # - update: Create new tables and columns if they are missing.\n # - create: Overwrites existing tables with empty tables.\n # - create-drop: Like create, but also drops all tables at application\n # shutdown.\n hibernate.hbm2ddl.auto=update\n\n # The CAS call-back service URI to use when doing CAS authentication\n security.cas.service=http://qwait.csc.kth.se:8080/authenticate\n # The CAS login URL to use\n security.cas.loginUrl=https://login.kth.se/login\n # The CAS logout URL to use\n security.cas.logoutUrl=https://login.kth.se/logout\n # The actual CAS ticket validator service\n security.cas.ticketValidator=https://login.kth.se\n # Our auth provider key for this webapp\n security.cas.authProviderKey=\n\n # The LDAP service to use when doing LDAP lookups\n security.ldap.url=ldaps://ldap0.csc.kth.se\n # The LDAP base query to constrain results\n security.ldap.base=ou=unix,dc=csc,dc=kth,dc=se\n # LDAP auth user if needed\n security.ldap.userDn=\n # LDAP auth password if needed\n security.ldap.password=\n # Enforce read-only operations via anonymous log-in\n security.ldap.anonymousReadOnly=true\n\n # Application configuration profiles to activate. If the \"ldap\"\n # profile is activated, the application will try to use LDAP to\n # look up user names.\n spring.profiles.active=default,ldap\n\n## After deployment\n\nWhen the application has been packaged as a `.war`, it is tedious to\nmodify the settings inside of it (but possible: simply open the file\nas a ZIP archive).\n\nInstead, settings can be overridden using container-specific\nmechanisms. For example, one way is to set Servlet context\nparameters. In Jetty, this is done globally by changing\n`/opt/jetty/etc/webdefault.xml`. A configuration setting might look\nlike:\n\n \n hibernate.dialect\n org.hibernate.dialect.PostgreSQL9Dialect\n \n\nIt is also possible to do per-application overrides in Jetty using the\n`override-web.xml` file as outlined\n[here](https://wiki.eclipse.org/Jetty/Reference/override-web.xml).\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",551044336,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",71968,"digest","sha256:d92f50e0558801129dc0f7742bd97a937ce20aa9196b6d065bd9d054ce3a9f9b","full_size",550993378,"id",39019,"images",[99],{"_100":101,"_91":92,"_102":44,"_103":104,"_105":106,"_107":44,"_108":44,"_109":-5,"_110":111,"_59":62,"_112":-5},"architecture","amd64","features","last_pulled","2026-09-21T16:12:26.049273378Z","last_pushed","2015-11-14T13:52:02Z","os","os_features","os_version","size",550993730,"variant","2015-11-14T13:52:07.282868Z","last_updater","last_updater_username","media_type","latest","repository",53852,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":135,"_142":143,"_131":152,"_153":11},{"_36":136,"_38":137,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":138,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":139,"_75":17,"_76":141,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":140},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_144":60,"_145":-5,"_146":-5,"_147":148},"count","next","previous","results",[149],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_97":150,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[151],{"_100":101,"_91":92,"_102":44,"_103":104,"_105":106,"_107":44,"_108":44,"_109":-5,"_110":111,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

dflemstr/qwait

Tags for dflemstr/qwait