From: Catonano <catonano@gmail.com>
To: Kristofer Buffington <kristoferbuffington@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Introducing GNUPaste
Date: Fri, 15 Dec 2017 05:57:24 +0100 [thread overview]
Message-ID: <CAJ98PDzC7bcqeKn9NqFzFN+tqc+=CD61Y-=KOE3ncjjC7D7KMw@mail.gmail.com> (raw)
In-Reply-To: <87k1xptatx.fsf@gmail.com>
Hi Kristofer !
2017-12-14 19:37 GMT+01:00 Kristofer Buffington <
kristoferbuffington@gmail.com>:
> Hello!
>
> I am excited to share GNUPaste! This is a really simple web app
> similar to paste.lisp.org built with Guile. I have a linode running it
> from git on GuixSD.
>
> https://paste.freshbakedyams.com (Please use it!)
> Source: https://github.com/kristoferbuffington/gnupaste.git
>
> Currently the frontend uses twitter bootstrap + jquery and highlightjs
> from a CDN. It really doesn't need all that boilerplate. It will
> definitely change in the future. GNUPaste depends on guile-wiredtiger
> and guile-fibers to compile.
>
> Ultimately I want to be able to deploy with something like:
>
> $ guix system disk-image gnupaste-system.scm
>
> Then boot it up in a VPS.
>
> I need to fix some issues with autotools before it can be installed with
> make. My issue is creating a consistent test-env because configure
> substitutes @localstatedir@ (root/gnupaste/config.scm.in) with a
> path/to/wt that is not in the build tree. I'm planning to imitate
> guix.git/build-aux/test-env in that regard.
>
> Otherwise, I would really appreciate some feature suggestions,
> especially if it involves using pubstrate!
>
> Thanks!
> Kris
>
>
thank you so much for this !
recently both paste.gnome and paste.lisp became unavailable and this little
thing of yours is usefful !
I made my first test paste
https://paste.freshbakedyams.com/paste/5A0RFWVR
I'd like to have a way to indicate that the text is scheme code so that it
could deal with strings and quoted blocs properly
I'm afraid this doesn't involve pubstate ;-)
But I'm not sure wat could be done involving pubstrate: maybe a button to
share my paste with my mastodon account ?
Anyway, thanks for you work !
next prev parent reply other threads:[~2017-12-15 4:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 18:37 Introducing GNUPaste Kristofer Buffington
2017-12-15 4:57 ` Catonano [this message]
2017-12-15 7:52 ` tomas
2017-12-15 9:13 ` ng0
2017-12-15 11:00 ` Ludovic Courtès
2017-12-16 16:53 ` Kristofer Buffington
2017-12-15 18:14 ` Mike Gerwitz
2017-12-16 15:46 ` Kristofer Buffington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ98PDzC7bcqeKn9NqFzFN+tqc+=CD61Y-=KOE3ncjjC7D7KMw@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=kristoferbuffington@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).