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
  • Continuous Deployment from Github Actions

Continuous Deployment from Github Actions

By default ShipClojure will run tests, linting & format checks in CI but automated deployment is not enabled by default.

Going to Production
Previous
Creating a docker private registry
Next