You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of an enhancement to help ease those who use Distillery, the problem is that the mappings in priv/elasticsearch won't match the right priv path when released into production, as something like:
would not search in the currently running release directory.
I implemented a naive solution in andrewvy@b2bed7d which uses Application.app_dir/2 to get the running application's priv folder, but this loses the ability for those who may be pointing to paths outside of their application. Let me know if this is something worth adding! (Separate option, fallback lookup?)
The text was updated successfully, but these errors were encountered:
Ah, the information is only correct at runtime. But I totally skipped over and realized I can just use Elasticsearch.Cluster.init/1 to provide runtime config anyways, making this a non-issue. :)
This is more of an enhancement to help ease those who use Distillery, the problem is that the mappings in
priv/elasticsearch
won't match the right priv path when released into production, as something like:would not search in the currently running release directory.
I implemented a naive solution in andrewvy@b2bed7d which uses
Application.app_dir/2
to get the running application's priv folder, but this loses the ability for those who may be pointing to paths outside of their application. Let me know if this is something worth adding! (Separate option, fallback lookup?)The text was updated successfully, but these errors were encountered: