Skip to content
Snippets Groups Projects
  1. Apr 01, 2020
  2. Mar 27, 2020
  3. Aug 02, 2019
  4. Apr 09, 2020
  5. Mar 26, 2020
  6. Apr 09, 2020
  7. Apr 08, 2020
  8. Apr 07, 2020
  9. Apr 06, 2020
  10. Apr 07, 2020
  11. Apr 03, 2020
    • P's avatar
      Update smtp.md · 8943cdc5
      P authored
      Added Open Telekom Cloud example config
      8943cdc5
  12. Apr 07, 2020
  13. Apr 05, 2020
  14. Apr 06, 2020
  15. Apr 01, 2020
  16. Apr 06, 2020
  17. Apr 03, 2020
  18. Mar 31, 2020
    • Bob Van Landuyt's avatar
      Conditionally start sidekiq-cluster named Sidekiq · 0d66d5be
      Bob Van Landuyt authored
      When configuring Sidekiq to run in cluster mode, using
      `sidekiq['cluster'] = true`, we would previously start up a service
      called `sidekiq-cluster`. This might be confusing to administrator, as
      the service they configured is `sidekiq` rather than
      `sidekiq-cluster`.
      
      This changes that behaviour, if sidekiq-cluster was started using the
      new configuration:
      
        sidekiq['enable'] = true
        sidekiq['cluster'] = true
      
      Then the service that will run sidekiq-cluster will be called
      `sidekiq` rather than `sidekiq-cluster`
      
      Configuring sidekiq-cluster using the soon-to-be deprecated
      configuration
      
        sidekiq_cluster['enable'] = true
      
      would still result in a service called `sidekiq-cluster`.
      
      It is not possible to start sidekiq-cluster twice with conflicting
      configuration. So we know when `node['gitlab']['sidekiq']['cluster']`
      is set and `sidekiq_cluster` is enabled that this will be the only
      sidekiq-cluster process that will be started.
      0d66d5be
  19. Apr 03, 2020
  20. Mar 31, 2020
  21. Apr 03, 2020
  22. Mar 26, 2020
  23. Apr 02, 2020
  24. Apr 01, 2020
Loading