purls.py
Personal URL Shortener.
Today, we can use bit.ly or goo.gl or any of the other publicly available URL shorteners out there, but doing so limits us in the shortURLs we can choose, because the namespace is crowded with every other user.
With the abundance of new TLDs, it is once again possible for an individual to register a short personal domain relatively cheaply. With that domain in hand, purls.py allows one to quickly and easily host one’s own URL shortener with minimal dependencies and almost no setup.
Usage
purls.py runs on port 8880 by default, so if one is running Apache primarily, the following two lines of configuration in the Apache configuration file are sufficient to redirect the prefix /u/ to purls.py:
ProxyPass /u/ http://localhost:8880/ ProxyPassReverse /u/ http://localhost:8880/
The simplest invocation of purls.py requires only the domain prefix of the shortened URL’s to be passed. For example, if my domain prefix is https://hq6.me/u/, I can invoke purls as follows:
python purls.py https://hq6.me/u/
Installation
This software is only compatible with Python 2, so installation must be done with one of the following commands:
pip2 install purls pip2.7 install purls
Metadata
Release files for purls 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| purls-0.0.3.tar.gz | 6.0 kB | Without provenance | Details for purls-0.0.3.tar.gz |
Release files / purls-0.0.3.tar.gz
| Download URL | purls-0.0.3.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
edcd17de8d7ad0973a807afa17027d574a1c0c6ba47cc6c8895ad84e2216b21c
|
|
BLAKE2b-256 checksum How to use checksums |
4fe4c9fcce54da12d241ce73c547566eb0904f2c07829e766bbeb81d7fa52b78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for purls 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.