partial work

Author: thiennamdinh

compose/file-system/Dockerfile

@@ -1,4 +1,4 @@
-FROM ghcr.io/sandialabs/sync-journal/journal-sdk:1.0.1
+FROM ghcr.io/sandialabs/sync-journal/journal-sdk:1.0.3
 
 ARG REPOSITORY=https://raw.githubusercontent.com/sandialabs/sync-records/965c839ac6bed6db24541ba642089e8fa8063633/lisp/
 

compose/file-system/docker-compose.yml

@@ -14,7 +14,7 @@ services:
     security_opt:
       - apparmor:unconfined
     ports:
-      - 445:445
+      - ${SAMBA_PORT:-445}:445
     networks:
       - docker
     environment:
@@ -23,25 +23,20 @@ services:
       SAMBA_SECRET: ${SAMBA_SECRET:-secret}
       SAMBA_SHARE: ${SAMBA_SHARE:-data}
     volumes:
-      - ./data-back:/data-back
-
-  cryptography:
-    image: ghcr.io/sandialabs/sync-services/cryptography:1.0.0
-    container_name: cryptography
-    networks:
-      - docker
+      - ./data-back:/srv/data-back
 
   journal:
-    image: ghcr.io/sandialabs/sync-services/ledger:1.0.0
+    image: ghcr.io/sandialabs/sync-services/ledger:1.0.1
     container_name: journal
     networks:
       - docker
-    depends_on:
-      - cryptography
     environment:
       SECRET: ${SECRET}
       PERIODICITY: ${PERIODICITY:-2}
-      CRYPTOGRAPHY: http://cryptography.docker
+      WINDOW: ${WINDOW:-1024}
+      RUST_LOG: ${RUST_LOG:-info}
+    volumes:
+      - database:/srv/database
 
   interface:
     image: nginx:stable-alpine
@@ -54,3 +49,6 @@ services:
       - docker
     ports:
       - "${PORT:-8192}:80"
+
+volumes:
+  database:

compose/file-system/file-system.scm

@@ -38,7 +38,7 @@
                           file-system-file-make!
                           file-system-file-read
                           file-system-file-write!
-                          file-system-file-delet!)))
+                          file-system-file-delete!)))
     (if (null? functions) #t
         ;; todo: wrap the function to access ledger
         ;;  - pass in ledger instead of record

compose/file-system/notes.org

@@ -1,5 +1,18 @@
+* overall thoughts
+- general purpose would be better...
+  - implies that there is not a file-system.scm extension, right? right?
 * conclusion
+- question: should file system be a pure explorer?
 - the file-system thing is just a separate use case, not general-purpose explorer
+- differences between FS and sync web data models
+  - empty directories
+  - most attributes will be undefined and chmod/chown not possible
+    - could have a default file/directory and add optional (chmod/chown stuff)
+      - maybe that could go in a mirrored *state* *fs* folder
+  - lack of ability to build in more complex data
+  - scalability (do I really want to save a pdf as bytes in rocksdb?)
+    - why not?
+  - is everything just a text file unless it's bytes?
 * idea:
 - need function to check expression (maybe at control level?)
 * paths
@@ -19,3 +32,10 @@
 - if parses as expression, then do expression
 - if ascii, then string
 - if not ascii, then bytes
+* dones
+- figure out why there is such a long loop process start startup
+* Todos
+- get chmod/chown/etc to work
+- **really need to figure this out** get long documents to work
+- handle refcount deletes
+- have real directory attributes

compose/file-system/run.sh

@@ -5,22 +5,17 @@ if [ -z "$SECRET" ]; then
     exit 1
 fi
 
+if [ -z "$WINDOW" ]; then
+    WINDOW="#f"
+fi
+
+if [ -z "$RUST_LOG" ]; then
+    RUST_LOG="info"
+fi
+
 record=$( cat record.scm )
 control=$( cat control.scm )
 ledger=$( cat ledger.scm )
+file_system=$( cat file-system.scm )
 
-check_status() {
-    while true; do
-        echo "Polling for cryptography service"
-	    response=$( wget -qO - "$1" 2>/dev/null)
-	    if [ -n "$response" ]; then
-	        return 0
-	    else
-            sleep 1
-	    fi
-    done
-}
-
-check_status "${CRYPTOGRAPHY}/signature/key/deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef"
-
-./journal-sdk -b "($record \"$SECRET\" $control ($ledger \"$CRYPTOGRAPHY\" #t #f) $preload)" -s "(*step* \"$SECRET\")" -p 80 -c $PERIODICITY
+RUST_LOG=$RUST_LOG ./journal-sdk -b "($record \"$SECRET\" $control ($ledger \"$SECRET\" #f $WINDOW) $file_system)" -s "(*step* \"$SECRET\")" -p 80 -c $PERIODICITY -d database

services/fuse/.gitignore

@@ -0,0 +1 @@
+env/

services/fuse/Dockerfile

@@ -8,6 +8,9 @@ RUN apk update
 RUN apk --no-cache add tini bash samba tzdata shadow fuse-dev
 ENV FUSE_LIBRARY_PATH=/usr/lib/libfuse.so
 
+COPY requirements.txt .
+RUN pip install -r requirements.txt
+
 RUN addgroup -S smb
 RUN rm -f /etc/samba/smb.conf && rm -rf /tmp/* /var/cache/apk/*
 
@@ -28,8 +31,6 @@ ENV RW=true
 
 HEALTHCHECK --interval=60s --timeout=15s CMD smbclient --configfile=/etc/samba.conf -L \\localhost -U % -m SMB3
 
-COPY requirements.txt .
-RUN pip install -r requirements.txt
 COPY service.py .
 
 RUN echo "user_allow_other" >> /etc/fuse.conf

services/fuse/notes.org

@@ -23,3 +23,13 @@
     - 5
     - 6
     - ... for the last X files
+    -
+      
+* Okay... so how do I handle the flush/release crap?
+- if storing separately:
+  - store in back-end file system
+    - update the hash on release
+  - store in memory
+    - maintain case of access -> write -> release
+  - store in sync web
+    - write every time