Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 161
    • Issues 161
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Issues
  • #359

Closed
Open
Created Oct 19, 2020 by Georges Racinet@gracinet🦑Owner

Project and Namespace environment variables on hashed storage

When called from the Rails application, the Mercurial process receives information about the current project, passed as environment variables which can in turn be useful to hooks.

We have notably HEPTAPOD_PROJECT_PATH and HEPTAPOD_PROJECT_NAMESPACE_FULL_PATH, the concatenation of which is the relative URI of the project from the server base URL.

The initial implementation was done for #72 (closed), at a time when these paths could be inferred in a very straightforward way from the repository path on the file system. With the hashed storage, the repository file system path has nothing to do with the URI path of the project.

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