v1.5.5: Dependency updates

What's Changed

• Bump semver from 6.3.0 to 6.3.1 by @dependabot in #46
• Bump word-wrap from 1.2.3 to 1.2.5 by @dependabot in #48
• Bump the npm_and_yarn group across 1 directories with 1 update by @dependabot in #49
• Bump the npm_and_yarn group across 1 directory with 3 updates by @dependabot in #52

Full Changelog: v1.5.4...v1.5.5

v1.5.4: Dependency updates

Resolve security issues from dependencies, including some high severity. You should upgrade.

What's Changed

• Bump sqlite3 from 5.0.8 to 5.1.5 by @dependabot in #44
• Bump http-cache-semantics from 4.1.0 to 4.1.1 by @dependabot in #43

Full Changelog: v1.5.3...v1.5.4

v1.5.3: Update dependencies

Important dependency updates, including some security issues. You should upgrade!

v1.5.2: Fix name length bug

Name lengths can now (really!) be up to 40 characters. Woohoo!

v1.5.1: Update dependencies

Security updates, other updates. What's not to love?

v1.5.0: Docker support, Fix Rate limiting

The server now supports being without Cloudflare.

If using Cloudflare, the environment variable cloudflare_limiting should true.

Also supports Docker, thanks to @EirikFA .

v1.4.1: Revert DB

DB was modified during last release, but should not have been. Fix that.

v1.4.0: Pagination and rate limiting

Improvements

• Add rate limiting. This is set to 1000 per minute globally, and 15 uploads per minute.

  • These are currently hard set limits. The global limit can be customised using env.ratelimit.

• Added pagination. Pages are 200 images, and you can navigate through them. Helps to make loading a bit faster and means all images are now accessible - instead of just the last 600, as was previously the case.

Fixes

• Renamed home.js to dashboard.js, because it makes more sense and that is what the main file is called.

v1.3.2: Dependency security updates

Just pulling some dependencies up to date to resolve security issues.

I will be adding some other improvements soon.

v1.3.1: Logout no longer expires token

Logout in the previous version was a more true "log out". It would remove your cookie & remove the token.
Since Save-Server relies on a single token this also disables ShareX - which is not ideal, and is identical to the "Reset token" button, but without giving a new one.

If you think your token has been compromised, use the "Reset token" button in your settings.
If you would like to access a different account via. the dashboard, use the "Log out" button.

Just to stress this: Log out does not reset your token. Reset token does.