Packages

•  package root

  Akka based micro service proving general leaderboard functionality for applications such as back-end game servers.

  Leaderboard Micro Service

  Akka based micro service proving general leaderboard functionality for applications such as back-end game servers.

  Overview

  Definition Classes

  root

•  package net

  Definition Classes

  root

•  package kolotyluk

  Definition Classes

  net

•  package scala

  Definition Classes

  kolotyluk

•  package extras

  Extra utilities for Scala developers.

  Extra Utilities

  Extra utilities for Scala developers.

  Some things it might have been nice to see in the standard Scala libraries, but are offered here instead. For example:

  object Main
    extends App
      with Configuration
      with Environment
      with Logging {
  
    // Safest way to indicate something is happening, don't rely on logging yet
    println(s"Starting ${getClass.getName}...")
  
    println("Reporting environment and configuration for troubleshooting purposes")
    println(environment.getEnvironmentReport())
    println(config.getConfigurationReport())
  
    // If logging is broken, hopefully there is enough output now for a diagnosis
    logger.info("Logging started")
  }

  Base 64 URL Identifiers

  Sometimes it's nice to encode a 128-bit UUID as a 22-character Base 64 URL String, such as "keAoZQECSwm0h7v6yw_3WQ". Normally a UUID is expressed as a 36-character string such as "91e02865-0102-4b09-b487-bbfacb0ff759", so this is a simple way of saving 14 characters in URL encoding. For example

  curl http://localhost/foo/keAoZQECSwm0h7v6yw_3WQ

  Would internally refer to a resource for "foo/91e02865-0102-4b09-b487-bbfacb0ff759"

  Definition Classes

  scala

•  trait Configuration extends Logging

  Extra features for Typesafe Config

  Enhanced Typesafe Config

  Extra features for Typesafe Config

  It is recommended that you extend this trait in your app, in the same style, but for local configuration. For example:

  trait Configuration extends net.kolotyluk.scala.extras.Configuration {
  
    config.setPathBase("net.flybynight.myapp")
  
    implicit class LocalConfiguration(val config: com.typesafe.config.Config) extends Logging  {
      import com.typesafe.config.Config
  
      // net.flybynight.myapp.akka.system.name
      def getAkkaSystemName(default: Some[String] = Some("myapp")): String  = config.getDefaultString("akka.system.name", default)
      def getRestAddress(default: Some[String] = Some("0.0.0.0")) : String = config.getDefaultString("rest.address", default)
      def getRestPort(default: Some[Int] = Some(8080)) : Int = config.getDefaultInt("rest.port", default, 0 to 65535)
    }
  }

  Good Separation of Concerns practice would be to make your configuration code as robust as possible. You main application should not handle any configuration problems, rather all configuration troubleshooting should be in your Configuration trait. In the main body of code you might use:

  val akkaSystemName = config.getAkkaSystemName()
  val restAddress = config.getRestAddress()
  val restPort = config.getRestPort()

  Definition Classes

  extras

• ConfigurationError
• ExtraConfiguration
• PathBase

net.kolotyluk.scala.extras.Configuration

ExtraConfiguration 