Self-Managed App Search, Configuration
The core configuration options can be found in
You can adjust host addresses, ports, Elasticsearch credentials, the logging level, and more.
config/env.sh file presents environment variables which can be altered as you see fit.
Configure a mailer within App Search to send user invitations and password resets.
Mailer, Local Mail Service Example
email.account: enabled: true smtp: auth: plain # Can be plain, login, or CRAM-MD5. starttls.enable: false # Whether emails are sent encapsulated in TLS, or not. host: 127.0.0.1 port: 25 user: firstname.lastname@example.org password: secure-pass-phrase email_defaults: from: email@example.com # The 'from' address is the address from which emails are sent. url_host: localhost:3002 # The url_host parameter is the domain used within generated emails, like password resets and invitations. Defaults to localhost.
Mailer, Gmail Example
email.account: enabled: true smtp: auth: plain starttls.enable: true host: smtp.gmail.com port: 587 user: firstname.lastname@example.org password: secure-pass-phrase email_defaults: from: email@example.com url_host: example.com
Mailer, Outlook Example
email.account: enabled: true smtp: auth: login starttls.enable: true host: smtp-mail.outlook.com port: 587 user: firstname.lastname@example.org password: secure-pass-phrase email_defaults: from: email@example.com url_host: example.com
Running Components Separately
The following run modes are not supported during the beta. But you might experiment...
If scale requires it, you can run App Search components separately.
There are two components that comprise an App Search deployment:
- An Application/API server that provides the web UI and API.
- A background worker that processes asynchronous requests like indexing, queries, and so on.
List all components:
Run a single component:
If you want to run the application server component - along with a Filebeat instance for collecting its logs:
Or, a background worker pool component could be started by running the following command:
An advanced mode is available for users that need to control and separately deploy specific processes:
bin/app-search --process PROCESS_NAME
WARNING: This mode is for operators with a deep understanding of internals and deployment procedures.
Thanks for trying out Self-Managed App Search. Please send us your beta feedback!