Skip to content

sapkalsachin096/openlibrary

 
 

Repository files navigation

Open Library

Build Status Join the chat at https://gitter.im/theopenlibrary/Lobby

Open Library is an open, editable library catalog, building towards a web page for every book ever published.

Table of Contents

Overview

Open Library is an effort started in 2006 to create "one web page for every book ever published". It provides access to many public domain and out-of-print books, which can be read online.

Installation

Docker

We're supporting Docker, moving forward. If you are a new contributor, especially on linux, please consider setting up using the Docker Instructions.

Open Library Docker Tutorial

Our Docker environment is in active development. Want to contribute? Here's our top-level Docker todo-list and a list of open Docker issues.

Developer's Guide

For instructions on administrating your Open Library instance and build instructions for developers, refer the Developer's Quickstart Guide.

You can also find more information regarding Developer Documentation for Open Library in the Open Library Wiki

Code Organization

  • openlibrary/core - core openlibrary functionality, imported and used by www
  • openlibrary/plugins - other models, controllers, and view helpers
  • openlibrary/views - views for rendering web pages
  • openlibrary/templates - all the templates used in the website
  • openlibrary/macros - macros are like templates, but can be called from wikitext

Architecture

The Backend

OpenLibrary is developed on top of the Infogami wiki system, which is itself built on top of the web.py Python web framework and the Infobase database framework.

Once you've read the overview of OpenLibrary Backend technologies, it's highly encouraged you read the developer primer which explains how to use Infogami (and its database, Infobase):

Running tests

Open Library tests can be run using pytest. Kindly look up on our Testing Document for more details

Run tests while the docker container is running

cd docker/
docker-compose exec web make test

Integration Tests

Integration tests use the Splinter webdriver with Google Chrome. For instructions on installation requirements and running integration tests, see Integration Tests README

About

One webpage for every book ever published!

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 66.3%
  • HTML 19.7%
  • JavaScript 7.2%
  • CSS 6.2%
  • Shell 0.4%
  • Makefile 0.1%
  • Other 0.1%