hfs 3.3.0 → 3.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -85,8 +85,10 @@ Troubleshooting
85
85
  you can [edit the config file to add your admin account](config.md#accounts)
86
86
  - If you don't want to use an editor, you can create the file with this command:
87
87
  `echo "create-admin: PASSWORD" > config.yaml`
88
- - For a new Docker installation, set `HFS_CREATE_ADMIN` to **only the password**, and log in as `admin`.
89
- The image uses this variable only when creating a new config file. See [Docker setup](https://github.com/rejetto/hfs/wiki/Docker).
88
+ - For a new Docker installation, set `HFS_INITIAL_ADMIN_PASSWORD` to **only the password**, and log in as `admin`.
89
+ It is used only when creating `config.yaml`; afterwards, manage the password in HFS and keep the config volume persistent.
90
+ The older `HFS_CREATE_ADMIN` takes precedence when non-empty and, by default, reapplies its password at every container start.
91
+ See [Docker setup](https://github.com/rejetto/hfs/wiki/Docker).
90
92
 
91
93
  By default, HFS does not require a login when you access the *Admin-panel* from localhost.
92
94
  If you don't like this behavior, disable it in the Admin-panel or enter this console command `config localhost_admin false`.
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "hfs",
3
- "version": "3.3.0",
3
+ "version": "3.3.1",
4
4
  "lockfileVersion": 3,
5
5
  "requires": true,
6
6
  "packages": {
7
7
  "": {
8
8
  "name": "hfs",
9
- "version": "3.3.0",
9
+ "version": "3.3.1",
10
10
  "license": "GPL-3.0",
11
11
  "dependencies": {
12
12
  "@gregoranders/csv": "^0.0.13",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hfs",
3
- "version": "3.3.0",
3
+ "version": "3.3.1",
4
4
  "description": "HTTP File Server",
5
5
  "keywords": [
6
6
  "file server",
package/src/config.js CHANGED
@@ -139,7 +139,7 @@ async function setConfig(newCfg, save) {
139
139
  const version = lodash_1.default.isString(newCfg.version) ? new Version(newCfg.version) : undefined;
140
140
  const considerEnvs = !process.env['HFS_ENV_BOOTSTRAP'] || !started && lodash_1.default.isEmpty(newCfg);
141
141
  // first time we consider also CLI args
142
- const argCfg = !started && lodash_1.default.pickBy((0, cross_1.newObj)(configProps, (_x, k) => (0, cross_1.tryJson)(k in argv_1.argv ? argv_1.argv[k] : considerEnvs ? process.env['HFS_' + k.toUpperCase().replaceAll('-', '_')] : '', lodash_1.default.identity)), x => x !== undefined);
142
+ const argCfg = !started && lodash_1.default.pickBy((0, cross_1.newObj)(configProps, (_x, k) => (0, cross_1.tryJson)(k in argv_1.argv ? argv_1.argv[k] : considerEnvs ? process.env['HFS_' + k.toUpperCase().replaceAll('-', '_')] : undefined, lodash_1.default.identity)), x => x !== undefined);
143
143
  if (!lodash_1.default.isEmpty(argCfg)) {
144
144
  (0, exports.saveConfigAsap)(); // don't set `save` argument, as it would interfere below, at check `save===false`
145
145
  Object.assign(newCfg, argCfg);