Skip to content

updating.rst

Latest commit

 

History

History
93 lines (57 loc) · 2.21 KB

updating.rst

File metadata and controls

93 lines (57 loc) · 2.21 KB

Updating

It is recommended to periodically update both Nextcloud and LibreSign in your local environment to ensure compatibility.

Updating Nextcloud

  • First, check if there are any local modifications in your Nextcloud repository:

    cd path/to/nextcloud
git status

    Note

    If there are uncommitted changes, resolve them (commit, stash, or discard) before pulling updates. This avoids conflicts when updating from the master branch.

  • Pull the latest changes from the Nextcloud master branch:

    git pull origin master

  • After pulling, the 3rdparty folder may be outdated. In that case, run:

    git submodule update --init --recursive

Updating LibreSign

  • Before starting a new task, always make sure your local main branch is up to date with the upstream repository:

    cd path/to/libresign
git checkout main
git pull upstream main

  • Then create your feature or fix branch from the updated main.

LibreSign - Host installation update

Use this flow when LibreSign is installed directly on the host in custom apps.

Go to the custom apps folder

cd /path/to/custom_apps

Switch to the target version branch

git clone https://github.com/LibreSign/libresign.git
cd libresign
git submodule update --init --recursive

chown -R www-data: .
git fetch origin stable32
git checkout stable32

Composer

docker run -it -v $PWD:/app --workdir /app composer composer install --no-dev --ignore-platform-req=ext-gd --ignore-platform-req=ext-bcmath --ignore-platform-req=ext-intl

npm

  • Install dependencies defined in package.json:

    docker run -it -v $PWD:/app --workdir /app node npm ci
docker run -it -v $PWD:/app --workdir /app node npm run build

Update the app in Nextcloud

occ app:enable libresign
occ libresign:install --all