fixup! [Examples] Add SQLite

Signed-off-by: Paweł Marczewski <[email protected]>
gramineproject · Jul 19, 2021 · 3b67e5d · 3b67e5d
1 parent 9c5e1f1
commit 3b67e5d
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 3 deletions.
diff --git a/Examples/sqlite/.gitignore b/Examples/sqlite/.gitignore
@@ -1,3 +1,3 @@
-OUTPUT
+/OUTPUT
 /scripts/testdir/*
 !/scripts/testdir/.dummy
diff --git a/Examples/sqlite/Makefile b/Examples/sqlite/Makefile
@@ -32,8 +32,6 @@ sqlite3.manifest: manifest.template
 		-Darch_libdir=$(ARCH_LIBDIR) \
 		$< >$@
 
-# Generating the SGX-specific manifest (*.manifest.sgx), the enclave signature,
-# and the token for enclave initialization.
 sqlite3.manifest.sgx: sqlite3.manifest
 	graphene-sgx-sign \
 		--key $(SGX_SIGNER_KEY) \

diff --git a/Examples/sqlite/README.md b/Examples/sqlite/README.md
@@ -48,3 +48,7 @@ That means it is safe to access the same database file from multiple processes,
 but only within a **single Graphene instance**. In other words, a multi-process
 Graphene application is OK, but multiple Graphene instances should not access
 the same database file concurrently.
+
+Note that in a production setup, the database should be either mounted as a
+protected file, or from tmpfs, which would make it impossible to access from
+multiple Graphene instances anyway.