Strip Heroku-style usernames from config url

[acorncom]

Fixes #36

[acorncom]

@lukemelia Thoughts here?

[ghedamat]

nitpick, can you remove this?

[ghedamat]

@acorncom thanks for this, LGTM aside from the tiny comment

just catching up on the issue here,

basically we always need to specify username separately for that to work then?

/cc @achambers @lukemelia

[lukemelia]

LGTM @acorncom. I'm a little worried that some setups may use the username somehow, but I guess we can introduce a config flag later if that turns out to be the case. Merge when you're happy @ghedamat

[acorncom]

@ghedamat Re: always needing to specify the username, from what I've been seeing it looks like the underlying then-redis library swaps the Redis DB into the username spot (more details here: #51 (comment)). Seems like it's not properly following the Redis URL spec.

At this point, I'm not sure if we want to merge this PR or work on fixing the upstream library (assuming they're willing to do it). But I'm not a huge fan of using non-spec compliant URLs ;-)

Thoughts?

[acorncom]

@ghedamat Spacing issue fixed too ;-)

[joshsmith]

I've been lurking on this issue for awhile, and I would vote for attempting to fix the upstream library.

EDIT: Of course, this is easy for me to say when I'm inventing work for other people.

[ghedamat]

thanks @acorncom and sorry for the delay!

[ghedamat]

@lukemelia maybe this is worth a minor version bump and a mention in the changelog?

[lukemelia]

@ghedamat agreed.