sci-oer / java-resource Goto Github PK

Javadocs, gradle docs are useful to have builtin to the container so the students do not require internet access to read the standard language documentation .

Currently the jupyter lab password is set using a deprecated method used for the jupyter notebooks

This is a java specific version of the container and should be renamed to reflect that.

This will have implications for the docker image name and the defaults for the automated builder

In the INTED paper we mentioned that some of the course content would only be accessible directly from the file system.

Perhaps preload the content into /builtin/work, then have all these files copied into the persistent mount

Currently wikijs is configured to require the internet to download some resources while it is running. This is not ideal, and instead side-loading support should be enabled by default.

Flip how the jupyter lab notebooks are loaded, instead of symlinking the custom notebooks into the containers internal storage the builtin notebooks should be copied to the storage volume if they are not already present. This will allow the builtin notebooks to be edited and saved while remaining persistent.

Some test packages are still being installed in this container, they should be removed

• nginx
• tini
• sudo ?

In the base container the wiki should be seeded with some of the basic container usage information

• Builtin tools
• hepfull aliases that have been added
• permissions and file locations
• how to extend the container
• support / feature requests
• the containers purpose

Since this resource is meant to be self contained gradle dependencies are fetched at compile time. All of the gradle dependencies for any sample applications should be pre fetched and cached within the image.

This may require some fancy gradle configuration work to use local caches.

currently it is only built for amd64

Bash completions are a nice to have feature that makes it a little bit easier to use the cli.

Specific tools that should have bash completions in this container:

• git
• java
• make

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update docker/build-push-action action to v5
• chore(deps): update docker/login-action action to v3
• chore(deps): update docker/metadata-action action to v5
• chore(deps): update docker/setup-buildx-action action to v3
• chore(deps): update docker/setup-qemu-action action to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

The wiki can be configured to import the posts from a git repository, however this needs to happen while the application is running.

Currently any seed content must be added manually, this is not conducive to automatically creating the image.

An image creation script should be developed that will:

1. start the base image without any customizations
2. configure the storage git repository:
   • set the URL
   • set the branch
   • set the ssh private key
   • configure to pull only from the repo
3. run the import from git repo
4. remove the git repo from the storage settings
5. deactivate the git repo storage setting
6. upload logo image asset
7. set site information
   • title
   • logo file
   • organization name
8. revoke api key
9. stop the docker container
10. copy the database.
11. create new image with the seed database

Some non standard librariers may be useful to include within the container.

This could be done by letting a user specify download urls or artifacts, or by providing a list of some common potential options

arg parse is an example that comes to mind