Create your own Data Vault called "Personal Knowledge Container". A system implementing the Aqua Protocol for sovereign data management. Suitable for individuals and organisations alike.
In the script, there is a check on a timestamp (which needs to be manually incremented) and on a version with each run.
Files are created outside of the actual project, which is not ideal.
Proposal for solution:
In the DataAccounting repository, a Docker image is created with each push. This is based on the MediaWiki image (currently inblockio/micro-pkc-mediawiki:1.0.0-alpha.4), and the extension is already added there. With the version tag, it is now ensured which version is contained in this image and does not need to be checked again separately in the PKC script. This has the advantage that the script becomes slightly smaller and there is no need to mount "onthefly" things into the container where it is not necessary. It also brings a certain flexibility as only the tag in the Compose file needs to be swapped out and not an extra timestamp needs to be searched for the PKC script to run.
During the PKC setup, the project "https://github.com/inblockio/DataAccounting.git" is checked out and then copied and mounted via a volume. This has the following disadvantages:
Proposal for solution: In the DataAccounting repository, a Docker image is created with each push. This is based on the MediaWiki image (currently inblockio/micro-pkc-mediawiki:1.0.0-alpha.4), and the extension is already added there. With the version tag, it is now ensured which version is contained in this image and does not need to be checked again separately in the PKC script. This has the advantage that the script becomes slightly smaller and there is no need to mount "onthefly" things into the container where it is not necessary. It also brings a certain flexibility as only the tag in the Compose file needs to be swapped out and not an extra timestamp needs to be searched for the PKC script to run.