| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Dynamic background images need some further work
|
|\
| |
| |
| |
| | |
Fix markdown-it gist plugin code closing tag
Fix #596
|
|/
|
|
| |
fix #596
|
|\
| |
| | |
Hides empty export section
|
| | |
|
|\ \
| |/
|/| |
Add jsonlint script to ensure all json files are valid
|
| | |
|
|\ \
| | |
| | | |
Fix a typo in README.md
|
|/ / |
|
|\ \
| | |
| | | |
Make HSTS Behaviour Configurable (Fixes #584)
|
| | | |
|
| | | |
|
| |/ |
|
|\ \
| |/
|/| |
Provide table for permissions
|
| |
| |
| |
| | |
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
|
|\ \
| | |
| | | |
Fix missing boolean setting for HMD_URL_ADDPORT
|
| |/
| |
| |
| | |
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
|
|\ \
| | |
| | | |
Remove duplicated nodejs version in .travis.yml
|
| |/
| |
| |
| | |
lts/boron is v6
|
|\ \
| | |
| | | |
createdAt DESC with quotation marks did not work with MySQL fixes #565
|
| |/ |
|
|\ \
| | |
| | | |
Add version badge in README.md
|
| |/ |
|
|\ \
| |/
|/| |
Prevent argument breaking by spaces
|
|/ |
|
|\
| |
| |
| |
| | |
Fix broken profile images in GitLab
Fixes #549
|
| | |
|
|\ \
| | |
| | | |
Adds button style to "new note"
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Updates default max_line_len in uglifyjs
|
|/ / |
|
|\ \
| | |
| | | |
Correct documentation of S3 bucket
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Documentation added in aaf034b on Nov 17th 2016 says the S3 bucket can
be specified with `s3.bucket`, but commit c8bcc4c (#285) on Dec 18th
2016 used `s3bucket`. Instead of fixing the code (#552) to match the
documentation this commit changes just the documentation so that
existing configurations are not broken. Also, the `s3` object is passed
as is to `AWS.S3()`, which does not know the option `bucket` (but
silently ignores it in my test).
http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#constructor-property
Following the old documentation leads to this exception:
2017-09-23T09:42:38.079Z - error: MissingRequiredParameter: Missing required key 'Bucket' in params
at ParamValidator.fail (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/param_validator.js:50:37)
at ParamValidator.validateStructure (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/param_validator.js:61:14)
at ParamValidator.validateMember (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/param_validator.js:88:21)
at ParamValidator.validate (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/param_validator.js:34:10)
at Request.VALIDATE_PARAMETERS (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/event_listeners.js:125:42)
at Request.callListeners (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
at callNextListener (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/sequential_executor.js:95:12)
at /srv/hackmd/hackmd/node_modules/aws-sdk/lib/event_listeners.js:85:9
at finish (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/config.js:315:7)
at /srv/hackmd/hackmd/node_modules/aws-sdk/lib/config.js:333:9
at Credentials.get (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/credentials.js:126:7)
at getAsyncCredentials (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/config.js:327:24)
at Config.getCredentials (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/config.js:347:9)
at Request.VALIDATE_CREDENTIALS (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/event_listeners.js:80:26)
at Request.callListeners (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/sequential_executor.js:101:18)
at Request.emit (/srv/hackmd/hackmd/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Update yarn.lock
|
| |/ |
|
|\ \
| | |
| | | |
Typo in Polish translation
|
| |/ |
|
|\ \
| | |
| | | |
Fix naming typo.
|
| |/ |
|
| | |
|
| |
| |
| |
| | |
preventXSS twice
|
| | |
|
|/ |
|
|\
| |
| | |
Use git URLs in package.json
|
|/
|
|
|
|
|
|
|
| |
Using the "github:..." form to declare a dependency in package.json
makes npm attempt to install the package using an ssh clone rather than
an https clone. Some deployment environments may not allow ssh access
to external servers which will prevent the clones from succeeding. Using
the "git+https://..." form will clone the same repo from GitHub without
requiring ssh connectivity.
|