summaryrefslogtreecommitdiff
path: root/config.json.example (unfollow)
Commit message (Collapse)AuthorFilesLines
2018-11-21Fix typo in config.json.exampleSheogorath1-1/+1
We recently added the new logging option. As it turns out, the new option was not added correctly, which points out that our current json linting is **not working**. It throws an error but doesn't break. This patch fixes the typo in the example. It does not fix the CI part. Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
2018-11-14Upgrade winstonSheogorath1-0/+2
Our log library got a new major version which should be implemented. That's exactly what this patch does. Implementing the new version of the logging library. Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
2018-07-31Add possibility to choose between version v3 or v4 for the gitlab api.Cédric Couralet1-1/+2
Apart from the uri versioning, one big change is the snippet visibility post data (visibility_level -> visibility) Default gitlab api version to v4 Signed-off-by: Cédric Couralet <cedric.couralet@gmail.com>
2018-06-24Rebrand HackMD to CodiMDSheogorath1-2/+2
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
2018-06-01Add Azure Blob Storage supportÁdám Hóka1-1/+6
Signed-off-by: Adam Hoka <hoka.adam@nexogen.hu>
2018-04-14Fix example configSheogorath1-2/+2
This commit fixes some json fromat issues in our config example that causes errors on setup. This change should fix it. Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
2018-03-30Fix CSP for disqus and Google AnalyticsSheogorath1-1/+3
This commit should fix existing problems with Disqus and Google Analytics enabled in the meta-yaml section of a note. Before this commit they were blocked by the strict CSP. It's still possible to disable the added directives using `addDisqus` and `addGoogleAnalytics` in the `csp` config section. They are enabled by default to prevent breaking changes. Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
2018-03-05Remove unused LDAP option `tokenSecret`Felix Schäfer1-1/+0
hackmdio/hackmd#754 Signed-off-by: Felix Schäfer <felix@thegcat.net>
2018-03-01Introduce ldap.useridFieldDustin Frisch1-1/+2
Signed-off-by: Dustin Frisch <fooker@lab.sh>
2018-01-23Add README and `config.json.example` contentSheogorath1-0/+7
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
2018-01-09Fix config.json.example format errorXiaodong Xu1-1/+1
2017-12-09parse HMD_LDAP_SEARCHATTRIBUTES env var as a comma-separated arrayalecdwm1-1/+1
Signed-off-by: Alec WM <firstcontact@owls.io>
2017-12-09Add setting `ldap.usernameField`Lukas Kalbertodt1-0/+1
This determines which ldap field is used as the username on HackMD. By default, the "id" is used as username, too. The id is taken from the fields `uidNumber`, `uid` or `sAMAccountName`. To give the user more flexibility, they can now choose the field used for the username instead.
2017-12-04added guide for SAML settingsNorihito Nakae1-1/+0
2017-11-29fixed the SAML callback URL to unconfigurable.Norihito Nakae1-1/+0
2017-11-28Initial support for SAML authenticationNorihito Nakae1-0/+16
2017-11-08added auth docs and images for GitHub and TwitterDevon Jue1-1/+7
2017-10-31Add mattermost authenticationChristoph Witzany1-0/+5
2017-10-22Move CSP logic to new file, Fix boolean config examplesLiterallie1-5/+5
Not sure why I was quoting these in the first place
2017-10-22Change CSP config format to be more intuitiveLiterallie1-0/+7
2017-10-13Make HSTS behaviour configurable; Fixes #584Literallie1-0/+9
2017-03-14Add config option for gitlab api scope and auto adapt gitlab snippet feature ↵Wu Cheng-Han1-1/+2
on it
2017-02-04Change database config development to sqlite, test to memorybananaappletw1-8/+3
2017-01-14Add google apiKey & dropbox appKey to config.jsonYukai Huang1-2/+4
2016-12-24Fix config mistakebananaappletw1-2/+4
2016-12-22Add sqlite for test environmentbananaappletw1-0/+4
2016-12-13Initial support for LDAP server authenticationalecdwm1-0/+12
Limitations as of this commit: - tlsOptions can only be specified in config.json, not as env vars - authentication failures are not yet gracefully handled by the UI - instead the error message is shown on a blank page (/auth/ldap) - no email address is associated with the LDAP user's account - no picture/profile URL is associated with the LDAP user's account - we might have to generate our own access + refresh tokens, because we aren't using oauth. The currently generated tokens are just a placeholder. - 'LDAP Sign in' needs to be translated to each locale
2016-10-05Create example configYukai Huang1-0/+52
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 11:08:10 +0000