konstantine-v / amber-library-webapp

Webapp that allows users to create libraries, share details, and create reviews on books they've read. Written using the Amber Crystal Framework

New Reads

Update

This project is archived, please refer to the GitLab repository for the most up-to-date version.

Info

This is a webapp written in Crystal and powered by the Amber Framework. This webapp acts as a library where users store their books and can write notes + reviews about said books.

Getting Started

These instructions will get a copy of this project running on your machine for development and testing purposes.

Please see deployment for notes on deploying the project in production.

Prerequisites

This project requires Crystal (installation guide).

Development

To start your Amber server:

1. Install dependencies with shards install
2. Build executables with shards build
3. Create and migrate your database with bin/amber db create migrate. Also see creating the database.
4. Start Amber server with bin/amber watch

Now you can visit http://localhost:3000/ from your browser.

Getting an error message you need help decoding? Check the Amber troubleshooting guide, post a tagged message on Stack Overflow, or visit Amber on Gitter.

Using Docker? Please check Amber Docker guides.

Tests

To run the test suite:

crystal spec

Contributing

1. Fork it ( https://github.com/materialfuture/amber-library-webapp/fork )
2. Create your feature branch ( git checkout -b my-new-feature )
3. Commit your changes ( git commit -am 'Add some feature' )
4. Push to the branch ( git push origin my-new-feature )
5. Create a new Pull Request

Contributors

• your-github-user Konstantine(MaterialFuture) - creator, maintainer

TODO

• Add more validation routes like /book/new
• Add roles to users via a roles table and foreign key assignment
• Further integrate relation of books to users and so forth

amber-library-webapp's Issues

Specs/Tests Should Be Updated

The specs are behind where the app is. This may deter people trying this app out.

For each new route created also create a spec. Simple, easy, and overall good practice. You think I would know better at this point since I have spec tests written for my other Crystal apps?