mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-21 00:27:43 -05:00
DJ MountneyandGitHub
1cb7459803
Related to https://github.com/actualbudget/actual/issues/1695 It's pretty common for users to have self-signed certificates for actual, but this presents some challenges for the API. Give a little bit of guidance here, for new contributors. Really, all the info here is just for Node.js and not for actual. (we would want to create seperate http agents and our own certificate config system if we wanted to have actual specific config for this). For many of the existing api use-cases the `NODE_TLS_REJECT_UNAUTHORIZED` option will be fine. But `NODE_EXTRA_CA_CERTS` seems like the proper way to do things (and the one I tested on nodejs 21, on ubuntu via asdf install). But I also made sure to mention the option of using openssl's ca certificates, because if you are in a situation where your node.js is configured to link to the system openssl on Linux, it's going to be the easiest and most familiar to Linux sysadmins. It's just not the cross-platform supported option like `NODE_EXTRA_CA_CERTS`.