Previously the seed logic ran when `SEED_EMAIL` was unset and the `admin`
users email address was changed, or if `SEED_EMAIL` did not match it
anymore.
We run `db:seed` on every docker container start to make it easy to get
started with Huginn. That could lead to situations in which the
container did not start if the admin users email address was changed (the
Seeder failed due to the uniqueness constraint on `username`).
Since we "seed" the database I think it is best to bail out of the
seeding logic as long as at least one user exists.
Fixes#2362
It now additionally allows to use `sticky`, `priority` and
`callback_url`. The Agent is now `FormConfigurable` and supports Liquid
in all options.
`register_growl` had to be moved inside of the `events` loop to allow
Liquid interpolation for the previously static `growl_*` options.
#2018
For backward compatibility, a new option `rss_content_type` is added
and existing agents will have its value set to `text/xml`, which was
the Content-Type value before this change.
This fixes#1968.
Closes -- https://github.com/cantino/huginn/issues/801
Testing -- ran rspec
About --
Adds an option `min_events` to the peak detector agent. The
agent will start looking for peaks only after min number of
events are accumulated.
Add new `emit_error_events` option which is set to `false` for all new `TwitterActionAgent`s. This will ensure the Agent
is retried when the action failed by raising an exception.
For all existing `TwitterUserAgent`s the option is set to `true` to keep the previous behavior.
* EmailDigestAgent relies on received events, rather than storing them in memory
- Addressing a problem where 40,000+ events were stored in one agent's memory, and the agent never loaded from the database
* Cleans up references to memory["queue"]
- incorporates suggested style and safeguards
* Adds clarification on event inclusion in email
* Use `reorder` rather than stripping away all scoping
Variables that are usable but not present with default values in .env.example were located with this one-liner:
```
diff --changed-group-format='%<' --unchanged-group-format='' <(ack "ENV\[.(.+?).\]" --output='$1' -h app config lib db| sort | uniq) <(grep = .env.example | sed -e 's/^#\([^ ]\)/\1/' | grep -v -e '^#'| ack "(.+?)=" --output='$1'|sort)
```
* checking in work for glyph upload
* checking in icon selections
* added more icon options
* work on upload icon
* fix issue
* switched to options for select
* removed wrapper and removed commment
* add migration to support icon
* remove right floating
* rm params session add it to model
* rebuilt the menu
* rm extra div
* converted js to coffee
* quick change in indentation
* using the view helper
* submitting icons and loading into form
* added icon to both scenario export and import
* added icon to spec
* low level caching the icons
* tentative work in making a new coffee class
* renamed js page
* switched to cache in memory and worked on coffee class
* made pathsmatching compatible for all scenarios
* switched to rails root
* fixed all rubocop stylings
* fixed line is too long styling
* rm private method definition
* patch to avoid having no icon
* blank or nil?
* reordering the lines
It is defaulted to `capitalized`, normalizing emitted headers by
capitalizing the names so downstream agents don't need to bother with
the letter cases.
Previously, the style of header names in an emitted event would vary
depending on the server and the backend HTTP library. Most notably, the
`net_http` backend downcases header names whereas other backends do not.
For backward compatibility, preexisting PostAgents are automatically
configured to have `event_headers_style` set to `raw` via migration.
- gives them a place to start from
- leverages existing code to import scenarios
- adds test coverage to seeds to ensure sees can run multiple times against the same db as is the case for Docker
- adds env variable to set if importing is turned on for new user
- adds env variable to point to a custom scenario for new users
- Huginn supports MySQL and Postgres which generates conflicts in the schema
- Remvoing it shows that schema.rb is not a source of truth
ClosesTildeWill/huginn#13
Related Issue cantino/huginn#1195
- Introduces new ENV variable SKIP_INVITATION_CODE, intentionally
phrased in the negative so that the absence of the variable
will not change the behavior of existing deployments.
