boravyvorant/eve-fuelbot

Notify Slack when structures need fuel

eve-fuelbot's Issues

Dates as local time

Slack has a mechanism for displaying time in the local timezone of each reader, described here:

https://api.slack.com/docs/message-formatting

It's not clear whether the exact expiry time for a structure is more useful in this form or not, but we should give some thought to changing this.

Don't restrict by system if unconfigured

At present, the systems configuration item must appear. We should change the application so that if it doesn't appear, the restriction by system is not performed.

Pass along deprecation warnings from ESI calls

ESI includes a system to allow applications to detect that they are using deprecated versioned routes. For a command-line application, it doesn't really make sense to do this in normal application use, but it could be added as something that could be called with a separate cron entry.

Unpowered structure causes fuelbot to crash

If you have a structure which is in low power state because no services are active, the fuel_expires value is nil rather than a DateTime and the following code fails:

# Sort by fuel expiry time.
structures.sort_by!(&:fuel_expires)

Error is:

fuelbot.rb:74:in `sort_by': comparison of DateTime with nil failed (ArgumentError)

Production configurations

To help deploying instances of this application we probably need:

• A Dockerfile to encapsulate the application
• A way to select different configuration files for different circumstances

State thresholds should be configurable

At present, the thresholds (in days) for danger and warning states are hard-wired. They should be taken from the configuration (but defaulted).

Allow symbols or strings as configuration keys

Production configurations

To help deploying instances of this application we probably need:

• A Dockerfile to encapsulate the application
• A way to select different configuration files for different circumstances