From 4e3b357d70f58b4ef754f7f1e4339d6c3911ed43 Mon Sep 17 00:00:00 2001 From: Hugo Osvaldo Barrera Date: Sat, 25 May 2024 19:54:27 +0200 Subject: [PATCH 1/2] Remove post content from listing The way subtitles get rendered is confusing, and this approach is much simpler than trying to tweak this. A shorter listing will likely be better once we have multiple articles too. --- assets/main.scss | 5 +++++ layouts/_default/single.html | 8 ++++++++ layouts/blog/section.html | 7 ++----- 3 files changed, 15 insertions(+), 5 deletions(-) diff --git a/assets/main.scss b/assets/main.scss index 672415c..bf3bcf8 100644 --- a/assets/main.scss +++ b/assets/main.scss @@ -84,3 +84,8 @@ article { margin-left: 1rem; } } + +.post-details { + color: gray; + margin-top: -1rem; +} diff --git a/layouts/_default/single.html b/layouts/_default/single.html index fea309d..f9eb7bb 100644 --- a/layouts/_default/single.html +++ b/layouts/_default/single.html @@ -1,5 +1,13 @@ {{ define "main" }}

{{ .Title }}

+{{ if and .Date .Params.Author }} +

+ Written by {{ .Params.Author }} on + +

+{{ end}}
{{ .Content }} diff --git a/layouts/blog/section.html b/layouts/blog/section.html index 8b160e6..f38e4f5 100644 --- a/layouts/blog/section.html +++ b/layouts/blog/section.html @@ -3,16 +3,13 @@
{{ range (where .Site.RegularPages "Section" "blog") }}
-

{{ .Title }}

-
+

{{ .Title }}

+
Written by {{ .Params.Author }} on
- - {{ .Content }} -
{{ end }}
From 483569ca7a9f20e8c657e69b4398da1c8abce19f Mon Sep 17 00:00:00 2001 From: Hugo Osvaldo Barrera Date: Sat, 25 May 2024 20:11:20 +0200 Subject: [PATCH 2/2] Vdirsyncer-2.0.0-alpha0 release notes --- assets/main.scss | 8 ++ .../2024-05-22-vdirsyncer-2.0.0-alpha0.md | 111 ++++++++++++++++++ 2 files changed, 119 insertions(+) create mode 100644 content/blog/2024-05-22-vdirsyncer-2.0.0-alpha0.md diff --git a/assets/main.scss b/assets/main.scss index bf3bcf8..fb47a8c 100644 --- a/assets/main.scss +++ b/assets/main.scss @@ -52,6 +52,8 @@ h1, h2, h3, h4, +.footnotes, +.highlight, .blog-post { max-width: 760px; margin-left: auto; @@ -89,3 +91,9 @@ article { color: gray; margin-top: -1rem; } + +.highlight { + pre { + padding: 0.5rem; + } +} diff --git a/content/blog/2024-05-22-vdirsyncer-2.0.0-alpha0.md b/content/blog/2024-05-22-vdirsyncer-2.0.0-alpha0.md new file mode 100644 index 0000000..778b0dc --- /dev/null +++ b/content/blog/2024-05-22-vdirsyncer-2.0.0-alpha0.md @@ -0,0 +1,111 @@ +--- +layout: post +title: Vdirsyncer 2.0.0-alpha0 release notes +date: 2024-05-22 +categories: blog +params: + author: WhyNotHugo +--- + +I've just tagged a first alpha version of the vdirsyncer rewrite. This is an +EXPERIMENTAL VERSION, and has several missing features. It likely has bugs too, +so I appreciate anyone willing to test this and report bugs. + +Keep in mind that as an early version, this MAY have bugs that result in data +loss. Ensure that you keep frequent backups. If you are unwilling to help report +bugs, please wait for a stable release. + +Compared to the previous series, there are a few exciting changes. + +## Continuing on errors + +When synchronising a collection, if a single items fails, synchronisation will +continue and other items will be processed properly. This has an impact when a +server rejects a single calendar event, but I want the other 500 events in my +calendar to synchronise properly. + +## Daemon + +A new `daemon` command has been implemented. This keeps vdirsyncer running and +performing new synchronisations every five minutes[^minutes]. In future +releases, I intend to implement storage monitoring, so instead of having a fixed +timeout, synchronisations will be triggered only when a storage reports that +changes have occurred. + +[^minutes]: This period is actually configurable. + +I have been running `vdirsyncer daemon` in the background for the last few weeks +and am quite happy with the results. + +## Collection creation and deletion + +When a collection is created or deleted on one side, this change will +immediately replicate to the other side (assuming that the affected collections +match the current configuration). + +This means that I can create a new calendar on one device, and it automatically +shows up on another. + +If this behaviour is problematic for some use case, please do reach out so we +can find a solution. + +## No more `discover` + +The `discover` command is gone and no longer necessary; discovery of collections +is handled automatically. + +## Conflict resolution + +Conflict resolution is not executed during normal synchronisations. This is +mostly because there commands are usually interactive and would interrupt the +automated flow or regular synchronisations. + +Use `vdirsyncer resolve-conflicts` to manually resolve any conflicts. + +## Testing + +Testers are welcome. Using a custom CA certificate and specifying TLS +certificate fingerprints has had minimal testing, so I would appreciate +real-world testing of this. + +When migrating from the previous vdirsyncer implementation, ensure that your +collections are already in sync. A new, separate status file is used, so any +changes on either side will result in conflicts. + +It is not trivial to migrate back to the previous version either: you will have +to ensure that both sides of your collection are in sync before doing so too. + +# Installation + +The current version needs to be built from source. The result is a single +binary, that can be copied onto other hosts without any additional support files +(note that binaries will only work across hosts of the same distribution and CPU +architecture). + +```sh +curl -LO https://git.sr.ht/~whynothugo/vdirsyncer-rs/archive/vdirsyncer/v2.0.0-alpha0.tar.gz +tar xf v2.0.0-alpha0.tar.gz +cd vdirsyncer-rs-vdirsyncer/v2.0.0-alpha0 +cargo build --release -p vdirsyncer +cp target/release/vdirsyncer /usr/local/bin/ +``` + +Replace `/usr/local/bin/` with any other directory in `$PATH`. + +Compilation will take a long time (several minutes, at least). I hope to improve +this in future releases, although Rust doesn't make this easy. Fortunately, this +cost pays off with vdirsyncer itself being quite lightweight at runtime. + +# Feedback + +See the [migration guide] for details on how to update a configuration file. +There is currently no documentation on setting up a new configuration from +scratch (this will be addressed at some point on a later release). + +Please [join us on IRC][contact] if you have feedback or questions. + +Issues are tracked in [a separate issue tracker][issues], to avoid any confusion +with existing issues from the previous implementation. + +[contact]: /contact/ +[issues]: https://todo.sr.ht/~whynothugo/vdirsyncer-rs