ShipClojure
  • Getting Started

    • ShipClojure Stack
    • Getting started
    • Troubleshooting
    • Managing Secrets
    • REPL Workflow
    • Code structure
    • Getting Updates
  • Tutorials

    • Observability guide
    • Privacy policy with GPT
  • Backend

    • Role-Based Access Control (RBAC)
    • Payments
    • Using integrant components in handlers
    • Organisations
    • Logging
    • Command Query Responsability Segregation (CQRS)
    • Ring API
    • Oauth2 Auth (Google Login)
  • Frontend

    • Frontend Navigation with Custom Actons
    • Static pages with Pizzazz
    • Writing UI Pages
    • Toast Notifications
    • Authentication
    • Frontend Release
    • Icons
    • Content Management (SEO Pages)
  • Deployment

    • Docker Build Guide
    • Going to Production
    • Continuous Deployment from Github Actions
    • Creating a docker private registry
  • Documentation
  • Datom
  • ShipClojure Stack
On this page
  • Frontend
  • Backend
  • Common

ShipClojure Stack

Here are the main libraries used by shipclojure:

Frontend

The frontend uses:

  • ClojureScript - Duuh
  • replicant - Frontend Rendering
  • nexus - data driven action dispatch
  • datascript - Datalog on the frontend
  • tailwindcss - utility CSS classes for scale
  • daisyUI - component system for tailwind

Backend

On the backend we use:

  • Clojure - Ofcourse
  • Datomic - Immutable Storage
  • Ring - Web handling & middleware
  • Reitit - Request Routing
  • Integrant - Lifecycle & Dependency Management for Components

Common

These libraries are used for both frontend & backend:

  • Malli - Data-driven schema management
  • Telemere - Logging provider
Multi-Instance Development
Previous
Getting started
Next