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
In the spirit of Chocolatey, an apt-get style tool for package management and installation, I beg you to automatically set the startup type to automatic and then automatically start the service as well. The audience using Chocolatey doesn't need that choice. We want our software auto-installed and running without any hand edits or after-install configuration whenever possible.
The text was updated successfully, but these errors were encountered:
@angryhussord Sorry it has taken so long to get back to you.
If you look at the documentation for the rpm package and deb package of Kibana from elastic search they both do not start automatically after Kibana has been installed but leave that as a additional step for someone to perform if they want it automatically started.
My general experience with Arch linux and others has been that many server style applications default to creating the service but starting it or not setting it to start automatically.
Given that Elastic.co isn't currently starting the service via their other distribution means and it doesn't feel like it is a hard and fast rule or expectation that installed servers should automatically start I think it is better to have the kibana package configure a service but leave it set to manual and not automatic.
In the spirit of Chocolatey, an apt-get style tool for package management and installation, I beg you to automatically set the startup type to automatic and then automatically start the service as well. The audience using Chocolatey doesn't need that choice. We want our software auto-installed and running without any hand edits or after-install configuration whenever possible.
The text was updated successfully, but these errors were encountered: