Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • omnibus-heptapod omnibus-heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • omnibus-heptapodomnibus-heptapod
  • Issues
  • #1

Closed
Open
Created Sep 02, 2020 by Georges Racinet@gracinet🦑Owner

Replace gitlab-rails sources by heptapod-rails

This is enough to produce packages with Heptapod frontend assets properly compiled (thumbnails and other images with discriminating hashes in their names, minified JavaScript code etc).

This is harder than it looks, because omnibus-gitlab very much wants to fetch the sources with Git and its own upstream Omnibus doesn't have a HgFetcher.

An intermediate step might be to switch to a manually prefetched directory in /var/cache/omnibus.

Then perhaps, we could just reuse parts of install_heptapod.py to do that fetching for us (and move heptapod_revisions.json to the omnibus-heptapod project).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking