unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ng0 <ng0@n0.is>
To: Kristofer Buffington <kristoferbuffington@gmail.com>
Cc: guile-user@gnu.org, help-guix@gnu.org
Subject: Re: Introducing GNUPaste
Date: Fri, 15 Dec 2017 09:13:37 +0000	[thread overview]
Message-ID: <20171215091337.ai62h5znigkhvvbb@abyayala> (raw)
In-Reply-To: <87k1xptatx.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]

Hi Kristofer,

Kristofer Buffington transcribed 1.1K bytes:
> 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.

great start, I like it.
What would be really good is if there could be an API similar to
what pb (example instance: https://ptpb.pw) has.
The power of pb lies in its features and its ability to be used
from the commandline. I can simply upload the output of a command
without saving it first to a textfile - I can simply pipe it to curl.
So pb is built using flask (https://github.com/ptpb/pb).
I'd like to see (and maybe even help when I have the time) a paste web app
written in Guile that can be compared to pb.
Long text, short nonsense: One of many features I'd welcome is the ability
to pipe and paste data to the paste server.

Another useful thing: Be able to delete pastes. I've asked one of the pb
developers a long time ago and they told me that pb just keeps collecting
and you have to manually delete content in the db (or something like that),
no ability to delete pastes for an admin was implemented.

> 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
> 
> 

-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-12-15  9:13 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
2017-12-15  7:52 ` tomas
2017-12-15  9:13 ` ng0 [this message]
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=20171215091337.ai62h5znigkhvvbb@abyayala \
    --to=ng0@n0.is \
    --cc=guile-user@gnu.org \
    --cc=help-guix@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).