BowerStudios.com

• Redis Datatypes
• Redis Cheatsheet by LeCoupa

  Command	Description
  redis-cli	redis client executable
  info	display info about redis
  info keyspaces	show databases equiv
  select [num]	Use database equiv
  keys [pattern / *]	List keys in db
  set [key value]
  get [key]
  mget [keys...]
  incr [key]
  incrBy [key incrementVal]
  decr [key]
  decrby [key decrementVal]
  del [key]
  ttl [key]
  expire [key seconds]

Always cool to see people who create libraries answer questions in stackoverflow.

Here's the author of Joda time answering a good question about why duration.get calls are generally incorrect.

You can't add Bouncy Castle libs to the fatjar that Dropwizard creates due to signing issues. So you'll need to exclude them from the fatjar process, and then add them to the runtime script.

You'll need to modify your shade config in your pom:

Then drop the bouncy castle libs beside your fatjar and modify the start script:

exec java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 -cp bcmail-jdk16-1.43.jar:bcprov-jdk16-1.43.jar -jar myFatJar.jar server config.yml

Link is a little older, but looks interesting: From enterprisedb.com

Npm will ignore by default files that are matched in your .gitignore
from stackoverflow

Deploy sources and javadoc to a maven repository

Likely due to the underlying javadoc tool on jdk8: See this question on
stackoverflow

StackOverflow

Stack Overflow answer by: Bozho

Today I miss Groovy....

This can happen when you're using the wrong form of authentication.

When using Realm Auth, npm login seemed to give me a success, but I couldn't publish with it.

npm whoami seemed to look at the wrong url.

From this doc in the Nexus Guide

I had to use the Basic Auth Option which involved:
Creating a hash to use in ~/.npmrc
echo -n 'admin:admin123' | openssl base64

as
registry=https://nexus.mydomain.com/content/groups/npm_repo
email=daniel@bowerstudios.com
always-auth=true
_auth=OUTPUT_FROM_THE_OPENSSL_HASH_ABOVE==