fossasia/susper-backbone

Name: susper-backbone

Owner: FOSSASIA

Description: Susper Backbone.js - Decentralised Search Engine https://fossasia.github.io/susper-backbone/

Forked from: yacy/yacy_webclient_bootstrap

Created: 2016-09-03 17:21:26.0

Updated: 2018-05-24 16:38:10.0

Pushed: 2017-02-09 18:53:33.0

Homepage:

Size: 682

Language: HTML

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

susper.com

Susper is a decentral Search Engine that uses the peer to peer system yacy and Apache Solr to crawl and index search results.

Build Status Codacy Badge Code Climate codecov Gitter

Communication

Our chat channel is on gitter here: https://gitter.im/fossasia/susper.com

Components and Technology

This is a search front-end for YaCy. Retrieval of search results using YaCys search API and display using AJAX technology.

Search results are displayed using AJAX-technology from a Solr server which is embedded into YaCy. All search results must be provided by a YaCy search server which includes a Solr with a specialized JSON result writer. When a search request is made in one of the search templates, a http request is made to YaCy. The response is done in JSON because that can much better be parsed than XML in JavaScript. To overcome the same orgin policy in JavaScript, the result is capsuled into a JSONP response. This enables you to run YaCy anywhere and to use the results from this server somewhere else, maybe in static web pages, even from a file system. We implemented a proper model view of search results using the MV*-Fra­me­work backbone.js.

Because the search results come right from a Solr instance using a specialized result writer, these templates can provide industry-strength search portals. This is an unique combination of Solr, JSON(P), flexible JavaScript presentation the beautiful YAML4 CSS Framework and the easiness of web index creation with YaCy.

There are standards for search request queries (i.e. SRU) and search request responses (i.e. opensearch). YaCy provides both! Actually these search templates send SRU requests to YaCy and the jsonp result writer in Solr (inside YaCy) returns a into-JSON transformed version of openseach. If you like, then you can also get search results from the same query url by replacing the “wt=yjson”-parameter by “wt=opensearch”.

These pages are made with the YAML4 CSS Framework and it will serve you very well for the creation of own search portals. Just use the template as provided in the git repository (see below: 'Clone This!') and create your own search portal.

Installation
How do I install on a Server

Please check out the documentation here.

How do I install on my local machine

Please check out the documentation here.

How do I install on Google Cloud

To install the system on Google Cloud please refer to the Google Cloud installation readme.

How do I install on AWS

To install the system on AWS please refer to the AWS installation readme.

How do I install on Digital Ocean

To install the system on Digital Ocean please refer to the Digital Ocean installation readme.

How do I deploy Web App Generator with Heroku

Please read how to deploy to Heroku here

Contributions, Bug Reports, Feature Requests

This is an Open Source project and we would be happy to see contributors who report bugs and file feature requests submitting pull requests as well. Please report issues here https://github.com/fossasia/susper.com/issues

Issue and Branch Policy

Before making a pull request, please file an issue. So, other developers have the chance to give feedback or discuss details. Match every pull request with an issue please and add the issue number in description e.g. like “Fixes #123”.

We have the following branches

LICENSE

The repository is licensed under Creative Commons Attribution 2.0 License (CC-BY 2.0).

Maintainers

The project is maintained by


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.