docs: Update README with new Lightyear link #421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kagkarlsson
changed the title
|
Great to hear! And thank you for reporting back, pretty cool to hear db-scheduler is used in such a significant way!
Hehehe, good stuff! |
|
🎉 This issue has been resolved in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @kagkarlsson!
Nearly three years on from when we first started using db-scheduler, the library has scaled beautifully along with us, never causing a headache!
Now, we're a big-boy startup with the root domain lightyear.com. As a result, the old link will soon be obsolete.
Thank you once again for creating this library. We're planning to launch in Norway soon—just to get you onboard as a VIP customer! 😄
Old PR for reference: #268