Granite
ORM Model with Adapters for mysql, pg, sqlite in the Crystal Language.
Install / Use
/learn @amberframework/GraniteREADME
Granite
Amber is a web framework written in the Crystal language.
This project is to provide an ORM in Crystal.
Looking for maintainers
Granite is looking for volunteers to take over maintainership of the repository, reviewing and merging pull requests, stewarding updates to follow along with Crystal language updates, etc. More information here
Documentation
Contributing
- Fork it ( https://github.com/amberframework/granite/fork )
- Create your feature branch (git checkout -b my-new-feature)
- Commit your changes (git commit -am 'Add some feature')
- Push to the branch (git push origin my-new-feature)
- Create a new Pull Request
Running tests
Granite uses Crystal's built in test framework. The tests can be run either within a dockerized testing environment or locally.
The test suite depends on access to a PostgreSQL, MySQL, and SQLite database to ensure the adapters work as intended.
Docker setup
There is a self-contained testing environment provided via the docker-compose.yml file in this repository.
We are testing against multiple databases so you have to specify which docker-compose file you would like to use.
- You can find postgres versions at https://hub.docker.com/_/postgres/
- You can find mysql versions at https://hub.docker.com/_/mysql/
After you have docker installed do the following to run tests:
Environment variable setup
Option 1
Export .env with $ source ./export.sh or $ source .env.
Option 2
Modify the .env file that docker-compose loads by default. The .env file can either be copied to the same directory as the docker-compose.{database_type}.yml files or passed as an option to the docker-compose commands --env-file ./foo/.env.
First run
Replace "{database_type}" with "mysql" or "pg" or "sqlite".
$ docker-compose -f docker/docker-compose.{database_type}.yml build spec
$ docker-compose -f docker/docker-compose.{database_type}.yml run spec
Subsequent runs
$ docker-compose -f docker/docker-compose.{database_type}.yml run spec
Cleanup
If you're done testing and you'd like to shut down and clean up the docker dependences run the following:
$ docker-compose -f docker/docker-compose.{database_type}.yml down
Run all
To run the specs for each database adapter use ./spec/run_all_specs.sh. This will build and run each adapter, then cleanup after itself.
Local setup
If you'd like to test without docker you can do so by following the instructions below:
- Install dependencies with
$ shards install - Update .env to use appropriate ENV variables, or create appropriate databases.
- Setup databases:
PostgreSQL
CREATE USER granite WITH PASSWORD 'password';
CREATE DATABASE granite_db;
GRANT ALL PRIVILEGES ON DATABASE granite_db TO granite;
MySQL
CREATE USER 'granite'@'localhost' IDENTIFIED BY 'password';
CREATE DATABASE granite_db;
GRANT ALL PRIVILEGES ON granite_db.* TO 'granite'@'localhost' WITH GRANT OPTION;
- Export
.envwith$ source ./export.shor$ source .env. $ crystal spec
Related Skills
oracle
338.7kBest practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
prose
338.7kOpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
Command Development
83.6kThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
Plugin Structure
83.6kThis skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
