This issue has been created
There are 3 updates.
 
 
Cristal / cid:jira-generated-image-avatar-561e488e-dfcc-4cdb-af0f-e16f50a01a1f CRISTAL-470 Open

Allow the nextcloud backend root location to be configurable

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-771defc7-b549-4531-a98e-4e2e20532fda Manuel Leduc created this issue on 19/Feb/25 17:36
 
Summary: Allow the nextcloud backend root location to be configurable
Issue Type: cid:jira-generated-image-avatar-561e488e-dfcc-4cdb-af0f-e16f50a01a1f Improvement
Affects Versions: 0.11
Assignee: Unassigned
Components: Backend - FileSystem
Created: 19/Feb/25 17:36
Priority: cid:jira-generated-image-static-major-a4e137a4-9efa-4dfb-81a2-dd53879839a8 Major
Reporter: Manuel Leduc
Description:

Currently, the filesystem backend is always located at ~/.cristal.
This can be annoying for users.
Various use cases:

  • For users: being able to have different local wikis for different domains
  • For devs: being able to define a temporary location for functional tests (see CRISTAL-281) that we know to be empty at start, and that we can safely wipe after the tests

PS: The same is also true for the Nextcloud backend.

 
 

3 updates

 
cid:jira-generated-image-avatar-771defc7-b549-4531-a98e-4e2e20532fda Changes by Manuel Leduc on 19/Feb/25 17:37
 
Fix Version: 0.16
Description: Currently, the filesystem nextcloud backend is always located at {{ {} ~/.cristal { }} } .
This can be annoying for users.
Various use cases:
* For users: being able to have different local wikis for different
domains
* For devs: being able to define a temporary location for functional tests (see CRISTAL-281) that we know to be empty at start
domain , and that we can safely wipe after the tests

PS: The same is also true for the Nextcloud backend.
or in shared folders
Assignee: Pierre Jeanjean