shuttlebay 0.2.0-aarch64-linux → 0.2.1-aarch64-linux
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/docs/guide.md +47 -6
- data/lib/shuttlebay/shuttlebay.so +0 -0
- data/lib/shuttlebay/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: fe674b008d997e54f538c829df7114f774b0b69dc981ce9b8f0a3ac646a9670f
|
|
4
|
+
data.tar.gz: 7456ad62c67d55985b15776f51f3b9568058d6cb475bf15cdd5e6c6893850c39
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 313fc004e0fc3f19cd9b2357fa89819ac73096f5199037c604df810ef4012262dc16f9f331418d16d596865548269d88ef54cda53ccf03209299ce05233a0c0d
|
|
7
|
+
data.tar.gz: 9dd9a29f436328435136750f05b6e3976d92a9b724e3329e37ec64d442aa9331410a6a37c08a96d393f1f4b2b799058b8150108a4eb0d1dc58e188aa47dd715b
|
data/docs/guide.md
CHANGED
|
@@ -196,18 +196,59 @@ covers the rest.
|
|
|
196
196
|
## 8. TLS and HTTP/2
|
|
197
197
|
|
|
198
198
|
Behind a CDN or Kamal proxy, they terminate TLS and speak HTTP/2 to browsers;
|
|
199
|
-
Mothership listens on plain HTTP behind them
|
|
200
|
-
|
|
199
|
+
Mothership listens on plain HTTP behind them, and nothing here is needed.
|
|
200
|
+
|
|
201
|
+
To terminate TLS in Mothership itself (guardship 0.2.1 and later), get a
|
|
202
|
+
certificate first, then add a TLS bind.
|
|
203
|
+
|
|
204
|
+
**The certificate.** Mothership serves `public/`, so certbot's webroot mode
|
|
205
|
+
works while the app runs on plain HTTP:
|
|
206
|
+
|
|
207
|
+
```bash
|
|
208
|
+
mkdir -p public/.well-known/acme-challenge # create it before certbot runs
|
|
209
|
+
certbot certonly --webroot -w ./public -d example.com -d www.example.com
|
|
210
|
+
```
|
|
211
|
+
|
|
212
|
+
Create `.well-known` beforehand: Mothership skips the filesystem for
|
|
213
|
+
top-level names it has not seen in `public/` (it re-lists the directory
|
|
214
|
+
about once a second), so one certbot creates on the spot can miss the
|
|
215
|
+
validation request. One certificate can name every domain (`-d` repeated).
|
|
216
|
+
|
|
217
|
+
**The binds.**
|
|
201
218
|
|
|
202
219
|
```toml
|
|
203
220
|
[mothership.bind]
|
|
204
221
|
http = "0.0.0.0:80"
|
|
205
|
-
https = { addr = "0.0.0.0:443", tls = { cert = "/etc/letsencrypt/live/
|
|
222
|
+
https = { addr = "0.0.0.0:443", tls = { cert = "/etc/letsencrypt/live/example.com/fullchain.pem", key = "/etc/letsencrypt/live/example.com/privkey.pem" } }
|
|
223
|
+
|
|
224
|
+
[[bays.http]]
|
|
225
|
+
name = "web"
|
|
226
|
+
# command, args, workers, threads as before
|
|
227
|
+
routes = [
|
|
228
|
+
{ bind = "http", pattern = "/.*" },
|
|
229
|
+
{ bind = "https", pattern = "/.*" },
|
|
230
|
+
]
|
|
231
|
+
```
|
|
232
|
+
|
|
233
|
+
```ruby
|
|
234
|
+
# config/environments/production.rb
|
|
235
|
+
config.force_ssl = true # redirects HTTP to HTTPS, sends HSTS, secures cookies
|
|
206
236
|
```
|
|
207
237
|
|
|
208
|
-
Browsers
|
|
209
|
-
`rack.url_scheme = "https"
|
|
210
|
-
|
|
238
|
+
- Browsers get HTTP/2 (negotiated over ALPN). On the TLS bind the app sees
|
|
239
|
+
`rack.url_scheme = "https"` and `HTTPS=on`, so `force_ssl` and
|
|
240
|
+
`request.ssl?` work with no `assume_ssl` or forwarded headers.
|
|
241
|
+
- Renewals are picked up without a restart, within 30 s of certbot writing
|
|
242
|
+
them. A renewal that does not load is logged; the old one keeps serving.
|
|
243
|
+
- Let's Encrypt keys are readable by root only: run with access to them, or
|
|
244
|
+
have a certbot `--deploy-hook` copy the pair where the app's user can read
|
|
245
|
+
it. Ports 80 and 443 need `setcap cap_net_bind_service=+ep` on the binary,
|
|
246
|
+
`AmbientCapabilities=CAP_NET_BIND_SERVICE` under systemd, or a container.
|
|
247
|
+
|
|
248
|
+
From guardship 0.3, Mothership can also redirect HTTP to HTTPS itself
|
|
249
|
+
(`http = { addr = "0.0.0.0:80", https_redirect = true }`, ACME challenges
|
|
250
|
+
left on HTTP) and serve a certificate per domain on one bind
|
|
251
|
+
(`tls = [{ cert, key }, ...]`, picked by SNI); see the Mothership README.
|
|
211
252
|
|
|
212
253
|
## 9. Docker and Kamal
|
|
213
254
|
|
|
Binary file
|
data/lib/shuttlebay/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: shuttlebay
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.2.
|
|
4
|
+
version: 0.2.1
|
|
5
5
|
platform: aarch64-linux
|
|
6
6
|
authors:
|
|
7
7
|
- Abdelkader Boudih
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: exe
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2026-
|
|
11
|
+
date: 2026-11-18 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: rack
|