Pastebin service

[ShalokShalom]

• Gitea version (or commit ref): all
• Git version: all
• Operating system: all
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant

Description

I am used to Gist, the pastebin service, since it offers me the option to collect all my pasted code in one central place and that in the same interface, text editor and so on, which i use on Github, so all is very consistent.

I suggest to implement such a service for Gitea too, as Gitlab does it with their snippets.

This is something we all use, it provides users and developers the very same look and feel as in Gitea, is easy to implement (so far i as a newbie can see) and offer us a history of all the already posted code.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[laplix]

👍 for this one and I would suggest to name this feature cups,, as in cups of tea....

[pgaskin]

@laplix That might be a bit confusing with the Common Unix Printing Service. Also +1 as well.

[ShalokShalom]

cup? cupi? Or simply Pastebin?

[tboerger]

Or just snippets, I know it's not a fancy name ;)

[bkcsoft]

I still (see gogs issue) think this should be an external service. We could however make it injectable into Gitea 🙂

[ShalokShalom]

Optional features:

) Comment section
) Revisions (History)
) Syntax Highlighting, which is not even available in Gist
) Filter and sorting

A lot of +1 and many separately created issue reports about this proposal show a clear picture:

gogs/gogs#936

[bkcsoft]

on the other hand, it should be fairly simple to implement snippets.

Keep a hidden repo called _snippets (or similar), each snippet is a folder, a folder (or snippet) can contain multiple files. Done :)

[andreynering]

@bkcsoft On GitHub, each snippet is a Git repo (but can contain many files). But we can make it different.

I don't know if it should be part of Gitea or a separated project. If in Gitea, it would be easier to reuse code.

Anyway we should keep in mind that many people (me included) dislike the GitHub UI for Gists. I think we can do it better. There should be categories or tags to organize gists. It should be easy to find and search for existing Gists.

[bkcsoft]

Containing all snippets in one repo:

Pros:

• Easy to import/sync with your editor
• Fairly easy to implement (think copy-paste wiki-code)

Cons:

• Might get slow if you use snippets a lot
• Hard to remove a snippet completely (rewrite history, never nice)

---

Gist UI sucks indeed... much to be improved, just feels hacked together...

IMO we should contain everything regarding snippets to said repo (if a single one, otherwise I'm all down for submodules or whatever to keep track of them...), this includes categories (folders anyone? ) and tags

Having that as a file in the repo makes it easy to sync that to your editor as well, and makes it fairly simple to do searches 🙂

[ShalokShalom]

@andreynering I thought about tags as well, think this a good idea.
Maybe put these tags/categorys on the left side
So its easy to create and find specific pastebins:

[ShalokShalom]

May be a nice candidate to fork and adjust: https://github.com/defunkt/gist

[joubertredrat]

Or this, https://github.com/gmarik/Gistie