diff --git a/.forgejo/workflows/deploy.yml b/.forgejo/workflows/deploy.yml index 1157023..4a714b2 100644 --- a/.forgejo/workflows/deploy.yml +++ b/.forgejo/workflows/deploy.yml @@ -1,5 +1,10 @@ name: Deploy on webserver +defaults: + run: + # hugo container only has `sh` + shell: sh + on: push: branches: @@ -7,28 +12,22 @@ on: jobs: deploy: + if: github.repository_owner == 'www' name: Build site with hugo and deploy on success - runs-on: debian-13 + runs-on: psyinf-hugo-site-build + container: + volumes: + # for depositing the built site directly + - /home/www/srv:/www:rw steps: - name: Checkout - uses: https://hub.psychoinformatics.de/actions/taiki-e-checkout-action@v1 - - - name: Fetch theme - run: git submodule update --init --depth 1 -- themes/hugo-theme-relearn - - - name: Setup Hugo - uses: https://github.com/peaceiris/actions-hugo@v3 + uses: https://hub.datalad.org/forgejo/datalad-clone-action@v1 with: - hugo-version: '0.169.0' - extended: true + recursive: true + get_file_content: false - name: Generate site run: hugo - name: Deploy - uses: actions/git-pages@v2 - with: - site: https://rdm.sfb1451.de/ - server: hub.psychoinformatics.de - password: ${{ secrets.DNS_CHALLENGE_PASSWORD }} - source: public/ + run: cp -r public /www/_rdm.sfb1451.de && rm -rf /www/rdm.sfb1451.de ; mv /www/_rdm.sfb1451.de /www/rdm.sfb1451.de diff --git a/content/about/_index.md b/content/about/_index.md index 7438e3d..50cdedb 100644 --- a/content/about/_index.md +++ b/content/about/_index.md @@ -1,7 +1,7 @@ +++ title = 'Extras' -[build] +[_build] list = 'never' publishResources = true render = 'always' diff --git a/content/catalog/datalad-based-deposition.md b/content/catalog/datalad-based-deposition.md index 5afe4f2..f272b6a 100644 --- a/content/catalog/datalad-based-deposition.md +++ b/content/catalog/datalad-based-deposition.md @@ -77,8 +77,9 @@ the added metadata records. ### 4. Publish the update -> [!important] +{{% notice style="important" %}} This step assumes that the project has already been published (has a configured sibling). +{{% /notice %}} Then, push the new state of the dataset to an existing sibling: diff --git a/content/datalad/extensions/_index.md b/content/datalad/extensions/_index.md index 6f35593..26fc116 100644 --- a/content/datalad/extensions/_index.md +++ b/content/datalad/extensions/_index.md @@ -25,10 +25,11 @@ and in [DataLad-NEXT documentation](https://docs.datalad.org/projects/next/en/la ![DataLad graphical user interface](gooey_pushed.png) -> [!important] -> Currently, the DataLad-Gooey extension is *de facto* unmaintained. -> However, it was an important proof of principle, and we expect it to -> make a comeback in the future; likely in a completely new guise. +{{% notice style="important" %}} +Currently, the DataLad-Gooey extension is *de facto* unmaintained. +However, it was an important proof of principle, and we expect it to +make a comeback in the future; likely in a completely new guise. +{{% /notice %}} The DataLad-Gooey (pronounce \"GUI\") package provides a graphical user interface for DataLad. It is specifically aiming at making key data @@ -48,8 +49,9 @@ documentation](https://docs.datalad.org/projects/gooey/en/latest/index.html). ## DataLad-XNAT -> [!info] -> The DataLad-XNAT extension is currently unmaintained. +{{% notice style="info" %}} +The DataLad-XNAT extension is currently unmaintained. +{{% /notice %}} [XNAT](https://www.xnat.org/) is an open source imaging informatics platform developed by the Neuroinformatics Research Group at Washington @@ -78,8 +80,9 @@ documentation](http://docs.datalad.org/projects/datalad-xnat/en/latest/). ## DataLad-REDCap {#sec-datalad-redcap} -> [!info] -> The DataLad-REDCap extension is currently unmaintained. +{{% notice style="info" %}} +The DataLad-REDCap extension is currently unmaintained. +{{% /notice %}} DataLad-REDCap extension provides convenience commands for exporting data from [REDCap](https://project-redcap.org/) into DataLad datasets. diff --git a/content/walkthroughs/publication-catalog.md b/content/walkthroughs/publication-catalog.md index dc3ec35..47e76bd 100644 --- a/content/walkthroughs/publication-catalog.md +++ b/content/walkthroughs/publication-catalog.md @@ -4,23 +4,27 @@ draft = false title = 'Publication Catalog' +++ -> [!important] -> The workflow described here remains a valid description for dataset -> publication on Sciebo. However, as a means for submitting datasets to -> the SFB1451 catalog, it has been deprecated in favour of the procedure -> described in [Register data in the data catalog]({{% relref "/catalog/register-data" %}}). -> -> If publications are to be shown in the catalog, information about them -> needs to be included directly in the dataset (metadata) files, -> preferably using standard metadata formats (e.g as -> [citation file format references field](https://github.com/citation-file-format/citation-file-format/blob/main/schema-guide.md#references)) -> or as a [datalad-tabby publications table]({{% relref "/catalog/register-data/#table-publications" %}}). -> All datasets with -> project descriptions and publication metadata created according to the -> workflow description below (either by INF or by respective projects) -> have been republished to GitHub as the -> [sfb1451/all-projects](https://github.com/sfb1451/all-projects) -> superdataset. +{{% notice style="important" %}} + +The workflow described here remains a valid description for dataset +publication on Sciebo. However, as a means for submitting datasets to +the SFB1451 catalog, it has been deprecated in favour of the procedure +described in +[Register data in the data catalog]({{% relref "/catalog/register-data" %}}). + +If publications are to be shown in the catalog, information about them +needs to be included directly in the dataset (metadata) files, +preferably using standard metadata formats (e.g as +[citation file format references field](https://github.com/citation-file-format/citation-file-format/blob/main/schema-guide.md#references)) +or as a [datalad-tabby publications table]({{% relref "/catalog/register-data/#table-publications" %}}). +All datasets with +project descriptions and publication metadata created according to the +workflow description below (either by INF or by respective projects) +have been republished to GitHub as the +[sfb1451/all-projects](https://github.com/sfb1451/all-projects) +superdataset. + +{{% /notice %}} ## Publication Catalog from Sciebo: a walkthrough @@ -75,11 +79,11 @@ it: cd my-project datalad run-procedure cfg_text2git -> [!info] -> The `run-procedure cfg_text2git` will configure DataLad so that text -> files will not be annexed -- this is a useful setting for the files we -> will be adding. - +{{% notice style="info" %}} +The `run-procedure cfg_text2git` will configure DataLad so that text +files will not be annexed -- this is a useful setting for the files we +will be adding. +{{% /notice %}} ### Create a citation file @@ -131,11 +135,11 @@ DataLad: datalad save -m "Add citation file" CITATION.cff -> [!info] -> Citation File Format is a standard for plain text files with human- and -> machine-readable information for datasets (and software). You can read -> more on the [CFF website](https://citation-file-format.github.io/). - +{{% notice style="info" %}} +Citation File Format is a standard for plain text files with human- and +machine-readable information for datasets (and software). You can read +more on the [CFF website](https://citation-file-format.github.io/). +{{% /notice %}} ### Add bibliographic information to the dataset @@ -174,27 +178,29 @@ If this is the first time you are using DataLad with Sciebo, you will be prompted for your credentials. -> [!info] -> Sciebo uses your entire e-mail address (name@example.com) as its username. +{{% notice style="info" %}} +Sciebo uses your entire e-mail address (name@example.com) as its username. +{{% /notice %}} -> [!info] -> The `--dataset` option lets us explicitly specify the dataset for which -> we configure a sibling. The `--name` option sets the name which we will -> use later when publishing. The `--mode filetree` option enables filetree -> mode, meaning that the sibling will have the same, human-readable, file -> tree layout as the folder on your drive. -> -> The WebDAV url can be obtained from Sciebo\'s web UI, by clicking at -> \"Settings\" in the lower left. This URL points to the user\'s home -> directory, and any subfolders must be appended \"by hand\". Nonexisting -> subfolders will be created. The URLs will be different for different -> instances and users. For example, with FZJ\'s instance, the full URL to -> the dataset folder would look like this (`` and `` are -> placeholders): -> -> ``` -> https://fz-juelich.sciebo.de/remote.php/dav/files///pub-dataset -> ``` +{{% notice style="info" %}} +The `--dataset` option lets us explicitly specify the dataset for which +we configure a sibling. The `--name` option sets the name which we will +use later when publishing. The `--mode filetree` option enables filetree +mode, meaning that the sibling will have the same, human-readable, file +tree layout as the folder on your drive. + +The WebDAV url can be obtained from Sciebo\'s web UI, by clicking at +\"Settings\" in the lower left. This URL points to the user\'s home +directory, and any subfolders must be appended \"by hand\". Nonexisting +subfolders will be created. The URLs will be different for different +instances and users. For example, with FZJ\'s instance, the full URL to +the dataset folder would look like this (`` and `` are +placeholders): + +``` +https://fz-juelich.sciebo.de/remote.php/dav/files///pub-dataset +``` +{{% /notice %}} ### Publish to Sciebo diff --git a/content/z03/access-data.md b/content/z03/access-data.md index 01cfc9b..7df6744 100644 --- a/content/z03/access-data.md +++ b/content/z03/access-data.md @@ -1,7 +1,7 @@ +++ date = '2025-02-12T18:01:59+01:00' draft = false -title = 'Accessing motor assessment data collection' +title = 'Accessing motor assessment data collection on Windows' weight = 4 +++ @@ -9,85 +9,11 @@ This note will explain in detail how to set-up your local copy of the aggregated Overview of the encrypted workflow and prerequisites are explained in the [encrypted workflow](z3-encrypted-workflow/) page. It is highly recommended that you read it first. -The note assumes that you have access to a shared copy of the dataset, and the data is being encrypted to your GPG key. - -## Distributed storage - -There are two components to the dataset: - -- The Git repository (which we can call a "lightweight dataset") contains information about content identity and availability, but does not contain the actual data. -- The content managed by git-annex ("annexed data"), i.e. the actual data. - -Each can be stored in / retrieved from multiple locations. -Depending on the platform used, the Git repository and annexed data can be stored and shared together (as is the case with Cerebra) or separately (JuGit + Sciebo). -The chart below illustrates the Git and git-annex repositories which can be configured as "remotes" for a local clone. -In the chart below, a square box symbolizes a Git remote, and cylinders symbolize Git-annex special remotes. -Retrieving data requires interacting with both kinds of remotes, and the main operations are shown over the lines. - -```mermaid -flowchart TD - A(Your local dataset clone) - AA["**Cerebra** (restricted)"] - AB[("**Cerebra-mask** (restricted, encrypted)")] - subgraph Deprecated - B["**JuGit** (public)"] - C[("**Sciebo** (restricted, encrypted)")] - end - D[("**INM-7 storage** (restricted, encrypted)")] - AA --- AB - A ---o |clone, update| AA - A ---o |enableremote, get| AB - A ---o |clone, update| B - A ---o |initremote, get| C - A ---o |"🚫"| D -``` - -Note that Cerebra is a special case: it could store the Git repository and its annex in a single remote. However, using encryption requires us to set up a [mask special remote](https://git-annex.branchable.com/special_remotes/mask/) for the annex, which shows separately in the list of annex remotes, but uses the same transport (think: the same credentials) as the Git remote. - -Because no data are stored in JuGit, the repository can be made public, and fetching information from JuGit requires no credentials. -However, access to the data stored in Sciebo or Cerebra-mask requires not only credentials, but also possession of a GPG key for which the data are encrypted. -Note that the Git repository also indexes data stored in INM7-storage, but that special remote is not accessible outside INM-7. - -The JuGit + Sciebo setup continues to be maintained for a transition period, but will be phased out in favour of Cerebra. - +The note assumes that you are working on Windows and using cmd shell. It also assumes that you have access to the shared Sciebo folder, and the data is being encrypted to your GPG key. ## Before you begin -### Cerebra token - -Instead of using your password (the one you use to log in to Cerebra), for DataLad (Git, git-annex) operations you should be using a token. Tokens are like passwords, but they are generated by the website rather than created by the user. A token can be revoked when it is no longer used or there is a risk that it got exposed. - -To generate a token: - -- Visit Cerebra and log in. -- Click your avatar in the top-right corner, and navigate to Settings → Applications. -- Under *Access tokens* click *New access token* and fill in the form: - - give the token a recognizable name; - - choose either "All" or "Specific repositories" for *Repository and organization access* (if you choose the latter, don't forget to select the repositories); - - under *Select permissions*, enable "repository: Read and write"; - - click *Generate token*. -- The token appears as a long string. Copy the generated value, and store it safely. It disappears after refreshing. - -Treat your token like a password. Do not share it with anyone. Once generated, the token can be used until revoked. - -### Git credential helper - -To avoid having to enter the token multiple times, we recommend using a Git credential helper. - -The easiest one to configure is [git-credential-cache](https://git-scm.com/docs/git-credential-cache), which temporarily (default timeout: 15 minutes) stores passwords in memory. It can be made default by setting a global Git configuration): - -``` -git config --global credential.helper cache -``` - -You may also configure a credential helper with persistent storage, for example one which interacts with your preferred password manager. You can also use OAuth (redirects to browser login and creates a temporary bearer token). Credential management is a matter of personal taste, so we can not document all possibilities here. Instead, see Git documentation about [credential helpers](https://git-scm.com/doc/credential-helpers) for a list of available options [^3]. - -### GPG (Windows) - -> [!info] -> This section is Windows-specific, and assumes you are using cmd shell. -> -> On GNU/Linux (and likely MacOS), no additional configuration is needed. +### GPG If you install Git (which is a requirement for using DataLad), it comes with its own `gpg` executable. If you install gpg4win (which is the solution recommended for digital signatures in our docs on [Input signing](digital-signatures) it naturally comes with a separate `gpg` executable. This means it is possible to have two GPG programs... which store their data (e.g. keys) in completely different locations on your computer. @@ -109,15 +35,121 @@ Then (if it is gpg4win) tell Git to use this one. Git-annex obeys the same setti git config gpg.program PATH/TO/GPG ``` + +### GPG-agent + +Operations which use your secret key (like downloading encrypted data with git-annex or listing your secret keys with `gpg --list-secret-keys`) require interactions with a program called `gpg-agent` [^2]. Normally, `gpg-agent` should be running in the background, and there is nothing to do. + +If you notice gpg-agent is not running (e.g. `get` fails with an error message which says that gpg-agent is not running, or you can not list your secret keys), you can start the gpg-agent with: + +``` +gpg-connect-agent reloadagent /bye +``` + +### Sciebo token (app password) + +Instead of using your password (the one you use to log in to Sciebo), it is recommended to generate a token for use with DataLad & git-annex. Tokens are like passwords, but they are generated by the website rather than created by the user. A token can be revoked when it is no longer used or there is a risk that it got exposed. + +To generate a token: + +- log in to Sciebo +- click your username on the upper right and go to settings +- select Security +- scroll down to App passwords / tokens +- enter a token name and click "Create new app passcode" +- copy (and store safely) the username and token + +The token name can be anything - it is only for your information, and will be displayed in the list of tokens, with the date of last use and an option to delete (revoke) the token. + + +## WebDAV URLs + +When using DataLad & git-annex, you will connect to Sciebo through a protocol called WebDAV. For this, you need to know your WebDAV URL, which is slightly different than the URL you use to visit Sciebo's web interface. + +### Base WebDAV URL + +To find your WebDAV address: + +- go to Sciebo (file view) +- click ⚙️ Settings in the lower left corner +- a "drawer" will slide up, showing your WebDAV URL + +The WebDAV URL will look like this: + +``` +https://fz-juelich.sciebo.de/remote.php/dav/files/j.doe%40fz-juelich.de/ +``` + +### WebDAV URLs to folders + +The URL above is pointing to your home directory. To access a specific folder, you will need to add some path components manually. + +Most likely, a folder named `Z03` will be shared with you. It will contain some folders; `motor_export_data` is the relevant one. + +The folder path relative to your home directory will depend on whether you move the shared folder or not. Assuming that `Z03` is in your home directory on Sciebo, the relative paths will be `Z03/motor_export_repo` and `Z03/motor_export_data`, respectively. + +For use with DataLad, you will need to put the base URL and the relative paths together. Using the example above, +and assuming that the shared folder is in the top-level directory, the data folder URL (for initremote) is: + + +``` +https://fz-juelich.sciebo.de/remote.php/dav/files/j.doe%40fz-juelich.de/Z03/motor_export_data +``` + + +## Distributed storage + +There are two components to the dataset: + +- The Git repository (which we can call a "lightweight dataset") contains information about content identity and availability, but does not contain the actual data. +- The content managed by git-annex ("annexed data"), i.e. the actual data. + +For technical reasons they are stored and shared separately. +In the chart below, a square box symbolizes a Git remote, and cylinders symbolize Git-annex special remotes. + +```mermaid +flowchart TD + A(Your local dataset clone) + A ---o |clone, update| B["**JuGit** (public)"] + A ---o |initremote, get| C[("**Sciebo** + (restricted, encrypted)")] + A ---o |"🚫"| D[("**INM-7 storage** + (restricted, encrypted)")] +``` + +Retrieving data requires interacting with both the Git remote and the Git-annex special remote (key commands are shown over the lines). +Because no data are stored in JuGit, the repository can be made public, and fetching information from JuGit requires no credentials. +However, access to the data stored in Sciebo requires not only credentials, but also possession of a GPG key for which the data are encrypted. +Note that the Git repository also indexes data stored in INM7-storage, but that special remote is not accessible outside INM-7. + ## Initial setup +#### Let git-annex know your token + +Git-annex needs WebDAV credentials to access the stored repository and data. +It expects them to be provided via environment variables. +Set the environment variables with the `set` command (substitute your Sciebo username and token): + +``` +set WEBDAV_USERNAME=j.doe@fz-juelich.de +set WEBDAV_PASSWORD=XXXXX-XXXXX-XXXXX-XXXXX +``` + +Important: do not put the password in quotes (`""`), because `set` command treats them literally. + +Tip: you can check the value of an environment variable with `echo`, e.g. `echo %WEBDAV_USERNAME%`. + +The environment variables persist until you close your cmd. +However, these credentials will later be cached in a owner-read-only file in the clone, +so re-entering the credentials should not be needed for subsequent updates. + ### Clone the dataset -Clone the (lightweight) dataset from Cerebra (using the URL below) into a directory with a name of your choice +Clone the (lightweight) dataset from JuGit (using the URL below) into a directory with a name of your choice (here: `motor_export`): ``` -datalad clone https://cerebra.fz-juelich.de/sfb1451-z03-internal/motor-assessment motor_export +datalad clone https://jugit.fz-juelich.de/m.szczepanik/motor-assesment.git motor_export ``` Then change your working directory to go into the dataset: @@ -125,43 +157,70 @@ Then change your working directory to go into the dataset: cd motor_export ``` -### Enable the mask special remote +### Initialize sciebo remote -Git-annex special remotes represent methods of transporting data. In this particular case, a *mask special remote* was set up to store encrypted data alongside the repository in Cerebra. Enabling it (and transferring data) requires having a matching GPG key. For this reason, it is not enabled automatically. +Git-annex special remotes represent methods of accessing data, and special remote configuration contains things like access URL or encryption type to be used. -Optionally, you can start by checking the list of available special remotes. -Each special remote has its own ID and assigned name, which can be used interchangeably inside git-annex commands. To list remotes known to the dataset, run: +One weaknes of the Sciebo setup is that WebDAV URLs contain user names and instance names, so will be different for each user (even though the shared folder is, in principle, the same). The dataset already has a sciebo remote, but it points to FZJ's sciebo and Michał Szczepanik's user account. There is no easy way to reconfigure it, other than each user initializing a new remote pointing to *their* sciebo URL. + +The trick is to initialize a special remote, and mark it *same as* the one above (meaning that we expect to reach exactly the same place, just through different means). + +This is by far the most involved part of the setup. + +#### (optional): check available remotes +Each special remote has its own ID and assigned name, which can be used interchangeably with git-annex commands. To list remotes known to the dataset, run: ``` git annex info ``` -Pending future changes, the remote we want to enable is going to be named cerebra-storage, -and it should appear in the list of *semitrusted repositories* like this: +Pending future changes, the remote we want to enable is going to be named sciebo-storage, +i.e. it will be this one: ``` -f095040a-18b7-4648-849e-f154c53ce976 -- cerebra-mask +325dd4e6-e71b-4512-bce6-0eb574b6ed15 -- sciebo-storage ``` -To enable the cerebra-mask special remote, run: +#### Initialize your own private special remote + +As explained above, you will need to initialize a special remote for yourself, and mark it "same as" the one above. + +Here's the command broken up into multiple lines with a caret (`^`) for readability. ``` -git annex enableremote cerebra-mask +git annex initremote my-sciebo-storage^ + --private^ + --sameas sciebo-storage^ + type=webdav^ + url="" ``` -You should see the following output: +And this is the same as a one-liner: -``` output -enableremote cerebra-mask (encryption update) (to gpg keys: [abbreviated]) ok -(recording state in git...) +``` +git annex initremote my-sciebo-storage --private --sameas sciebo-storage type=webdav url="" ``` -If that didn't work, see the *Troubleshooting* section below. +Substitute the `` with your data URL (the one which ends with `motor_export_data`)! + +{{% notice style="note" %}} +In the example above, we enclosed the URL with double quotes (`"...")`. +Keep in mind that cmd distinguishes single- and double quotes and treats them differently! +Find out more in https://ss64.com/nt/syntax-esc.html +{{% /notice %}} + +#### Troubleshooting + +- If the error message complains about credentials (bearer authentication), most likely the credentials (environment variables) are incorrect. +- If the error message complains about gpg-agent not running, it is either not running or git-annex is using a different gpg than intended. See sections on gpg and gpg-agent above. +- If there is seemingly no error but data can not be downloaded, then probably the URL given to initremote was incorrect. Make sure that the URL points to `motor_export_data` (not `repo`). + ## Data access -> [!note] -> This assumes your working directory is in the dataset (that you `cd`'ed into the dataset). +{{% notice style="note" %}} +This assumes your working directory is in the dataset (that you `cd`'ed into the dataset). +{{% /notice %}} To download data, use: @@ -189,19 +248,6 @@ git log ``` -## Troubleshooting - -Operations which use your secret key (like downloading encrypted data with git-annex or listing your secret keys with `gpg --list-secret-keys`) require interactions with a program called `gpg-agent` [^2]. Normally, `gpg-agent` should be running in the background, and there is nothing to do. - -If you notice gpg-agent is not running (e.g. `enableremote` or `get` fails with an error message which says that gpg-agent is not running, or you can not list your secret keys), you can start the gpg-agent with: - -``` -gpg-connect-agent reloadagent /bye -``` - -If an operation (e.g. `enableremote` or `get`) fails with an error message which says that a private key is not available (but you know from running `gpg --list-secret-keys` that your private key is configured), or the message says gpg-agent is not running (but you know it is) it is possible that you have more than one gpg program installed, and Git-annex uses a different one that you would expect. See the *GPG (Windows)* part of the *Before you begin* section above. - - [^1]: It would, at least in theory, be possible to modify the [PATH variable](https://en.wikipedia.org/wiki/PATH_(variable)) so that running `gpg` would use the Git-bundled gpg instead of the gpg4win gpg. [^2]: You call `datalad get`, DataLad calls `git annex get`; git-annex calls `gpg --decrypt`, and gpg asks gpg-agent for a matching secret key. -[^3]: For a more technical introduction to what Git credential helpers do, see this blog post: [Git The Stupid Password Store](https://tylercipriani.com/blog/2024/07/31/git-as-a-password-prompt/) +[^3]: The credential name and username are stored in global (i.e. user) Git configuration, the password is stored in Windows' secret storage. diff --git a/content/z03/encrypted-workflow.md b/content/z03/encrypted-workflow.md index 936695c..103c316 100644 --- a/content/z03/encrypted-workflow.md +++ b/content/z03/encrypted-workflow.md @@ -31,25 +31,8 @@ an e-mail signed with a trusted GPG or S/MIME signature). INF their GPG key fingerprint (which, ideally, they would have confirmed in person), and their intended access rights. -## Cerebra - data engineering platform - -We are using [Cerebra](https://cerebra.fz-juelich.de/) to exchange -encrypted data. A Cerebra account is required for access. Repositories -are grouped in an organization, in which Z03 members have administrator -privileges and can manage user permissions. Both the organization and -repositories are private, and are only accessible to designated users. - -Cerebra is a data engineering platform operated by INM-7 and hosted on -JSC Cloud at FZJ. It is powered by -[Forgejo-aneksajo](https://codeberg.org/forgejo-aneksajo/forgejo-aneksajo/wiki), -a fork of [Forgejo](https://forgejo.org/) which adds git-annex -support. - ## Sciebo - cloud storage -> [!note] -> With the availability of Cerebra, the use of Sciebo will be phased out. - We are using Sciebo () to exchange encrypted data. Z03 members would likely already have accounts via UzK/UKK () or Jülich diff --git a/hugo.toml b/hugo.toml index 9d218e6..2fe0b4e 100644 --- a/hugo.toml +++ b/hugo.toml @@ -1,5 +1,5 @@ baseURL = 'https://rdm.sfb1451.de/' -locale = 'en-us' +languageCode = 'en-us' title = 'SFB1451 RDM docs' theme= 'hugo-theme-relearn' diff --git a/themes/hugo-theme-relearn b/themes/hugo-theme-relearn index 289a038..adb82b0 160000 --- a/themes/hugo-theme-relearn +++ b/themes/hugo-theme-relearn @@ -1 +1 @@ -Subproject commit 289a03821aae0c5fc5dcd823f7bb000fd2b5d857 +Subproject commit adb82b040f7cda6de4d78892bb580a62f248d5ef