Skip to content
master
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
dev
 
 
doc
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

ventas

Build Status Clojars Project License

ventas is a WIP ecommerce platform written entirely in Clojure.

For any questions I'm usually available at the #ventas channel in clojurians. You can also open an issue, or contact me by email (you'll find it in project.clj) .

Documentation

Demo instance and source for the demo instance

Motivation

No open source ecommerce project satisfies me. I've been working with most of them for years and I think they suck. I won't name any, but this is roughly what I think about the available solutions:

  • They tend to be difficult to extend or modify. They try to tackle the problem with extension systems, but in the end you need to modify the code of the core to do meaningful changes. This forces you to choose between never updating the software or making an exceptional effort to keep your changes applied. This is why one of the main design decisions for this project is to make it very easy to extend and modify.

  • They tend to be difficult to reason about. Because they are built upon a fundamentally mutable model, it's impossible to know how did the database get to the current state. In the best case, something bad happens and I don't know why. In the worst case, something bad happens and I don't even notice (until it's too late). Having mutable objects everywhere doesn't help either.

  • They tend to have poor performance out of the box. Of course everything can be made performant, but I shouldn't need to make the effort. Particularly when "effort" means rewriting SQL queries, or wasting several days trying to find out what's causing my store to take 20 seconds to load.

  • They tend to be over-engineered, or having user-hostile "features". This is a problem in a lot of software, but it's there nonetheless.

Note that these points don't mean that ventas does not or will not commit the same sins. I just try not to.

Getting started

At the moment, ventas is unfit for its purpose. However, if you are a developer and just want to see the project in action, read on.

You need to have git and leiningen installed. You also need access to a Datomic database and an Elasticsearch instance. (See Setting up a local environment with docker-compose if you feel comfortable with Docker)

First clone the project and cd into it:

$ git clone https://github.com/JoelSanchez/ventas
$ cd ventas

Now you can start the REPL:

$ lein repl

When the REPL is ready, execute init:

user=> (init)
:reloading (ventas.common.utils ventas.utils ventas.config ventas.database ventas.database.schema ventas.database.entity ventas.entities.product-variation ventas.database.generators ventas.entities.i18n ventas.entities.brand ventas.plugin ventas.database.seed ventas.entity-test ventas.events repl ventas.entities.image-size ventas.paths ventas.entities.file ventas.server.ws ventas.logging ventas.server ventas.server-test ventas.auth ventas.entities.user ventas.test-tools ventas.database-test ventas.entities.product-taxonomy ventas.server.pagination ventas.utils.images ventas.server.api ventas.entities.configuration ventas.entities.address ventas.entities.product-term client ventas.plugins.featured-categories.core ventas.plugins.slider.core ventas.entities.order-line ventas.entities.order ventas.common.utils-test ventas.entities.resource ventas.entities.category ventas.entities.product ventas.entities.country ventas.entities.tax ventas.entities.state ventas.plugins.blog.core ventas.plugins.featured-products.core user)
INFO [ventas.database:27] - Starting database, URL: datomic:dev://localhost:4334/ventas
INFO [ventas.server:99] - Starting server
INFO [ventas.server:102] - Starting server on 0.0.0.0:3450
INFO [client:28] - Starting Figwheel
Figwheel: Starting server at http://0.0.0.0:3449
Figwheel: Watching build - app
Compiling "resources/public/files/js/compiled/ventas.js" from ["src/cljs" "src/cljc" "test/cljs" "test/cljc"]...
Successfully compiled "resources/public/files/js/compiled/ventas.js" in 8.252 seconds.
Figwheel: Starting CSS Watcher for paths  ["resources/public/files/css"]
INFO [client:42] - Starting SASS
:done

Then, execute the setup! function, which will migrate the database, install fixtures, etc.:

(ventas.core/setup!)

Now you can open localhost:3450/admin to see the administration. A frontoffice is not included, but you can check out ventas-demo for an example.

To enter the backoffice you'll need to create an admin user for yourself:

(entity/create :user {:first-name "Admin"
                      :email "your@email.com"
                      :password "yourpassword"}

To do frontend development in the backoffice:

lein sass4clj auto
shadow-cljs watch :admin

You can connect to the nREPL server created by shadow-cljs to get a CLJS RPEL:

lein repl :connect localhost:4002
user=> (shadow.cljs.devtools.api/nrepl-select :admin)

Setting up a local environment with Docker Compose

A docker-compose.yaml file is included:

docker-compose up -d

Overview

Backend

  • Written in Clojure.

  • Uses mount and really likes REPL-driven development. Code reload is done by calling repl/r . App initialization is done by calling repl/init.

    ;; (r) reloads changed namespaces, restarts defstates within them, and optionally
    ;; restarts given defstates as keywords
    (r :db)
    INFO [ventas.database:34] - Stopping database
    :reloading ()
    INFO [ventas.database:27] - Starting database, URL: datomic:dev://localhost:4334/ventas
    => :done
  • The database is Datomic. A custom database entity system, which relies on core.spec, abstracts the database and allows easy testing and generation of sample data.

    ;; recreates the database, applies the schema, creates the fixtures and seeds the database with randomly generated entities
    (seed/seed :recreate? true :generate? true)

    Lots of utility functions make exploring the database and getting data from it more interactive and fast.

     ;; returns a list of active users
    (entity/query :user {:status :user.status/active})
    ;; returns an entity by EID
    (entity/find 17592186045760)
    ;; creates an user and returns the result
    (entity/create :user {:email "test@email"
                          :first-name "Test"
                          :last-name "User"})
    ;; generates three users
    (entity/generate :user 3)
    ;; updates an user's company
    (entity/update {:id 17592186045920
                    :company "Test"})

    Adding new entities is easy and schema additions are handled behind the curtains (search for calls to entity/register-type! to know more)

  • The HTTP server is http-kit. Routing is handled by Compojure, but they are just 4 handlers, because the actual communication happens over websockets, with the help of chord.

    (register-endpoint!
      :products/get
      (fn [{:keys [params]} state]
        (entity/serialize (entity/find (:id params)))))
  • Authentication is done with JWT tokens (provided by buddy).

Frontend

  • Written in ClojureScript, and uses re-frame.

  • Development is done with shadow-cljs.

  • Communication with the server is done using a re-frame effect that abstracts websocket requests. All requests and responses are logged to the verbose level of the JS console, so you can see what's going on.

  • Client-side routing is handled by bidi, but a custom wrapper exists for it, which makes things much easier to deal with.

    (routes/define-route!
     :frontend.product ;; this route is nested inside the :frontend route
     {:name (i18n ::the-name-of-this-page)
      :url ["product/" :id]
      :component a-re-frame-component-for-this-route})
  • Stylesheets are written in SCSS. The watcher is also handled by the server's REPL.

  • i18n is done with tongue

  • Semantic UI components.

Contributing

I'd appreciate help in any part of the project.

Please read CONTRIBUTING.md

You can’t perform that action at this time.