From 526da797c55a5b43d7b69dadac5bb7ea254880cc Mon Sep 17 00:00:00 2001 From: Leopere Date: Sun, 19 Oct 2025 16:17:40 -0400 Subject: [PATCH] Fix ScanSnap WebDAV service URL and simplify explanations - Corrected URL from 192.168.1.119 to 192.168.0.119:9876 - Simplified technical explanations to focus on user experience - Added direct URL prominently in project descriptions - Removed complex WebDAV implementation details - Maintained key functionality information (fast scanning, auto-cleanup at 3am) --- docker/resume/index.html | 12 ++++----- docker/resume/stories/scansnap-webdav.html | 31 +++++++--------------- 2 files changed, 16 insertions(+), 27 deletions(-) diff --git a/docker/resume/index.html b/docker/resume/index.html index 50108dc..649e8af 100644 --- a/docker/resume/index.html +++ b/docker/resume/index.html @@ -303,15 +303,15 @@

ScanSnap WebDAV Service for buildersclub.ca

Timeframe: 2025-Present
- Overview: Developed a high-performance WebDAV service specifically optimized for buildersclub.ca members to rapidly digitize receipts and documents using ScanSnap scanners. + Overview: Developed a simple network scanner endpoint at http://192.168.0.119:9876 that allows buildersclub.ca members to rapidly digitize receipts and documents using ScanSnap scanners.

Key Contributions:

Impact: Enabled buildersclub.ca members to rapidly digitize receipts and documents with enterprise-grade performance, reducing manual document processing time by 95% while maintaining secure file handling practices.

Read more about the ScanSnap WebDAV Service →

diff --git a/docker/resume/stories/scansnap-webdav.html b/docker/resume/stories/scansnap-webdav.html index 485ff6a..6d5f4f2 100644 --- a/docker/resume/stories/scansnap-webdav.html +++ b/docker/resume/stories/scansnap-webdav.html @@ -58,7 +58,7 @@
  • Network Protocol: WebDAV 1.0/2.0 compliant

    • - For buildersclub.ca members: Access the scanner service here (clubhouse network only) + For buildersclub.ca members: Access the scanner service here (clubhouse network only)

    @@ -66,24 +66,14 @@

    The Technical Journey

    -

    When Finder Refuses to Play Nice

    +

    Simple Network Scanner Access

    - The first hurdle? Getting macOS Finder to actually connect to our WebDAV server. Turns out, Finder is incredibly - picky about WebDAV implementations. It expects very specific protocol responses that many standard WebDAV libraries - don't provide out of the box. + The system provides a straightforward network location where the ScanSnap scanner can send documents directly. + Just connect with Command+K in Finder, enter the URL, and you have instant access to a network drive ready for scanning.

    - After digging through Finder's network traffic and WebDAV specs, I discovered it needed three specific "hotfixes" - that mimic Windows server behavior: -

    - -

    - Once these were in place, Finder connected instantly. The whole experience felt native—just Command+K to connect, - and boom, you've got a network drive ready for scanning. + This creates a seamless experience - load your documents, hit scan, and they're immediately available on your computer + without any additional steps or software.

    Security Without the Headache

    @@ -222,11 +212,10 @@ schedule.every().day.at("03:00").do(cleanup_scans) dump files quickly, and users needed to grab those files easily. Mission accomplished with a fraction of the complexity.

    -

    macOS WebDAV is Quirky

    +

    Simple Network Integration

    - Apple's Finder WebDAV client has some very specific expectations that aren't always documented. The solution - involved reading through protocol specs, analyzing network traffic, and testing various server configurations. - Once you know the tricks (those three hotfix flags), it's actually rock solid. + The solution integrates directly with macOS Finder, making it immediately familiar to users without requiring + any special software or training. Connect once, and the scanner endpoint is always ready to receive your documents.

    Automatic Cleanup Changes Everything

    @@ -243,7 +232,7 @@ schedule.every().day.at("03:00").do(cleanup_scans)