Paste server written in Haskell. Fork of Hpaste, fully freedom and privacy respecting and generally improved. At the time of writing there's an instance at .
fr33domlover 2e13ebbaf1 minor UI string changes | %!s(int64=9) %!d(string=hai) anos | |
---|---|---|
scripts | %!s(int64=10) %!d(string=hai) anos | |
sql | %!s(int64=9) %!d(string=hai) anos | |
src | %!s(int64=9) %!d(string=hai) anos | |
static | %!s(int64=9) %!d(string=hai) anos | |
.gitignore | %!s(int64=11) %!d(string=hai) anos | |
README.md | %!s(int64=9) %!d(string=hai) anos | |
Setup.hs | %!s(int64=13) %!d(string=hai) anos | |
amelie.conf.sample | %!s(int64=11) %!d(string=hai) anos | |
cabal.config | %!s(int64=9) %!d(string=hai) anos | |
hpaste.cabal | %!s(int64=9) %!d(string=hai) anos | |
hpaste.conf.sample | %!s(int64=9) %!d(string=hai) anos |
This is a simple paste server, a modified version of Chris Done's hpaste. Toothpaste can syntax-highlight some computer languages, and can post links into IRC channels.
Examples for some of the changes made:
Even after the modifications I made, there are hardcoded URLs in some places, and some extra links I added, which you may wish to change. More generally, it seems the original author wrote the code in his earlier days as a Haskell developer and the code in some places could use a big cleaner layout. So feel free to hack and impove!
Also, "hpaste" and "lpaste" are used when referring to the server in various
places in the code. Don't worry about it. Just go to the UI layout code and
change the UI strings and URLS you need. You can grep
for the URLs or first
launch the server and then take a look and see what you'd like to change.
Data is stored in a PostgreSQL database.
$ sudo su postgres --command 'createuser hpaste -P'
$ sudo su postgres --command 'createdb hpaste -O hpaste'
$ cat sql/schema.sql | psql -U hpaste -h 127.0.0.1 -d hpaste
You can also run the last line with the sql/data.schema
, which contains some
initial data such as lists of IRC channels and programming languages. Take a
look at that file and tweak as needed before you commit it to psql
.
$ cp hpaste.conf.sample hpaste.conf
Edit hpaste.conf
. Make sure the cache directory has correct permissions (the
user running the server needs to be able to create files there).
$ dist/build/hpaste/hpaste hpaste.conf
You can use cron or supervisord or similar to have the server launch automatically at boot time.
The server keeps some content in a cache, whose path is set in hpaste.conf
(/tmp/hpaste-cache
by default). Some changes to the code won't take effect
until you clear the cache and cause the server to generate new files there. You
can safely clear the cache like this:
$ rm -rf /tmp/hpaste-cache/*