Installation difficult due to hard-coded paths and credentials being spread across files

[bcipolli]

Currently, setting up a system is hard as:

• The versions for Apache storm & other dependencies are assumed
• The paths to the installations are hard-coded into various scripts
• Twitter credentials are hard-coded elsewhere.
• Little of this is documented.

I suggest two options:

• It would be great to have a single place where these editable settings exist (e.g. a bash script for setting environment variables, that is sourced in other scripts)
• Either way, the process of editing script(s) should be documented.

@davisliang are you cool with this change? If so, I'd be happy to implement.

[davisliang]

Sounds good!

On Sunday, February 19, 2017 5:29 AM, Ben Cipollini <notifications@github.com> wrote:

Currently, setting up a system is hard as:

• The versions for Apache storm & other dependencies are assumed
• The paths to the installations are hard-coded into various scripts
• Twitter credentials are hard-coded elsewhere.
• Little of this is documented. I suggest two options:
• It would be great to have a single place where these editable settings exist (e.g. a bash script for setting environment variables, that is sourced in other scripts)
• Either way, the process of editing script(s) should be documented. @davisliang are you cool with this change? If so, I'd be happy to implement.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.