Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/gabrielcsapo/granary-server
🚫 npm / bower bundler
https://github.com/gabrielcsapo/granary-server
deprecated
Last synced: 9 days ago
JSON representation
🚫 npm / bower bundler
- Host: GitHub
- URL: https://github.com/gabrielcsapo/granary-server
- Owner: gabrielcsapo
- License: apache-2.0
- Created: 2016-04-20T00:49:30.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2017-11-02T05:59:33.000Z (about 7 years ago)
- Last Synced: 2025-01-20T04:13:07.983Z (11 days ago)
- Topics: deprecated
- Language: JavaScript
- Homepage:
- Size: 21.8 MB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
> DEPRECATED: THIS WILL NO LONGER BE UNDER DEVELOPMENT
# [granary-server](http://gabrielcsapo.github.io/granary-server/) [![Build Status](https://travis-ci.org/gabrielcsapo/granary-server.svg?branch=master)](https://travis-ci.org/gabrielcsapo/granary-server) [![Dependency Status](https://david-dm.org/gabrielcsapo/granary-server.svg)](https://david-dm.org/gabrielcsapo/granary-server) [![devDependency Status](https://david-dm.org/gabrielcsapo/granary-server/dev-status.svg)](https://david-dm.org/gabrielcsapo/granary-server#info=devDependencies)
> based on https://github.com/node-freight/freight-server
> forked and renamed due to lack of culpability in helping add functionality to freight
> hopefully will be able to merge upstream once features and bugs are fixed.# Screenshots
[screenshots](screenshot)
# Install
```
vagrant up;
vagrant ssh;
npm start;
```# Contributions
> all contributions are welcome and wanted
## Ways to contribute
- create an issue
- if the issue is UI related, please provide a screenshot
- if the issue is code related, please provide code sample that causes this issue (a curl command, etc)
- close an issue or code cleanup
- branch names should be named `fix-#{issue-number}` if they are fixing an issue
- branches that are aimed at code cleanup should be labeled `cleanup-{area-of-cleanup}`
- please run `npm test` and `grunt build` before issuing a PR