feat: Use Unkey and write a blog

[Khaan25]

What does this PR do?
Fixes #2150

Blog post: https://medium.com/@ziaurzai/rate-limiting-my-url-shortner-next-js-app-with-unkey-86342ecf1461

Live App: https://url-shortner-zia-unkey.vercel.app/

App repo: https://github.com/Khaan25/url-shortner/

I've added Live link in the Blog post. Moreover, I've also included the repo link the blog at last for people who wanna checkout the code.

Summary by CodeRabbit

• New Features
  • Added a new blog post entry about implementing rate limiting in a URL shortener application using Unkey.
  • Included a link to the blog post authored by Khaan25.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1d7293a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 28, 2024 4:46pm

[vercel]

@Khaan25 is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request introduce a new entry in a blog post list related to the use of Unkey in applications. Specifically, it adds a blog post by the user "Khaan25," dated October 28, 2024, which discusses implementing rate limiting in a URL shortener application using Unkey. The new entry is formatted consistently with existing entries, and the overall structure of the document remains unchanged.

Changes

File	Change Summary
oss.gg/8_use_unkey_blog.md	Added a new blog entry by Khaan25 dated 28-October-2024, linking to a Medium post on rate limiting with Unkey.

Assessment against linked issues

Objective	Addressed	Explanation
Add a new entry for blog contributions (#2150)	✅

Possibly related issues

• [oss.gg hackathon] Integrated unkey's ratelimiter into my project and wrote a blog post on the same #2346: This issue involves integrating Unkey's rate limiter and writing a blog post, which aligns with the new entry added in this PR.
• [oss.gg hackathon] Use Unkey in your app and write a blog post about it  #2575: This issue requests using Unkey's rate limiter and writing a blog post, which is similar to the content of the new blog entry.
• [oss.gg hackathon] - Use Unkey in your app and write a blog post about it #2566: This issue also involves writing a technical blog about using Unkey, which relates to the new blog post added.

Possibly related PRs

• docs: integrated unkey's ratelimiter into my project and wrote a blog post on the same #2347: This PR adds a blog entry related to integrating Unkey's rate limiter, which connects to the focus of this PR.
• chore: Updated 8 use unkey blog.md #2491: This PR updates a blog entry about rate limiting with Unkey, aligning with the theme of documenting Unkey's use in applications.

Suggested labels

🕹️ oss.gg, :joystick: 1500 points

Suggested reviewers

• mcstepp
• chronark
• perkinsjr
• MichaelUnkey

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8fb9d4d and 1d7293a.

📒 Files selected for processing (1)

• oss.gg/8_use_unkey_blog.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• oss.gg/8_use_unkey_blog.md

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏

[chronark]

I feel like this is gaming the system a little
you already got 750 points for the template, and now reuse the same thing for another 1500

I'll award 750 here, so in total this is 1500 for template+blog
/award 750

[oss-gg]

Awarding Khaan25: 750 points 🕹️ Well done! Check out your new contribution on oss.gg/Khaan25

[Khaan25]

Right. I've created two separate templates:

• one with standard rate limiting for a URL shortener
• another with time-based rate limiting for a URL shortener (where the link expires after a set time)

There was another submission where someone added unkeyed rate limiting to an existing project and received points for it.
I still made these 2 different, hope it clarifies :) @chronark

[Khaan25]

Hey, @chronark, any update :)