Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gitlab-pages
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 167
    • Issues 167
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 17
    • Merge requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-pages
  • Issues
  • #464
Closed
Open
Created Sep 21, 2020 by Jaime Martinez@jaime🚀Maintainer0 of 1 task completed0/1 task

Make zip cache configurable

A simple in-memory cache was introduced in !351 (merged) and !364 (merged) with some hard-coded values. These should be configurable.

Proposal

  • Add configuration changes flag to Pages
    • Add a zipCacheConfig type and flags:
    • zip-cache-expiration
    • zip-cache-cleanup
    • zip-cache-refresh
    • zip-open-timeout
    • zip-cache-dataoffset-size
    • zip-cache-dataoffset-prune-count
    • zip-cache-readlink-size
    • zip-cache-readlink-prune-count
  • Add documentation
  • Add flag to omnibus

The following discussion from !351 (merged) should be addressed:

  • @jaime started a discussion: (+2 comments)

    question: are these values good enough? Should we make them configurable in future iterations?

Edited Nov 16, 2020 by Jaime Martinez
Assignee
Assign to
Time tracking