You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A quick naive search on github using a query “intelephense.licenceKey” reveals the problem very soon - people committing their keys into the version control.
Would be nice to have intelephense.licenceKeyFile or intelephense.licenceKeyEnvVar to stop this from happening.
While it’s not implemented, how do I safely store the key if I still want to commit my coc-settings.json?
The text was updated successfully, but these errors were encountered:
if filereadable(expand("~/.vim/coc-user-config.vim"))
source ~/.vim/coc-user-config.vim
endif
added ~/.vim/coc-user-config.vim to .gitignore, contents:
let g:coc_user_config = {
\ "intelephense.licenceKey": "REAL_LICENCE_KEY",
\ }
But this method is not as good as if main page of coc-phpls might have suggested a more straightforward, and fool-proof approach. Right now, as I noticed, search on github "intelephense.licenceKey" and see how many people blindly copy-pasted and committed their actual keys to github.
A quick naive search on github using a query “intelephense.licenceKey” reveals the problem very soon - people committing their keys into the version control.
Would be nice to have
intelephense.licenceKeyFile
orintelephense.licenceKeyEnvVar
to stop this from happening.While it’s not implemented, how do I safely store the key if I still want to commit my coc-settings.json?
The text was updated successfully, but these errors were encountered: