url-shortener

Personal URL shortener

Visitor stats

Code stats

GitHub code size in bytes GitHub repo size GitHub language count GitHub top language GitHub last commit

Manage Links

Links are managed through src/links.json, which is seeded with a few examples to start:

{
	"/": "https://atanas.info",
	"in": "https://linkedin.com/in/scriptex",
	"tw": "https://twitter.com/scriptexbg"
}

It couldn’t be simpler: the key is the “shortlink” path that gets redirected, and the value is the target URL. Keys can be as short or as long as you want, using whatever mixture of characters you want. / is a special entry for redirecting the root path.

Go ahead and make an edit, then commit and push to your repository. The hosting provider you chose above should automatically build and deploy your change. That’s it!

Config

Environment variables are used to set config options. There is only one at this point:

Variable	Description	Values	Default
`USE_JS`	Whether to redirect with JavaScript instead of a `<meta>` refresh.	`1`, `0`	`0`

Install Manually

To install somewhere else, or just on your own machine:

Fork this repository to create your own copy and clone to your machine.
Make sure you have a compatible version of Node.js (see engines.node in package.json). nvm is the recommended installation method on your own machine:
```
 $ nvm install
```
Install dependencies with npm:
```
 $ npm install
```
Build the static site:
```
 $ npm run build
```
Deploy the generated _site directory to its final destination.

Development

The following includes a few instructions for developing. For 11ty-specific details – the static site generator that powers the url shortener – see their docs.

Install

Follow the “Install Manually” section above to setup on your own machine.

Start

Start the development server:

$ npm run dev

Code Style

Prettier is setup to enforce a consistent code style. It’s highly recommended to add an integration to your editor that automatically formats on save.

To run via the command line:

$ npm run lint

Releasing

After development is done in the development branch and is ready for release, it should be merged into the master branch, where the latest release code lives. Release It! is then used to interactively orchestrate the release process:

$ npm run release

Connect with me:

Support and sponsor my work:

This site is open source. Improve this page.