model: Do not write version.txt inside storage

The intention of this file was that a Ceres executable could compare its
version with the version of the storage folder.

If the versions match the storage folder could be directly used. If the
storage version is lower the executable can apply migrations to the
storage folder until the versions match.

The problem is that executing migrations inside the database and
updating the version.txt cannot be atomic.

In contrast the version string could be saved inside the database itself
in a metadata table. In that case the migration together with the update
of the version string can be executed inside one database transaction
which guarantees atomicity.

The problem could still be that migrations should be applied also to the
files and folders inside the storage folder. This problem can only be
avoided by not using files to store data and instead use the BLOB
datatype if necessary.

Even in case of a future filesystem use it is still better to have the
guarantee that the database with file paths and metadata and the there
included version string are in sync.

1 files changed, 0 insertions, 1 deletions

diff --git a/main.go b/main.go
index 07e1c90..34d2425 100644
--- a/main.go
+++ b/main.go
@@ -38,7 +38,6 @@ func main() {
 		storage.Create()
 	}
 	log.Printf("Storage directory: %s\n", storage.Path)
-	storage.Init(gitDescribe)
 
 	model.InitDatabase(config.StorageFilePath)
 	defer model.CloseDatabase()