Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Vaultwarden
  3. Vaultwarden Branding

Vaultwarden Branding

Scheduled Pinned Locked Moved Vaultwarden
5 Posts 3 Posters 806 Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • andreasduerenA Offline
    andreasduerenA Offline
    andreasdueren
    wrote on last edited by
    #1

    Since v1.33.0 it is apparently possible to modify some of the branding. Has anyone experimented with that yet? I tried following the instructions but it doesn't seem to recognize the user.vaultwarden.scss.hbsfile.

    1 Reply Last reply
    2
    • andreasduerenA Offline
      andreasduerenA Offline
      andreasdueren
      wrote last edited by
      #2

      What it boiled down to is that assets linked in the handlebars file need to be located in /app/code/web-vault/images. @girish could we symlink this folder maybe so we can add custom logos etc?

      1 Reply Last reply
      2
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote last edited by
        #3

        I think this comes from the source - https://github.com/dani-garcia/bw_web_builds/tree/master/resources/src . Generally, we don't make source assets symlinkable (this applies to all apps and not just Vaultwarden). For example, if new assets appear there, there is no way to know if the whole directory was symlinked.

        andreasduerenA 1 Reply Last reply
        0
        • girishG girish

          I think this comes from the source - https://github.com/dani-garcia/bw_web_builds/tree/master/resources/src . Generally, we don't make source assets symlinkable (this applies to all apps and not just Vaultwarden). For example, if new assets appear there, there is no way to know if the whole directory was symlinked.

          andreasduerenA Offline
          andreasduerenA Offline
          andreasdueren
          wrote last edited by
          #4

          @girish said in Vaultwarden Branding:

          we don't make source assets symlinkable

          I'm not sure I understand the exact reasoning behind this yet. Is this a security concern or if this would create inconsistency issues.

          1 Reply Last reply
          0
          • nebulonN Away
            nebulonN Away
            nebulon
            Staff
            wrote last edited by
            #5

            The main reason is, that this makes it impossible to test package updates. So customization really can only be supported if the upstream app has a well defined process to do this outside of requiring the user to manually merge files with custom changes which may also be changed in the upstream release.

            1 Reply Last reply
            2
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search