Skip to content

allow @files and externalModules dirs to persist on mounted storage #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 31, 2025

Conversation

labkey-willm
Copy link
Contributor

Rationale

system maintenance files are being lost on container restart because they are being mounted as a Docker volume. Similarly, externalVolumes was unable to be used because it was also set as a Docker volume. This update moves them both under the /labkey/files directory, typically mounted to external storage, so they can persist over container restarts and upgrades.

Related Pull Requests

Changes

  • remove @files as a Docker volume, so it comes in under the (usually external) /labkey/files mount
  • remove system maintenance files > 90 days old (which will now persist under @files)
    • add PURGE_MTNC_LOGS_OLDER_THAN_DAYS env var, default to 90
  • remove externalModules Dockfer volume, instead creating under (usually external) /labkey/files mount
    • add LABKEY_EXTERNAL_MODULES env var, default to /labkey/files/externalModules
  • add context.externalModules to application.properties
  • shift optional SLEEP to just before env var purge and java startup, for testing
  • bump quickstart version to 25.8

@labkey-willm labkey-willm merged commit e6622f8 into develop Jul 31, 2025
8 checks passed
@labkey-willm labkey-willm deleted the fb_53208_at_files_to_efs_and_ephemeral_vols branch July 31, 2025 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants