[Bug 276739] security/vaultwarden config file config.json.sample is not a JSON

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276739

            Bug ID: 276739
           Summary: security/vaultwarden config file config.json.sample is
                    not a JSON
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: mr@FreeBSD.org
          Reporter: 000.fbsd@quip.cz
          Assignee: mr@FreeBSD.org
             Flags: maintainer-feedback?(mr@FreeBSD.org)

I already post about this issue back in October 2023 to maintainer's e-mail and
to ports@, but without any reply.

I noticed the change of config file location. It was previously in
local/etc/rc.conf.d/vaultwarden (and I still have this file)
But according to this https://reviews.freebsd.org/D41602 new install location
is local/www/data/config.json.sample so I looked in to this file and it is
totally different than local/www/data/config.json. 
The later is real JSON file, but config.json.sample is not a JSON file at all
so why it is named like it? 
(this is the source of the sample file
https://cgit.freebsd.org/ports/tree/security/vaultwarden/files/vaultwarden_conf.in) 

Beginning of the config.json:
------------------
{
  "domain": "http://localhost/vaultwarden/",
  "sends_allowed": true,
  "incomplete_2fa_time_limit": 3,
  "disable_icon_download": false,
  "signups_allowed": false,
  "signups_verify": false,
  "signups_verify_resend_time": 3600,
  "signups_verify_resend_limit": 6,
------------------

Beginning config.json.sample:
------------------
#Warning : Some of these settings may be overridden when changing settings on
the admin page or in the config.json file
#located by default at: /usr/local/www/vaulwarden/data/config.json

ROCKET_ADDRESS=127.0.0.1
export ROCKET_ADDRESS

ROCKET_PORT=4567 # your port here
export ROCKET_PORT
------------------

Note, there is also a typo in a commented path "vaulwarden" instead of
"vaultwarden"


What is the right way to configure vaultwarden now?

-- 
You are receiving this mail because:
You are the assignee for the bug.