Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #558
Closed
Open
Issue created Sep 08, 2020 by Samuel GAIST@samuel.gaistOwner3 of 3 checklist items completed3/3 checklist items

Fix usage of URL_PREFIX

Currently the URL_PREFIX settings variable is used like a fully qualified URL in many parts of the website which is wrong. As the name suggests, this prefix shall essentially "move" all the URLs of the site behind it.

If a fully qualified address is needed it should be generated either using the request object associated with the method call or using Django's Sites framework.

This issue tracks the cleanup of the following:

  • Email generation
  • Template rendering
  • Other usages
Edited Sep 28, 2020 by Samuel GAIST
Assignee
Assign to
Time tracking