Subash Pathak
Subash Pathak
I would prefer to throw Checkit.ValidationError instead of plain error. ``` js // 'unique:users:email' Checkit.Validators.test = function(val, collection, field) { throw new Checkit.ValidationError('error message'); }; ```
Any updates on this ? I haven't been able to use my lan management app (for almost a month now) because of this issue.
I am currently using the [patch](https://github.com/Subash/lan-manager/blob/master/mikronode.patch) provided by @Fibrewire that runs [after npm install](https://github.com/Subash/lan-manager/blob/e05c960ce9129d6183a575cbeae06586639d0b70/Dockerfile#L30). Would be great to have this fix published to npm.
Can you also post your nuxt config? Looks like you are using ca.key and ca.cert instead of cert.key and cert.crt.
I apologize for the misunderstanding. This package doesn't install the certificate to the system trust store automatically so you have to trust the certificate manually to make the warning go...
The api outputs certificate text that you can write to a file with fs.writeFile
That would require adding a preferences window, that's a lot of work. Any specific reason why you want to configure the port ?
> Maybe it could be taken from an environment variable that you just have to document? If the variable doesn't exist, go with the default :-) Sounds reasonable.