Open markwilkinson opened 1 month ago
For what it's worth, we see the same confusion with our demo compose file at https://guides.dataverse.org/en/6.4/container/running/demo.html
I don't know about this dataverse-docker repo but over at https://github.com/IQSS/dataverse/blob/v6.4/docker/compose/demo/compose.yml we just have the one file store, which on the filesystem.
It's defined like this:
-Ddataverse.files.storage-driver-id=file1
-Ddataverse.files.file1.type=file
-Ddataverse.files.file1.label=Filesystem
-Ddataverse.files.file1.directory=${STORAGE_DIR}/store
So that's where "Filesystem" is coming from in the upstream repo. In this dataverse-docker repo, I'm not sure where the "Filesytem" label is coming from. 🤔
As for "Local"... I'm not sure where it comes from.
For another view we can use http://localhost:8080/api/admin/dataverse/storageDrivers which shows this:
{
"status": "OK",
"data": {
"Local": "local",
"Filesystem": "file1"
}
}
I added this to the agenda of our next Containerization working group meeting because I'm curious if anyone else there knows what's going on. 😅
(@markwilkinson you're welcome to come to these meetings if you like!)
@pdurbin I would probably enjoy that! But... you would have to arrange with the Supreme Being to add a few more hours to the day... ;-)
Hi!
Running the vanilla docker, v. 5.13 build 1244-79d6e57
I'm configuring my root dataverse, and one of the options is "Storage". The dropdown has "Local", "Local (default)", and "file" as choices.
What is the difference between them? I thought that dataverse was, by default, file... so are they all the same thing?
My next question will be related to this one...