launchdarkly-server-sdk 5.5.7

data/.simplecov

@@ -0,0 +1,4 @@
+SimpleCov.start do
+  add_filter '/spec/'
+  add_filter '/.bundle/'
+end

data/.yardopts

@@ -0,0 +1,9 @@
+--no-private
+--markup markdown
+--embed-mixins
+lib/*.rb
+lib/**/*.rb
+lib/**/**/*.rb
+lib/**/**/**/*.rb
+-
+README.md

data/CHANGELOG.md

@@ -0,0 +1,261 @@
+# Change log
+
+All notable changes to the LaunchDarkly Ruby SDK will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
+
+## [5.5.7] - 2019-05-13
+### Changed:
+- Changed the gem name from `ldclient-rb` to `launchdarkly-server-sdk`.
+
+There are no other changes in this release. Substituting `ldclient-rb` version 5.5.6 with `launchdarkly-server-sdk` version 5.5.7 will not affect functionality.
+
+## [5.5.6] - 2019-05-08
+### Fixed:
+- CI tests now include Ruby 2.6.x.
+- Running the SDK unit tests is now simpler, as the database integrations can be skipped. See `CONTRIBUTING.md`.
+
+# Note on future releases
+
+The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now `ruby-server-sdk` rather than `ruby-client`.
+
+The gem name will also change. In the 5.5.6 release, it is still `ldclient-rb`; in all future releases, it will be `launchdarkly-server-sdk`. No further updates to the `ldclient-rb` gem will be published after this release.
+
+
+## [5.5.5] - 2019-03-28
+### Fixed:
+- Setting user attributes to non-string values when a string was expected would cause analytics events not to be processed. Also, in the case of the `secondary` attribute, this could cause evaluations to fail for a flag with a percentage rollout. The SDK will now convert attribute values to strings as needed. ([#131](https://github.com/launchdarkly/ruby-server-sdk/issues/131))
+
+## [5.5.4] - 2019-03-29
+### Fixed:
+- Fixed a missing `require` that could sometimes cause a `NameError` to be thrown when starting the client, depending on what other gems were installed. This bug was introduced in version 5.5.3. ([#129](https://github.com/launchdarkly/ruby-server-sdk/issues/129))
+- When an analytics event was generated for a feature flag because it is a prerequisite for another flag that was evaluated, the user data was being omitted from the event. ([#128](https://github.com/launchdarkly/ruby-server-sdk/issues/128))
+- If `track` or `identify` is called without a user, the SDK now logs a warning, and does not send an analytics event to LaunchDarkly (since it would not be processed without a user).
+- Added a link from the SDK readme to the guide regarding the client initialization.
+
+## [5.5.3] - 2019-02-13
+### Changed:
+- The SDK previously used the `faraday` and `net-http-persistent` gems for all HTTP requests other than streaming connections. Since `faraday` lacks a stable version and has a known issue with character encoding, and `net-http-persistent` is no longer maintained, these have both been removed. This should not affect any SDK functionality.
+
+### Fixed:
+- The SDK was not usable in Windows because of `net-http-persistent`. That gem has been removed.
+- When running in Windows, the event-processing thread threw a `RangeError` due to a difference in the Windows implementation of `concurrent-ruby`. This has been fixed.
+- Windows incompatibilities were undetected before because we were not running a Windows CI job. We are now testing on Windows with Ruby 2.5.
+
+## [5.5.2] - 2019-01-18
+### Fixed:
+- Like 5.5.1, this release contains only documentation fixes. Implementation classes that are not part of the supported API are now hidden from the [generated documentation](https://www.rubydoc.info/gems/ldclient-rb).
+
+
+## [5.5.1] - 2019-01-17
+### Fixed:
+- Fixed several documentation comments that had the wrong parameter names. There are no other changes in this release; it's only to correct the documentation.
+
+## [5.5.0] - 2019-01-17
+### Added:
+- It is now possible to use Consul or DynamoDB as a persistent feature store, similar to the existing Redis integration. See the `LaunchDarkly::Integrations::Consul` and `LaunchDarkly::Integrations::DynamoDB` modules, and the reference guide [Using a persistent feature store](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
+- There is now a `LaunchDarkly::Integrations::Redis` module, which is the preferred method for creating a Redis feature store.
+- All of the database feature stores now support local caching not only for individual feature flag queries, but also for `all_flags_state`.
+- The `Config` property `data_source` is the new name for `update_processor` and `update_processor_factory`.
+
+### Changed:
+- The implementation of the SSE protocol for streaming has been moved into a separate gem, [`ld-eventsource`](https://github.com/launchdarkly/ruby-eventsource). This has no effect on streaming functionality.
+
+### Fixed:
+- Added or corrected a large number of documentation comments. All API classes and methods are now documented, and internal implementation details have been hidden from the documentation. You can view the latest documentation on [RubyDoc](https://www.rubydoc.info/gems/ldclient-rb).
+- Fixed a problem in the Redis feature store that would only happen under unlikely circumstances: trying to evaluate a flag when the LaunchDarkly client had not yet been fully initialized and the store did not yet have data in it, and then trying again when the client was still not ready but the store _did_ have data (presumably put there by another process). Previously, the second attempt would fail.
+- In polling mode, the SDK did not correctly handle non-ASCII Unicode characters in feature flag data. ([#90](https://github.com/launchdarkly/ruby-server-sdk/issues/90))
+
+### Deprecated:
+- `RedisFeatureStore.new`. This implementation class may be changed or moved in the future; use `LaunchDarkly::Integrations::Redis::new_feature_store`.
+- `Config.update_processor` and `Config.update_processor_factory`; use `Config.data_source`.
+
+## [5.4.3] - 2019-01-11
+### Changed:
+- The SDK is now compatible with `net-http-persistent` 3.x. (Thanks, [CodingAnarchy](https://github.com/launchdarkly/ruby-server-sdk/pull/113)!)
+
+## [5.4.2] - 2019-01-04
+### Fixed:
+- Fixed overly specific dependency versions of `concurrent-ruby` and `semantic`. ([#115](https://github.com/launchdarkly/ruby-server-sdk/issues/115))
+- Removed obsolete dependencies on `hashdiff` and `thread_safe`.
+
+## [5.4.1] - 2018-11-05
+### Fixed:
+- Fixed a `LoadError` in `file_data_source.rb`, which was added in 5.4.0. (Thanks, [kbarrette](https://github.com/launchdarkly/ruby-server-sdk/pull/110)!)
+
+
+## [5.4.0] - 2018-11-02
+### Added:
+- It is now possible to inject feature flags into the client from local JSON or YAML files, replacing the normal LaunchDarkly connection. This would typically be for testing purposes. See `file_data_source.rb`.
+
+### Fixed:
+- When shutting down an `LDClient`, if in polling mode, the client was using `Thread.raise` to make the polling thread stop sleeping. `Thread.raise` can cause unpredictable behavior in a worker thread, so it is no longer used.
+
+## [5.3.0] - 2018-10-24
+### Added:
+- The `all_flags_state` method now accepts a new option, `details_only_for_tracked_flags`, which reduces the size of the JSON representation of the flag state by omitting some metadata. Specifically, it omits any data that is normally used for generating detailed evaluation events if a flag does not have event tracking or debugging turned on.
+
+### Fixed:
+- JSON data from `all_flags_state` is now slightly smaller even if you do not use the new option described above, because it omits the flag property for event tracking unless that property is true.
+
+## [5.2.0] - 2018-08-29
+### Added:
+- The new `LDClient` method `variation_detail` allows you to evaluate a feature flag (using the same parameters as you would for `variation`) and receive more information about how the value was calculated. This information is returned in an `EvaluationDetail` object, which contains both the result value and a "reason" object which will tell you, for instance, if the user was individually targeted for the flag or was matched by one of the flag's rules, or if the flag returned the default value due to an error.
+
+### Fixed:
+- Evaluating a prerequisite feature flag did not produce an analytics event if the prerequisite flag was off.
+
+ 
+## [5.1.0] - 2018-08-27
+### Added:
+- The new `LDClient` method `all_flags_state()` should be used instead of `all_flags()` if you are passing flag data to the front end for use with the JavaScript SDK. It preserves some flag metadata that the front end requires in order to send analytics events correctly. Versions 2.5.0 and above of the JavaScript SDK are able to use this metadata, but the output of `all_flags_state()` will still work with older versions.
+- The `all_flags_state()` method also allows you to select only client-side-enabled flags to pass to the front end, by using the option `client_side_only: true`.
+
+### Changed:
+- Unexpected exceptions are now logged at `ERROR` level, and exception stacktraces at `DEBUG` level. Previously, both were being logged at `WARN` level.
+
+### Deprecated:
+- `LDClient.all_flags()`
+
+
+## [5.0.1] - 2018-07-02
+### Fixed:
+Fixed a regression in version 5.0.0 that could prevent the client from reconnecting if the stream connection was dropped by the server.
+
+
+## [5.0.0] - 2018-06-26
+### Changed:
+- The client no longer uses Celluloid for streaming I/O. Instead, it uses [socketry](https://github.com/socketry/socketry).
+- The client now treats most HTTP 4xx errors as unrecoverable: that is, after receiving such an error, it will not make any more HTTP requests for the lifetime of the client instance, in effect taking the client offline. This is because such errors indicate either a configuration problem (invalid SDK key) or a bug, which is not likely to resolve without a restart or an upgrade. This does not apply if the error is 400, 408, 429, or any 5xx error.
+- During initialization, if the client receives any of the unrecoverable errors described above, the client constructor will return immediately; previously it would continue waiting until a timeout. The `initialized?` method will return false in this case.
+
+### Removed:
+- The SDK no longer supports Ruby versions below 2.2.6, or JRuby below 9.1.16.
+
+## [4.0.0] - 2018-05-10
+
+### Changed:
+- To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option `inline_users_in_events`. For more details, see [Analytics Data Stream Reference](https://docs.launchdarkly.com/v2.0/docs/analytics-data-stream-reference).
+
+### Removed:
+- JRuby 1.7 is no longer supported.
+- Greatly reduced the number of indirect gem dependencies by removing `moneta`, which was previously a requirement for the Redis feature store.
+
+
+## [3.0.3] - 2018-03-23
+## Fixed
+- In the Redis feature store, fixed a synchronization problem that could cause a feature flag update to be missed if several of them happened in rapid succession.
+
+## [3.0.2] - 2018-03-06
+## Fixed
+- Improved efficiency of logging by not constructing messages that won't be visible at the current log level. (Thanks, [julik](https://github.com/launchdarkly/ruby-server-sdk/pull/98)!)
+
+
+## [3.0.1] - 2018-02-26
+### Fixed
+- Fixed a bug that could prevent very large feature flags from being updated in streaming mode.
+
+
+## [3.0.0] - 2018-02-22
+### Added
+- Support for a new LaunchDarkly feature: reusable user segments.
+
+### Changed
+- The feature store interface has been changed to support user segment data as well as feature flags. Existing code that uses `InMemoryFeatureStore` or `RedisFeatureStore` should work as before, but custom feature store implementations will need to be updated.
+
+
+## [2.5.0] - 2018-02-12
+
+## Added
+- Adds support for a future LaunchDarkly feature, coming soon: semantic version user attributes.
+
+## Changed
+- It is now possible to compute rollouts based on an integer attribute of a user, not just a string attribute.
+
+## [2.4.1] - 2018-01-23
+## Changed
+- Reduce logging level for missing flags
+- Relax json and faraday dependencies
+## Fixed
+- Wrap redis bulk updates in a transaction
+- Fixed documentation links
+
+## [2.4.0] - 2018-01-12
+## Changed
+- Will use feature store if already initialized even if connection to service could not be established.  This is useful when flags have been initialized in redis.
+- Increase default and  minimum polling interval to 30s
+- Strip out unknown top-level attributes
+
+## [2.3.2] - 2017-12-02
+
+### Fixed
+- Make sure redis store initializations are atomic
+
+
+## [2.3.1] - 2017-11-16
+
+### Changed
+- Include source code for changes described in 2.3.0
+
+
+## [2.3.0] - 2017-11-16
+## Added
+- Add `close` method to Ruby client to stop processing events
+- Add support for Redis feature store
+- Add support for LDD mode
+- Allow user to disable outgoing event stream.
+
+## Changed
+- Stop retrying on 401 responses (due to bad sdk keys)
+
+## [2.2.7] - 2017-07-26
+## Changed
+- Update Readme to fix instructions on installing gem using command line
+- Cleaned up formatting on various files (Rubocop)
+## [2.2.5] - 2017-05-08
+## Changed
+- Added proxy support to streaming and http connections. Respects `HTTP_PROXY` and `http_proxy` environment variables as well as the `:proxy => protocol://user:pass@host` configuration parameter.
+
+## [2.1.5] - 2017-03-28
+## Changed
+- Updated changelog 
+
+## [2.1.1] - 2017-03-28
+## Changed
+- Bumped nio4r to 2.0
+
+## [2.0.6] - 2017-02-10
+## Changed
+- Improved handling of http status codes that may not be integers.
+
+## [2.0.5] - 2017-01-31
+## Changed
+- Improved error handling when connected to flag update stream.
+
+## [2.0.3] - 2016-10-21
+## Fixed
+- Indirect stream events are now correctly processed
+
+## [2.0.2] - 2016-08-08
+## Changed
+- The default logger now logs at `info` level
+
+## [2.0.0] - 2016-08-08
+### Added
+- Support for multivariate feature flags. In addition to booleans, feature flags can now return numbers, strings, dictionaries, or arrays via the `variation` method.
+- New `all_flags` method returns all flag values for a specified user.
+- If streaming is disabled, the client polls for feature flag changes. If streaming is disabled, the client will default to polling LaunchDarkly every second for updates. The poll interval is configurable via `poll_interval`.
+- New `secure_mode_hash` function computes a hash suitable for the new LaunchDarkly JavaScript client's secure mode feature.
+- Support for extremely large feature flags. When a large feature flag changes, the stream will include a directive to fetch the updated flag.
+
+### Changed
+- You can now initialize the LaunchDarkly client with an optional timeout (specified in seconds). This will block initialization until the client has finished bootstrapping and is able to serve feature flags.
+- The streaming implementation (`StreamProcessor`) uses [Celluloid](https://github.com/celluloid/celluloid) under the hood instead of [EventMachine](https://github.com/eventmachine/eventmachine). The dependency on EventMachine has been removed.
+- The `store` option has been renamed to `cache_store`.
+- Offline mode can no longer be set dynamically. Instead, at configuration time, the `offline` parameter can be set to put the client in offline mode. It is no longer possible to dynamically change whether the client is online and offline (via `set_online` and `set_offline`). Call `offline?` to determine whether or not the client is offline.
+- The `debug_stream` configuration option has been removed.
+- The `log_timings` configuration option has been removed.
+
+### Deprecated
+- The `toggle` call has been deprecated in favor of `variation`.
+
+### Removed
+- `update_user_flag_setting` has been removed. To change user settings, use the LaunchDarkly REST API.

data/CODEOWNERS

@@ -0,0 +1 @@
+

data/CONTRIBUTING.md

@@ -0,0 +1,37 @@
+Contributing to the LaunchDarkly Server-side SDK for Ruby
+================================================
+
+LaunchDarkly has published an [SDK contributor's guide](https://docs.launchdarkly.com/docs/sdk-contributors-guide) that provides a detailed explanation of how our SDKs work. See below for additional information on how to contribute to this SDK.
+
+Submitting bug reports and feature requests
+------------------
+
+The LaunchDarkly SDK team monitors the [issue tracker](https://github.com/launchdarkly/ruby-server-sdk/issues) in the SDK repository. Bug reports and feature requests specific to this SDK should be filed in this issue tracker. The SDK team will respond to all newly filed issues within two business days.
+
+Submitting pull requests
+------------------
+
+We encourage pull requests and other contributions from the community. Before submitting pull requests, ensure that all temporary or unintended code is removed. Don't worry about adding reviewers to the pull request; the LaunchDarkly SDK team will add themselves. The SDK team will acknowledge all pull requests within two business days.
+
+Build instructions
+------------------
+
+### Prerequisites
+
+This SDK is built with [Bundler](https://bundler.io/). To install Bundler, run `gem install bundler -v 1.17.3`. You might need `sudo` to execute the command successfully. As of this writing, the SDK does not support being built with Bundler 2.0.
+
+To install the runtime dependencies:
+
+```
+bundle install
+```
+
+### Testing
+
+To run all unit tests:
+
+```
+bundle exec rspec spec
+```
+
+By default, the full unit test suite includes live tests of the integrations for Consul, DynamoDB, and Redis. Those tests expect you to have instances of all of those databases running locally. To skip them, set the environment variable `LD_SKIP_DATABASE_TESTS=1` before running the tests.

data/Gemfile

@@ -0,0 +1,3 @@
+source "https://rubygems.org"
+
+gemspec

data/Gemfile.lock

@@ -0,0 +1,102 @@
+PATH
+  remote: .
+  specs:
+    launchdarkly-server-sdk (5.5.6)
+      concurrent-ruby (~> 1.0)
+      json (>= 1.8, < 3)
+      ld-eventsource (~> 1.0)
+      semantic (~> 1.6)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    aws-eventstream (1.0.1)
+    aws-partitions (1.128.0)
+    aws-sdk-core (3.44.2)
+      aws-eventstream (~> 1.0)
+      aws-partitions (~> 1.0)
+      aws-sigv4 (~> 1.0)
+      jmespath (~> 1.0)
+    aws-sdk-dynamodb (1.19.0)
+      aws-sdk-core (~> 3, >= 3.39.0)
+      aws-sigv4 (~> 1.0)
+    aws-sigv4 (1.0.3)
+    codeclimate-test-reporter (0.6.0)
+      simplecov (>= 0.7.1, < 1.0.0)
+    concurrent-ruby (1.1.5)
+    connection_pool (2.2.1)
+    diff-lcs (1.3)
+    diplomat (2.0.2)
+      faraday (~> 0.9)
+      json
+    docile (1.1.5)
+    faraday (0.15.4)
+      multipart-post (>= 1.2, < 3)
+    ffi (1.9.25)
+    ffi (1.9.25-java)
+    hitimes (1.3.1)
+    hitimes (1.3.1-java)
+    http_tools (0.4.5)
+    jmespath (1.4.0)
+    json (1.8.6)
+    json (1.8.6-java)
+    ld-eventsource (1.0.0)
+      concurrent-ruby (~> 1.0)
+      http_tools (~> 0.4.5)
+      socketry (~> 0.5.1)
+    listen (3.1.5)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+      ruby_dep (~> 1.2)
+    multipart-post (2.0.0)
+    rake (10.5.0)
+    rb-fsevent (0.10.3)
+    rb-inotify (0.9.10)
+      ffi (>= 0.5.0, < 2)
+    redis (3.3.5)
+    rspec (3.7.0)
+      rspec-core (~> 3.7.0)
+      rspec-expectations (~> 3.7.0)
+      rspec-mocks (~> 3.7.0)
+    rspec-core (3.7.1)
+      rspec-support (~> 3.7.0)
+    rspec-expectations (3.7.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.7.0)
+    rspec-mocks (3.7.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.7.0)
+    rspec-support (3.7.0)
+    rspec_junit_formatter (0.3.0)
+      rspec-core (>= 2, < 4, != 2.12.0)
+    ruby_dep (1.5.0)
+    semantic (1.6.1)
+    simplecov (0.15.1)
+      docile (~> 1.1.0)
+      json (>= 1.8, < 3)
+      simplecov-html (~> 0.10.0)
+    simplecov-html (0.10.2)
+    socketry (0.5.1)
+      hitimes (~> 1.2)
+    timecop (0.9.1)
+
+PLATFORMS
+  java
+  ruby
+
+DEPENDENCIES
+  aws-sdk-dynamodb (~> 1.18)
+  bundler (~> 1.7)
+  codeclimate-test-reporter (~> 0)
+  connection_pool (>= 2.1.2)
+  diplomat (>= 2.0.2)
+  launchdarkly-server-sdk!
+  listen (~> 3.0)
+  rake (~> 10.0)
+  redis (~> 3.3.5)
+  rspec (~> 3.2)
+  rspec_junit_formatter (~> 0.3.0)
+  timecop (~> 0.9.1)
+
+BUNDLED WITH
+   1.17.3

data/LICENSE.txt

@@ -0,0 +1,13 @@
+Copyright 2014 Catamorphic, Co.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,56 @@
+LaunchDarkly Server-side SDK for Ruby
+===========================
+
+[![Gem Version](https://badge.fury.io/rb/launchdarkly-server-sdk.svg)](http://badge.fury.io/rb/launchdarkly-server-sdk)
+
+[![Circle CI](https://circleci.com/gh/launchdarkly/ruby-server-sdk/tree/master.svg?style=svg)](https://circleci.com/gh/launchdarkly/ruby-server-sdk/tree/master)
+[![Security](https://hakiri.io/github/launchdarkly/ruby-server-sdk/master.svg)](https://hakiri.io/github/launchdarkly/ruby-server-sdk/master)
+
+LaunchDarkly overview
+-------------------------
+[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/docs/getting-started) using LaunchDarkly today!
+ 
+[![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)
+
+Supported Ruby versions
+-----------------------
+
+This version of the LaunchDarkly SDK has a minimum Ruby version of 2.2.6, or 9.1.6 for JRuby.
+
+Getting started
+-----------
+
+Refer to the [SDK documentation](https://docs.launchdarkly.com/docs/ruby-sdk-reference#section-getting-started) for instructions on getting started with using the SDK.
+
+Learn more
+-----------
+
+Check out our [documentation](http://docs.launchdarkly.com) for in-depth instructions on configuring and using LaunchDarkly. You can also head straight to the [reference guide for this SDK](http://docs.launchdarkly.com/docs/ruby-sdk-reference).
+
+Generated API documentation is on [RubyDoc.info](https://www.rubydoc.info/gems/launchdarkly-server-sdk).
+
+Testing
+-------
+ 
+We run integration tests for all our SDKs using a centralized test harness. This approach gives us the ability to test for consistency across SDKs, as well as test networking behavior in a long-running application. These tests cover each method in the SDK, and verify that event sending, flag evaluation, stream reconnection, and other aspects of the SDK all behave correctly.
+ 
+Contributing
+------------
+ 
+We encourage pull requests and other contributions from the community. Check out our [contributing guidelines](CONTRIBUTING.md) for instructions on how to contribute to this SDK.
+ 
+About LaunchDarkly
+-----------
+ 
+* LaunchDarkly is a continuous delivery platform that provides feature flags as a service and allows developers to iterate quickly and safely. We allow you to easily flag your features and manage them from the LaunchDarkly dashboard.  With LaunchDarkly, you can:
+    * Roll out a new feature to a subset of your users (like a group of users who opt-in to a beta tester group), gathering feedback and bug reports from real-world use cases.
+    * Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
+    * Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
+    * Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.
+* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Check out [our documentation](https://docs.launchdarkly.com/docs) for a complete list.
+* Explore LaunchDarkly
+    * [launchdarkly.com](https://www.launchdarkly.com/ "LaunchDarkly Main Website") for more information
+    * [docs.launchdarkly.com](https://docs.launchdarkly.com/  "LaunchDarkly Documentation") for our documentation and SDK reference guides
+    * [apidocs.launchdarkly.com](https://apidocs.launchdarkly.com/  "LaunchDarkly API Documentation") for our API documentation
+    * [blog.launchdarkly.com](https://blog.launchdarkly.com/  "LaunchDarkly Blog Documentation") for the latest product updates
+    * [Feature Flagging Guide](https://github.com/launchdarkly/featureflags/  "Feature Flagging Guide") for best practices and strategies