mark-twin 0.4.2 → 0.4.3

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 (3) hide show
  1. checksums.yaml +4 -4
  2. data/lib/twin/version.rb +1 -1
  3. metadata +7 -12
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 07baefa770954e6be785cd591c727fb287b7a64dcf84d4c83eb3c747978da7ba
4
- data.tar.gz: d29597f8f7b20380b658bd9127c5a72f904f8baea2e3dd20756a7431317e53bd
3
+ metadata.gz: 8f9146653ecf4288e9bd05297300344cc68b0606291d2bbc61c73f13aa067706
4
+ data.tar.gz: 30e5c66372ae4511a550ed522701505463586b72eaa7ddb79cf2b266b5d47681
5
5
  SHA512:
6
- metadata.gz: 43c56ce8ed70a445dd3dabf803e68d25651cafe7b4a04e90f4202680592ac447345ab0f55e0dbd09970004d553c84868ae6aec6a643f48cd71f5d2583e0c20a4
7
- data.tar.gz: 25043aaa4ddf2f30ed8b546f52e68dccd008493414a9c8447d44c2c36acc45d32e375977b0d8b927623d2e5d6e937f0b2b56ed28cb8be53c2eeedeea08c73871
6
+ metadata.gz: a4d702bfe0443951977d6db35e61697140a97d3c12c278a6eebcb58665e8aa35a1e3eb646c9fbdbac0187ca8368dc161a24ab9db12de0ac698c2e23a92f0a01a
7
+ data.tar.gz: bb56c6892a1b93b8d6108cbfcbdd82b7021cd89116a59b896d755646c699a805c5a08e73825d5e2297d20056de1b1f04f0ae8d3035006d34a2a8169cff3af5bf
data/lib/twin/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module Twin
2
- VERSION = "0.4.2"
2
+ VERSION = "0.4.3"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: mark-twin
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.4.2
4
+ version: 0.4.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Ralf Hülsmann
@@ -24,19 +24,14 @@ dependencies:
24
24
  - !ruby/object:Gem::Version
25
25
  version: '5.0'
26
26
  description: |
27
- Keeping two machines' configuration aligned usually ends in a shell script
28
- nobody dares touch, because the reasons behind it were never written down.
27
+ twin helps keep two machines' configuration aligned.
29
28
 
30
- twin puts the reasons and the instructions in the same file. A sync-file is
31
- ordinary Markdown: the prose explains why a path is synced, and fenced YAML
32
- blocks say what to do. rsync does the copying.
29
+ A sync-file is just Markdown: the prose says why a path is synced, and
30
+ fenced YAML blocks define what to do. rsync does the copying.
33
31
 
34
- It knows the awkward parts. Paths the other machine owns stay untouched and
35
- are named as such, not buried among build artefacts. When both sides changed
36
- since the last sync, twin shows a diff and asks before overwriting anything,
37
- once for the whole group, so a half-applied deploy is not a state it can
38
- leave you in. Targets are a local path, a mounted volume, or user@host:/path
39
- over ssh, with no difference in how they are used.
32
+ When both sides changed since the last sync, twin shows a diff and asks
33
+ before overwriting. A target is a local path, a mounted volume, or
34
+ user@host:/path over ssh, and twin treats all three the same.
40
35
 
41
36
  Interactive selection runs through fzf with a rendered Markdown preview; the
42
37
  same sync-files drive scriptable status, dry-run and sync commands.