doc: themes: remove unmaintained theme shaarli-blocks - Attention: This theme will no longer be updated - unmaintained since 2015
nodiscc
2023-11-02 16:40:51 +0100
doc: themes: remove unmaintained theme shaarli-launch - This repository has been archived by the owner on Aug 16, 2018. It is now read-only. - This theme is no longer maintained and won't get any support or update.
nodiscc
2023-11-02 16:38:40 +0100
doc: themes: remove unmaintained superhero theme - This repository has been archived by the owner on Oct 28, 2019. It is now read-only.
nodiscc
2023-11-02 16:36:46 +0100
doc: server configuration: update apache configuration, use php-fpm - remove apache 2.2 configuration (2.4 was released in 2012)
nodiscc
2023-10-04 14:30:11 +0200
doc: server configuration: remove outdated screencast - ref. https://github.com/shaarli/Shaarli/issues/2002 - uses old instructions/mod-php instead of the now recommended php-fpm - server configuration may not be the ideal page for this, installation would be more suitable
nodiscc
2023-09-25 16:13:16 +0200
doc: group all development-releated documentation under a single Development page - add the Development page to the main TOC
nodiscc
2023-09-25 15:45:17 +0200
replace mkdocs with sphinx/myst-parser for HTML documentation generation - fixes https://github.com/shaarli/Shaarli/issues/1451 - tools/.gitattributes: exclude doc/conf.py and doc/requirements.txt from zip exports - tools/doc/sphinx: suppress myst.xref_missing warnings caused by https://github.com/executablebooks/MyST-Parser/issues/564 - dockerfile: use makefile/sphinx instead of mkdocs to build HTML documentation - dockerfile: add bash to the docs build container (make: bash: No such file or directory) - tools/doc/readthedocs: force use of python 3.11 (readthedocs ERROR: No matching distribution found for sphinx==7.1.0) - tools/doc/readthedocs: add all required configuration variables https://docs.readthedocs.io/en/latest/config-file/v2.html#build-os - tools/doc/readthedocs: override build commands to allow the source directory to be different from the conf.py directory (https://docs.readthedocs.io/en/stable/config-file/v2.html#build-commands, https://github.com/readthedocs/readthedocs.org/issues/1543) - tools/doc/readthedocs: manually set output directory (readthedocs ERROR: No _readthedocs/html folder was created during this build.) - doc: replace all references to mkdocs with sphinx
nodiscc
2023-08-28 09:33:33 +0200
docker: update base alpine docker image to 3.16.7 - the previous (0.12.2) release image was based on 3.16.4 since the .patch version was not specified, which shows vulnerabilities when scanned with trivy (https://github.com/shaarli/Shaarli/pull/2019)
nodiscc
2023-10-03 18:43:24 +0200
doc: fix mkdocs build warnings/relative links INFO - Cleaning site directory INFO - Building documentation to directory: /home/live/GIT/Shaarli/doc/html INFO - Doc file 'index.md' contains an unrecognized relative link 'Usage#tag-cloud', it was left as is. Did you mean 'Usage.md#tag-cloud'? INFO - Doc file 'index.md' contains an unrecognized relative link 'Usage#picture-wall', it was left as is. Did you mean 'Usage.md#picture-wall'? INFO - Doc file 'index.md' contains an unrecognized relative link 'Usage#import-export', it was left as is. Did you mean 'Usage.md#import-export'? INFO - Doc file 'Community-and-related-software.md' contains an unrecognized relative link 'REST-API', it was left as is. Did you mean 'REST-API.md'? INFO - Doc file 'Community-and-related-software.md' contains an unrecognized relative link 'Theming', it was left as is. INFO - Doc file 'Installation.md' contains an unrecognized relative link 'dev/Development#third-party-libraries', it was left as is. Did you mean 'dev/Development.md#third-party-libraries'? INFO - Doc file 'Installation.md' contains an unrecognized relative link 'Upgrade-and-migration', it was left as is. Did you mean 'Upgrade-and-migration.md'? INFO - Doc file 'Plugins.md' contains an unrecognized relative link 'Shaarli-configuration', it was left as is. Did you mean 'Shaarli-configuration.md'? INFO - Doc file 'REST-API.md' contains an unrecognized relative link 'Server-configuration', it was left as is. Did you mean 'Server-configuration.md'? INFO - Doc file 'Reverse-proxy.md' contains an unrecognized relative link 'Shaarli-configuration', it was left as is. Did you mean 'Shaarli-configuration.md'? INFO - Doc file 'Server-configuration.md' contains an unrecognized relative link 'Directory-structure', it was left as is. INFO - Doc file 'Shaarli-configuration.md' contains an unrecognized relative link 'Translations', it was left as is. INFO - Doc file 'dev/Development.md' contains an unrecognized relative link 'Unit-tests', it was left as is. Did you mean 'Unit-tests.md'? INFO - Doc file 'dev/Development.md' contains an unrecognized relative link 'GnuPG-signature', it was left as is. Did you mean 'GnuPG-signature.md'? INFO - Doc file 'dev/GnuPG-signature.md' contains an unrecognized relative link 'Release Shaarli', it was left as is. INFO - Doc file 'dev/Theming.md' contains an unrecognized relative link 'Shaarli-configuration', it was left as is. INFO - Doc file 'dev/Translations.md' contains an unrecognized relative link 'Theming', it was left as is. Did you mean 'Theming.md'? INFO - Documentation built in 0.40 seconds
nodiscc
2023-08-20 23:13:59 +0200
tools: github actions: build docker images on pull requests - fixes https://github.com/shaarli/Shaarli/issues/1800 - do not push, only check that the image builds correctly - tag the image as :pr-PR_NUMBER
nodiscc
2022-11-04 16:34:30 +0100
tools/CI: scan repository with trivy security scanner (yarn.lock, composer.lock) - run scan on each push/pull request update - can be run locally using make test_trivy_repo - exit with error code 0/success when vulnerabilities are found, as not to make the workflow fail, a separate periodic run that exits with code 1 should be added in parallel - update trivy to v0.43.0 - https://github.com/aquasecurity/trivy/releases/tag/v0.43.0 - also consider TRIVY_EXIT_CODE when running trivy on the latest docker image - ref. https://github.com/shaarli/Shaarli/issues/1531
nodiscc
2023-05-21 22:16:48 +0200
gihub actions: fix value of TRIVY_TARGET_DOCKER_IMAGE - fixes Error response from daemon: no such image: ghcr.io/***:trivy: No such image: ghcr.io/***:trivy - introduced in https://github.com/shaarli/Shaarli/pull/1980 but the test target branch/tag was never reverted to 'latest'
nodiscc
2023-05-21 21:08:33 +0200
run trivy vulnerability scanner on the 'latest' docker image - run trivy from makefile so that it can be run both locally and through github actions - usage: make test_trivy TRIVY_TARGET_DOCKER_IMAGE=regist.ry/user/image:tag - tested by downgrading the base image to alpine 3.15.7 and verifying that vulnerabilities are reported (https://github.com/nodiscc/Shaarli/actions/runs/4860040980/jobs/8663400103) - TEMP/TESTING only push image to ghcr.io, run trivy on trivy branch/docker tag as well as master - ref. https://github.com/shaarli/Shaarli/issues/1531
nodiscc
2023-05-02 12:15:57 +0200
Knah Tsaeb
ArthurHoaro
nodiscc
David
dependabot[bot]
clach04
Amadeous
Alistair Young
Nicolas Le Gaillart
Gregory
bschwede