thruster 0.1.3-aarch64-linux → 0.1.5-aarch64-linux

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +25 -25
  3. data/exe/aarch64-linux/thrust +0 -0
  4. data/lib/thruster/version.rb +1 -1
  5. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 508f3697ec94c14ed085a8c58aaef6d20f8d1c26ae6e7c7f0d5f9bfb20da3a94
4
- data.tar.gz: 01b6ef2a334c0cfbd53adade2e7e44c2af8771195e4bf2e71281cf70d8850454
3
+ metadata.gz: af050d68cda8acc203b082155bfb04f816b643e0c322c141520247638f097404
4
+ data.tar.gz: 05e7be1660d01b78c801e5d67e775eda15e51c63c1d17616eca5ca7bfa18c834
5
5
  SHA512:
6
- metadata.gz: e12e4d86587ca09de70e70ad0e7e0ca59842afabb3a902379f492519097aac389b026e6f4b80418673e9bd04f08867160118306d8ca5008333b2624b3478e6b8
7
- data.tar.gz: 17e13125bb31d56dda7511222bd01c1d7a4ce9887859a3d1e90cc32268ddff5cf9f06ebd58a9b725b74a580d14a307e20eb13813c1afa1e0d364b42bbca164d0
6
+ metadata.gz: 73d4d04e79a0258509638e272251821a9d3b44484473f27673b9a47f927746a03e7b0ec4dcfd3eae5f74fe0695c3923c46396e52212aad27d3e50ada31770d21
7
+ data.tar.gz: f04b047d8f510082f547c49aaa1144e0e9cc0a56e501cb7f350cef8c812b467ea9c312c4fd74f17d063e4af92b85b84f52fef0e30365c163d8cd3c7a090bc5e2
data/README.md CHANGED
@@ -5,7 +5,7 @@ applications. It runs alongside the Puma webserver to provide a few additional
5
5
  features that help your app run efficiently and safely on the open Internet:
6
6
 
7
7
  - HTTP/2 support
8
- - Automatic SSL certificate management with Let's Encrypt
8
+ - Automatic TLS certificate management with Let's Encrypt
9
9
  - Basic HTTP caching of public assets
10
10
  - X-Sendfile support and compression, to efficiently serve static files
11
11
 
@@ -14,9 +14,9 @@ and most features are automatically enabled with sensible defaults. The goal is
14
14
  that simply running your Puma server with Thruster should be enough to get a
15
15
  production-ready setup.
16
16
 
17
- The only exception to this is SSL provisioning: in order for Thruster to
18
- provision SSL certificates, it needs to know which domain those certificates
19
- should be for. So to use SSL, you need to set the `SSL_DOMAIN` environment
17
+ The only exception to this is TLS provisioning: in order for Thruster to
18
+ provision TLS certificates, it needs to know which domain those certificates
19
+ should be for. So to use TLS, you need to set the `TLS_DOMAIN` environment
20
20
  variable. If you don't set this variable, Thruster will run in HTTP-only mode.
21
21
 
22
22
  Thruster also wraps the Puma process so that you can use it without managing
@@ -59,10 +59,10 @@ with `thrust`. For example:
59
59
  $ thrust bin/rails server
60
60
  ```
61
61
 
62
- Or with automatic SSL:
62
+ Or with automatic TLS:
63
63
 
64
64
  ```sh
65
- $ SSL_DOMAIN=myapp.example.com thrust bin/rails server
65
+ $ TLS_DOMAIN=myapp.example.com thrust bin/rails server
66
66
  ```
67
67
 
68
68
 
@@ -72,27 +72,27 @@ In most cases, Thruster should work out of the box with no additional
72
72
  configuration. But if you need to customize its behavior, there are a few
73
73
  environment variables that you can set.
74
74
 
75
- | Variable Name | Description | Default Value |
76
- |-----------------------|---------------------------------------------------------------------------------|---------------|
77
- | `SSL_DOMAIN` | The domain name to use for SSL provisioning. If not set, SSL will be disabled. | None |
78
- | `TARGET_PORT` | The port that your Puma server should run on. Thruster will set `PORT` to this value when starting your server. | 3000 |
79
- | `CACHE_SIZE` | The size of the HTTP cache in bytes. | 64MB |
80
- | `MAX_CACHE_ITEM_SIZE` | The maximum size of a single item in the HTTP cache in bytes. | 1MB |
81
- | `X_SENDFILE_ENABLED` | Whether to enable X-Sendfile support. Set to `0` or `false` to disable. | Enabled |
82
- | `MAX_REQUEST_BODY` | The maximum size of a request body in bytes. Requests larger than this size will be refused; `0` means no maximum size is enforced. | `0` |
83
- | `STORAGE_PATH` | The path to store Thruster's internal state. Provisioned SSL certificates will be stored here, so that they will not need to be requested every time your application is started. | `./storage/thruster` |
75
+ | Variable Name | Description | Default Value |
76
+ |-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
77
+ | `TLS_DOMAIN` | Comma-separated list of domain names to use for TLS provisioning. If not set, TLS will be disabled. | None |
78
+ | `TARGET_PORT` | The port that your Puma server should run on. Thruster will set `PORT` to this value when starting your server. | 3000 |
79
+ | `CACHE_SIZE` | The size of the HTTP cache in bytes. | 64MB |
80
+ | `MAX_CACHE_ITEM_SIZE` | The maximum size of a single item in the HTTP cache in bytes. | 1MB |
81
+ | `X_SENDFILE_ENABLED` | Whether to enable X-Sendfile support. Set to `0` or `false` to disable. | Enabled |
82
+ | `MAX_REQUEST_BODY` | The maximum size of a request body in bytes. Requests larger than this size will be refused; `0` means no maximum size is enforced. | `0` |
83
+ | `STORAGE_PATH` | The path to store Thruster's internal state. Provisioned TLS certificates will be stored here, so that they will not need to be requested every time your application is started. | `./storage/thruster` |
84
84
  | `BAD_GATEWAY_PAGE` | Path to an HTML file to serve when the backend server returns a 502 Bad Gateway error. If there is no file at the specific path, Thruster will serve an empty 502 response instead. Because Thruster boots very quickly, a custom page can be a useful way to show that your application is starting up. | `./public/502.html` |
85
- | `HTTP_PORT` | The port to listen on for HTTP traffic. | 80 |
86
- | `HTTPS_PORT` | The port to listen on for HTTPS traffic. | 443 |
87
- | `HTTP_IDLE_TIMEOUT` | The maximum time in seconds that a client can be idle before the connection is closed. | 60 |
88
- | `HTTP_READ_TIMEOUT` | The maximum time in seconds that a client can take to send the request headers. | 30 |
89
- | `HTTP_WRITE_TIMEOUT` | The maximum time in seconds during which the client must read the response. | 30 |
90
- | `ACME_DIRECTORY` | The URL of the ACME directory to use for SSL certificate provisioning. | `https://acme-v02.api.letsencrypt.org/directory` (Let's Encrypt production) |
91
- | `EAB_KID` | The EAB key identifier to use when provisioning SSL certificates, if required. | None |
92
- | `EAB_HMAC_KEY` | The Base64-encoded EAB HMAC key to use when provisioning SSL certificates, if required. | None |
93
- | `DEBUG` | Set to `1` or `true` to enable debug logging. | Disabled |
85
+ | `HTTP_PORT` | The port to listen on for HTTP traffic. | 80 |
86
+ | `HTTPS_PORT` | The port to listen on for HTTPS traffic. | 443 |
87
+ | `HTTP_IDLE_TIMEOUT` | The maximum time in seconds that a client can be idle before the connection is closed. | 60 |
88
+ | `HTTP_READ_TIMEOUT` | The maximum time in seconds that a client can take to send the request headers and body. | 30 |
89
+ | `HTTP_WRITE_TIMEOUT` | The maximum time in seconds during which the client must read the response. | 30 |
90
+ | `ACME_DIRECTORY` | The URL of the ACME directory to use for TLS certificate provisioning. | `https://acme-v02.api.letsencrypt.org/directory` (Let's Encrypt production) |
91
+ | `EAB_KID` | The EAB key identifier to use when provisioning TLS certificates, if required. | None |
92
+ | `EAB_HMAC_KEY` | The Base64-encoded EAB HMAC key to use when provisioning TLS certificates, if required. | None |
93
+ | `DEBUG` | Set to `1` or `true` to enable debug logging. | Disabled |
94
94
 
95
95
  To prevent naming clashes with your application's own environment variables,
96
96
  Thruster's environment variables can optionally be prefixed with `THRUSTER_`.
97
- For example, `SSL_DOMAIN` can also be written as `THRUSTER_SSL_DOMAIN`. Whenever
97
+ For example, `TLS_DOMAIN` can also be written as `THRUSTER_TLS_DOMAIN`. Whenever
98
98
  a prefixed variable is set, it will take precedence over the unprefixed version.
data/exe/aarch64-linux/thrust CHANGED
Binary file
data/lib/thruster/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module Thruster
2
- VERSION = "0.1.3"
2
+ VERSION = "0.1.5"
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: thruster
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.3
4
+ version: 0.1.5
5
5
  platform: aarch64-linux
6
6
  authors:
7
7
  - Kevin McConnell
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2024-03-21 00:00:00.000000000 Z
11
+ date: 2024-07-09 00:00:00.000000000 Z
12
12
  dependencies: []
13
13
  description: A zero-config HTTP/2 proxy for lightweight production deployments
14
14
  email: kevin@37signals.com