Getting Started

As of right now, junction is best used with ShareX. There is a basic user panel that can be used to shorten URL's as well. I've also successfully made an iOS Siri Shortcut that uses junction to shorten links.

git clone https://github.com/tycrek/junction.git && cd junction
npm i

Bindings

First, create a KV namespace and bind it to the worker. You can do this in the Workers dashboard.

junction expects the namespace to be called junction. For publishing, ensure your project is also called junction.

Environment Variables

For local dev, put these variables in a file called .dev.vars (formatted the same as a typical .env).

For production, set these values on the dashboard.

• TOKEN is used for requests to junction's KV API. Set to a random string.

Usage

To run locally, run npm run dev. This will launch the Wrangler dev server (press B to open the browser).

To publish, run npm run publish. This will build the project and publish it to Cloudflare Workers, under the project name junction.

API

GET /api/shorten/:url

Requires a Authorization header with a Bearer token. This token must match the TOKEN environment variable.

GET /:key

Redirects to the URL associated with the key, if it exists.

Adjusting the response type

By default, the API returns a JSON response with the following format:

{
  "key": "abc123",
  "url": "https://example.com/abc123"
}

You may request alternate response types by adding an Accept header to your request. The Response will match the format of the Accept type.

At this time, junction supports the following response types:

Supported response types

{
  "key": "12ab0",
  "url": "https://example.com/12ab0"
}

https://example.com/12ab0

<a href="https://example.com/12ab0">https://example.com/12ab0</a>

url=https%3A%2F%2Fexample.com%2F12ab0

<short>
  <key>12ab0</key>
  <url>https://example.com/12ab0</url>
</short>

junction does not support multiple Accept types. If you request multiple types, it may not behave as expected. I'll fix this in the future.

ShareX setup

1. Download and install ShareX.

2. Open ShareX and click Destinations in the left sidebar, then click URL Shortener, then select Custom URL shortener.

3. Click Destinations again, then click Custom uploader settings....

4. Create a new uploader with the following settings:

   Setting	Value
   Name	junction
   Destination type	URL shortener
   Method	GET
   Request URL	https://YOUR.DOMAIN.HERE/api/shorten/{input}
   Body	No body
   URL	https://YOUR.DOMAIN.HERE/{json:key}

   Add an Authorization header with the value Bearer YOUR-TOKEN-FROM-ABOVE.

5. In the bottom left of the Custom uploader settings window, choose junction as your URL shortener.

To shorten links with ShareX, either set a keybind or right-click the tray icon and select Upload > Shorten URL.... The link will be copied to your clipboard automatically.

Stack

• Cloudflare Workers - serverless hosting (technically Cloudflare Pages, because I prefer using the JAMstack frontend method)
• Hono.js - backend
• Pagery - frontend (landing page)

Why Pages, not Workers? There's only one file!

I chose Pages because I preferred Pages Advanced Mode + asset upload over Workers storing HTML contents in KV. Cloudflare themselves recommends this:

Consider using Cloudflare Pages for hosting static applications instead of Workers Sites.

I also found this way easier to incorporate my custom JAMstack framework, Pagery. So does a service like this require a Pages site? Not really. But I plan to add a user panel in the future, and Pages is a much better fit for that.