971d497c1e
ref https://linear.app/tryghost/issue/ENG-1543/debounce-the-members-lastseenatupdater - The `LastSeenAtUpdater.updateLastSeenAt` function is called in response to a `MemberClickEvent` — when a member clicks a link in an email with tracking enabled. This function can be called many times for the same member in a short period of time if e.g. a link checker is clicking all the links in an email they received. - This function should only update a member's `last_seen_at` timestamp once per day. To accomplish this, `updateLastSeenAt` runs a `select...for update` query to find the member's current `last_seen_at` timestamp, and only updates the timestamp if the current `last_seen_at` is before the start of the current day. The `for update` is required to avoid a race condition, which previously caused this function to update the `last_seen_at` timestamp more frequently than needed, which results in many unnecessary database queries. However, we still run the initial `select...for update` query for each event, which seems to be resulting in contention for locks on the member's row in the `members` table. - This commit introduces a simple in-memory cache so that we avoid calling `updateLastSeenAt` if the member's `last_seen_at` timestamp has already been updated in the current day, which should avoid running so many `select...for update` queries and locking the `members` table up. |
||
|---|---|---|
| .github | ||
| .vscode | ||
| apps | ||
| ghost | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| LICENSE | ||
| nx.json | ||
| package.json | ||
| PRIVACY.md | ||
| README.md | ||
| SECURITY.md | ||
| yarn.lock | ||
Ghost.org •
Forum •
Docs •
Contributing •
Twitter
The easiest way to get a production instance deployed is with our official Ghost(Pro) managed service. It takes about 2 minutes to launch a new site with worldwide CDN, backups, security and maintenance all done for you.
For most people this ends up being the best value option because of how much time it saves — and 100% of revenue goes to the Ghost Foundation; funding the maintenance and further development of the project itself. So you’ll be supporting open source software and getting a great service!
Quickstart install
If you want to run your own instance of Ghost, in most cases the best way is to use our CLI tool
npm install ghost-cli -g
Then, if installing locally add the local flag to get up and running in under a minute - Local install docs
ghost install local
or on a server run the full install, including automatic SSL setup using LetsEncrypt - Production install docs
ghost install
Check out our official documentation for more information about our recommended hosting stack & properly upgrading Ghost, plus everything you need to develop your own Ghost themes or work with our API.
Contributors & advanced developers
For anyone wishing to contribute to Ghost or to hack/customize core files we recommend following our full development setup guides: Contributor guide • Developer setup
Ghost sponsors
A big thanks to our sponsors and partners who make Ghost possible. If you're interested in sponsoring Ghost and supporting the project, please check out our profile on GitHub sponsors ❤️
Getting help
Everyone can get help and support from a large community of developers over on the Ghost forum. Ghost(Pro) customers have access to 24/7 email support.
To stay up to date with all the latest news and product updates, make sure you subscribe to our changelog newsletter — or follow us on Twitter, if you prefer your updates bite-sized and facetious. 🎷🐢
Copyright & license
Copyright (c) 2013-2024 Ghost Foundation - Released under the MIT license. Ghost and the Ghost Logo are trademarks of Ghost Foundation Ltd. Please see our trademark policy for info on acceptable usage.