Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
lemonldap-ng
lemonldap-ng
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 244
    • Issues 244
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • LemonLDAP NG
  • lemonldap-nglemonldap-ng
  • Issues
  • #1840

Closed
Open
Opened Jul 04, 2019 by Xavier Guimard@guimardOwner

One-file skins

Summary

Today, custom skins are a little complex to do and require a lot of work on each upgrade. The goal of this issue is to be able to deploy a skin with only one file (that can be downloaded by the manager ?)

Design proposition

  • old-fashion skin method stays available (== duplicate bootstrap dir)
  • new fashion is named "standard-skin"
  • our skin is modified to include more than changing only background image (may be a .zip containing images and only one general HTML template)
  • standard-skin file is stored in configuration DB in a specific place
  • when portal detects that it has not the good file, it download it from configuration DB and deploy it in a directory (write authorized)
  • LLNG website proposes some of these new standard skins
Edited Jul 04, 2019 by Xavier Guimard
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: lemonldap-ng/lemonldap-ng#1840