URL shortener, pastebin & file-sharing service, written from the ground up in C. https://r8r.be
 
 
 
 
 
Go to file
Jef Roosens a22a2e5cfa
feat: create pastes directory; separate routes
2022-11-21 15:45:31 +01:00
crow@edf12f699e Configured start of project 2022-11-15 16:05:47 +01:00
src feat: create pastes directory; separate routes 2022-11-21 15:45:31 +01:00
tries feat: pave way for pastebin integration 2022-11-21 15:28:02 +01:00
.dockerignore Basic working version without persistent storage 2022-11-15 21:12:08 +01:00
.editorconfig feat: added randomly generated URLs 2022-11-21 12:03:16 +01:00
.gitignore Added a readme 2022-11-16 13:05:09 +01:00
.gitmodules Configured start of project 2022-11-15 16:05:47 +01:00
.woodpecker.yml feat: use more std::string 2022-11-21 14:19:56 +01:00
CMakeLists.txt I will murder cmake 2022-11-15 17:05:14 +01:00
Dockerfile Started dockerfile 2022-11-15 21:30:10 +01:00
Makefile feat: create pastes directory; separate routes 2022-11-21 15:45:31 +01:00
README.md Added a readme 2022-11-16 13:05:09 +01:00
landerctl feat: create pastes directory; separate routes 2022-11-21 15:45:31 +01:00

README.md

Lander

The idea

A URL shortener has always been on my list of things I'd like to write myself. It's simple, yet useful.

for our Algorithms & Datastructures 3 class, we had to implement three different tries (Patricia trie, ternary trie, and a custom one). Considering these are efficient string-based search trees, this gave me the idea to use it as the backend for a URL shortener!

This implementation currently uses a ternary trie as its search tree. The persistence model is very simple; I simply append a line to a text file every time a URL is added, and add the lines of this file to the trie on startup. The trie is stored completely im memory, and no I/O operations are required when requesting a redirect. This makes the server very fast.

The name

I gave up giving my projects original names a long time ago, so now I just use the names of my friends ;p