Mirror of Vervis, a federated forge server
Find a file
2016-04-26 05:58:05 +00:00
app Put all modules under a new Vervis module 2016-02-23 08:45:03 +00:00
config Dummy git upload-pack request POST handler 2016-04-23 18:33:41 +00:00
src Git upload-pack request handler, parses it but returns nothing 2016-04-26 05:58:05 +00:00
src-old/Vervis Make initial homepage with table and simple login 2016-02-16 11:41:13 +00:00
templates Remove copyright field from settings, copyright is wrong! 2016-04-19 15:47:26 +00:00
test Bring Yesod scaffolding 2016-02-13 03:35:30 +00:00
.ghci Bring Yesod scaffolding 2016-02-13 03:35:30 +00:00
_boring Change SSH host key default filenames 2016-03-07 00:37:07 +00:00
AUTHORS Initial record with empty package that builds 2016-01-28 14:15:54 +00:00
ChangeLog Initial record with empty package that builds 2016-01-28 14:15:54 +00:00
COPYING Initial record with empty package that builds 2016-01-28 14:15:54 +00:00
INSTALL.md Change SSH host key default filenames 2016-03-07 00:37:07 +00:00
NEWS.md No trailing zero components in version number 2016-04-12 15:19:02 +00:00
README.md Update feature status list in readme 2016-04-18 18:57:34 +00:00
stack.yaml Smart HTTP ref discovery 2016-04-22 19:46:46 +00:00
vervis.cabal Binary request body decoder 2016-04-24 18:48:07 +00:00

Vervis

Vervis is a project hosting and management application, with a focus on softare projects and decentralization. It's still in very early development. At the time of writing, it is a minimal web application in which you can create Git repositories and watch their commit logs.

Vervis is free software, and is committed to software freedom and to freedom in general. It is released to the public domain using the CC0 Public Domain Dedication. For the boring "legal" details, see the file COPYING. Please use and reuse Vervis for a Good purpose, and share your work too in the same spirit.

Features

[ ] - To do
[~] - Work in progress
[/] - Initial coding done, needs tests and polishing
[x] - Complete

[ ] User management
  [~] View your personal overview
  [~] Other users' pages
  [/] Register
  [ ] Delete account
  [/] Log in
  [/] Log out
  [ ] Reset password
  [ ] TLS client cert
    [ ] Upload it
    [ ] View it
    [ ] Log in using it
  [ ] Change profile details
  [ ] Key management
    [/] Add key
    [ ] Delete key
    [/] View keys
[ ] Project management
  [ ] Tickets
  [ ] Wiki
  [ ] Kanban
  [ ] Merge requests
[ ] Repo management
  [ ] Delete repo
  [/] Add repo
  [ ] Rename repo
  [ ] Edit repo settings
  [ ] View repo content
    [/] File tree
    [ ] File content
      [/] Plain text
      [/] Syntax highlighting
      [/] Document rendering
      [ ] Images
      [ ] Audio
      [ ] Video
      [ ] Raw file download
[ ] Git network access
  [ ] SSH push
  [~] SSH pull
  [ ] git://
  [ ] HTTP(S) push
  [ ] HTTPS(S) pull
[ ] Federation

Installation

See INSTALL.md. To be honest, I haven't written it yet. Just use stack install, pray, and ask me if anything fails. Ah, actually before that you need to create a PostgreSQL database, generate an SSH key and update the settings in config/settings.yml as needed. I promise to write detailed instructions soon.

Using

See the .cabal file for more info and link to project website and version control.

The official download location is the Darcs repository:

http://hub.darcs.net/fr33domlover/vervis

Releases are made to Hackage, the Haskell package repository. See http://hackage.haskell.org/package/vervis.

See the file INSTALL.md for a detailed usage and deployment guide. The file ChangeLog explains how to see the history log of the changes done in the code. NEWS.md provides a friendly overview of the changes for each release.

Reporting Bugs and Suggesting Features

If you found a bug, or you have an idea, a feature request or a wishlist item, open a ticket for it! Even if you're goint to implement something or try to solve it.

http://rel4tion.org/projects/vervis/tickets/

If you're going to implement some feature or fix some bug you found, start by opening a ticket so that other people will know which features are being developed and who does what.