Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 25 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,24 +80,27 @@ LITESTREAM_INSTALL_DIR=.bin

You configure the Litestream executable through the [`config/litestream.yml` file](https://litestream.io/reference/config/), which is a standard Litestream configuration file as if Litestream was running in a traditional installation.

The gem streamlines the configuration process by providing a default configuration file for you. This configuration file will backup all SQLite databases defined in your `config/database.yml` file to one replication bucket. In order to ensure that no secrets are stored in plain-text in your repository, this configuration file leverages Litestream's support for environment variables. The default configuration file looks like this if you only have one SQLite database:
The gem streamlines the configuration process by providing a default configuration file for you. This configuration file will backup all SQLite databases defined in your `config/database.yml` file to one replication bucket. In order to ensure that no secrets are stored in plain-text in your repository, this configuration file leverages Litestream's support for environment variables. Inspect which environment variables are available by running the `bin/rails litestream:env` command.

The default configuration file looks like this if you only have one SQLite database:

```yaml
dbs:
- path: storage/production.sqlite3
replicas:
- type: s3
bucket: $LITESTREAM_REPLICA_BUCKET
path: storage/production.sqlite3
bucket: $LITESTREAM_REPLICA_BUCKET
access-key-id: $LITESTREAM_ACCESS_KEY_ID
secret-access-key: $LITESTREAM_SECRET_ACCESS_KEY
```

This is the default for Amazon S3. The full range of possible replica types (e.g. other S3-compatible object storage servers) are covered in Litestream's [replica guides](https://litestream.io/guides/#replica-guides).

The gem also provides a default initializer file at `config/initializers/litestream.rb` that allows you to configure these three environment variables referenced in the configuration file in Ruby. By providing a Ruby interface to these environment variables, you can use any method of storing secrets that you prefer. For example, the default generated file uses Rails' encrypted credentials to store your secrets:
The gem also provides a default initializer file at `config/initializers/litestream.rb` that allows you to configure various variables referenced in the configuration file in Ruby. By providing a Ruby interface to these environment variables, you can use your preferred method of storing secrets. For example, the default generated file uses Rails' encrypted credentials to store your secrets.

```ruby
# config/initializers/litestream.rb
Rails.application.configure do
litestream_credentials = Rails.application.credentials.litestream

Expand All @@ -107,7 +110,21 @@ Rails.application.configure do
end
```

However, if you need manual control over the Litestream configuration, you can manually edit the `config/litestream.yml` file. The full range of possible configurations are covered in Litestream's [configuration reference](https://litestream.io/reference/config/). NB: If you configure a longer `sync-interval`, you may need to adjust `replication_sleep` when calling `Litestream.verify!`.
Outside of configuring Litestream's replication, you may also configure various other aspects of `litestream-ruby` itself.

```ruby
# config/initializers/litestream.rb
Rails.application.configure do
# ...

# Base controller used for Litestream dashboard
config.litestream.base_controller_class = "MyApplicationController"
# Set the location of the Litestream config
config.litestream.config_path = "config/litestream.yml"
end
```

However, if you need manual control over the Litestream configuration, you can edit the `config/litestream.yml` file. The full range of possible configurations are covered in Litestream's [configuration reference](https://litestream.io/reference/config/).

### Replication

Expand Down Expand Up @@ -232,6 +249,7 @@ You can verify the integrity of your backed-up databases using the gem's provide

```ruby
Litestream.verify! "storage/production.sqlite3"
Litestream.verify!(replication_sleep: 10) "storage/production.sqlite3"
```

In order to verify that the backup for that database is both restorable and fresh, the method will add a new row to that database under the `_litestream_verification` table, which it will create if needed. It will then wait `replication_sleep` seconds (defaults to 10) to give the Litestream utility time to replicate that change to whatever storage providers you have configured. After that, it will download the latest backup from that storage provider and ensure that this verification row is present in the backup. If the verification row is _not_ present, the method will raise a `Litestream::VerificationFailure` exception. This check ensures that the restored database file:
Expand All @@ -242,6 +260,9 @@ In order to verify that the backup for that database is both restorable and fres

After restoring the backup, the `Litestream.verify!` method will delete the restored database file. If you need the restored database file, use the `litestream:restore` rake task or `Litestream::Commands.restore` method instead.

> [!NOTE]
> If you configure Litestream's [`sync-interval`](https://litestream.io/reference/config/#replica-settings) to be longer than the default `replication_sleep` value of 10 seconds, you will need to adjust `replication_sleep` to a value larger than `sync-interval`; otherwise, `Litestream.verify!` may appear to fail where it actually simply didn't wait long enough for replication.

### Dashboard

The gem provides a web dashboard for monitoring the status of your Litestream replication. To mount the dashboard in your Rails application, add the following to your `config/routes.rb` file:
Expand Down
44 changes: 28 additions & 16 deletions lib/litestream/generators/litestream/templates/initializer.rb
Original file line number Diff line number Diff line change
Expand Up @@ -5,29 +5,41 @@
# or some other mechanism where the values are only available at runtime.

Rails.application.configure do
# An example of using Rails encrypted credentials to configure Litestream.
# Configure Litestream through environment variables. Use Rails encrypted credentials for secrets.
# litestream_credentials = Rails.application.credentials.litestream

# Replica-specific bucket location.
# This will be your bucket's URL without the `https://` prefix.
# Replica-specific bucket location. This will be your bucket's URL without the `https://` prefix.
# For example, if you used DigitalOcean Spaces, your bucket URL could look like:
#
# https://myapp.fra1.digitaloceanspaces.com
#
# And so you should set your `replica_bucket` to:
#
# myapp.fra1.digitaloceanspaces.com
# Litestream supports Azure Blog Storage, Backblaze B2, DigitalOcean Spaces,
# Scaleway Object Storage, Google Cloud Storage, Linode Object Storage, and
# any SFTP server.
# In this example, we are using Rails encrypted credentials to store the URL to
# our storage provider bucket.
#
# config.litestream.replica_bucket = litestream_credentials&.replica_bucket

# Replica-specific authentication key.
# Litestream needs authentication credentials to access your storage provider bucket.
# In this example, we are using Rails encrypted credentials to store the access key ID.
#
# Replica-specific authentication key. Litestream needs authentication credentials to access your storage provider bucket.
# config.litestream.replica_key_id = litestream_credentials&.replica_key_id

# Replica-specific secret key.
# Litestream needs authentication credentials to access your storage provider bucket.
# In this example, we are using Rails encrypted credentials to store the secret access key.
#
# Replica-specific secret key. Litestream needs authentication credentials to access your storage provider bucket.
# config.litestream.replica_access_key = litestream_credentials&.replica_access_key
#
# Replica-specific region. Set the bucket’s region. Only used for AWS S3 & Backblaze B2.
# config.litestream.replica_region = "us-east-1"
#
# Replica-specific endpoint. Set the endpoint URL of the S3-compatible service. Only required for non-AWS services.
# config.litestream.replica_endpoint = "endpoint.your-objectstorage.com"

# Configure the default Litestream config path
# config.config_path = Rails.root.join("config", "litestream.yml")

# Configure the Litestream dashboard
#
# Set the default base controller class
# config.litestream.base_controller_class = "MyApplicationController"
#
# Set authentication credentials for Litestream dashboard
# config.litestream.username = litestream_credentials&.username
# config.litestream.password = litestream_credentials&.password
end