railwatch-server 0.1.1-x86_64-linux → 0.1.2-x86_64-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.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +2 -2
  3. data/lib/railwatch/server/version.rb +1 -1
  4. metadata +3 -3
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 786f76e1f3bfbfa4448c518ec41c02fbb693d0cddd0ade2aa0b82266909fc104
4
- data.tar.gz: ef5a2155577e752edf495e7d28ba356297403618996beaf6b5d5544c2e3ffd70
3
+ metadata.gz: ec93afa6ac6f35f0bb7d7e6c7f0705e3c2d2cf510a8eba63aa6eee469624ab96
4
+ data.tar.gz: 7c47ef197ab6265b2f2ef9cf48670f104a4cd614578708722fd8ea696bee53d4
5
5
  SHA512:
6
- metadata.gz: 526046c249399835db4b9d5a2e8298fb0ef8db0ca20a812026a79624d4c777a33ad6d78d7e8fb115a385bfae85afb399fa446fcf19ef4ac15d8645fc295ddb19
7
- data.tar.gz: 1d5ce7a42ed9fe924e183405457a9c14f8f4156c44eb6b9d9541a53274048261e3a162e0175260a7b30e10c07a0510fedae4d0162041e51c35038f2e1f2c4fd3
6
+ metadata.gz: d8ba4e1c8a6aaf4fa5a8cbf07f5cd274f6e8d77d1feb6afee2cfdd9c23a63f76d4e70408ac6a61ffeba621515ec53ccc37c9d1e6e4dc5161b6bc8d28a7a35471
7
+ data.tar.gz: 1a9c72a04a60cbb83faf1135e563c0dd8cc753b8dbc582429ca4e415df0fc69cfba5df18cf06309245bb366933e868dfb9b719ad221f4f8b3fce6e856296ab1c
data/README.md CHANGED
@@ -222,8 +222,8 @@ Puma workers, jobs ── railwatch agent ── /ingest ───────
222
222
  ## The server side (Rebulk/railwatch-rs)
223
223
 
224
224
  The server features this gem relies on are upstream, in Rebulk/railwatch-rs
225
- `main` from `ef87f72` (PR #16), and the dashboard's mount handling is in the
226
- railwatch gem from 0.9.3. Every setting is off by default, so a self-hosted
225
+ `main` from `ef87f72` (PR #16), and the dashboard's mount handling is part of
226
+ the server's frontend. Every setting is off by default, so a self-hosted
227
227
  install is unchanged. Documented in railwatch-rs `docs/SELF-HOST.md`,
228
228
  "Running behind an app".
229
229
 
data/lib/railwatch/server/version.rb CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  module Railwatch
4
4
  module Server
5
- VERSION = "0.1.1"
5
+ VERSION = "0.1.2"
6
6
  # The published railwatch-rs commit the bundled binaries are built from
7
7
  # (README, "The server side"); the Corresponding Source under AGPL-3.0.
8
8
  RAILWATCH_RS = "d4c842c2f02e1cd56aeedb1e9ad1403313f0aed8"
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: railwatch-server
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.1
4
+ version: 0.1.2
5
5
  platform: x86_64-linux
6
6
  authors:
7
7
  - Rebulk
@@ -15,14 +15,14 @@ dependencies:
15
15
  requirements:
16
16
  - - ">="
17
17
  - !ruby/object:Gem::Version
18
- version: 0.9.4
18
+ version: '1.1'
19
19
  type: :runtime
20
20
  prerelease: false
21
21
  version_requirements: !ruby/object:Gem::Requirement
22
22
  requirements:
23
23
  - - ">="
24
24
  - !ruby/object:Gem::Version
25
- version: 0.9.4
25
+ version: '1.1'
26
26
  - !ruby/object:Gem::Dependency
27
27
  name: railties
28
28
  requirement: !ruby/object:Gem::Requirement