jarcane/clojurice

An opinionated starter app for full-stack web applications in Clojure

clojurice's Issues

Build fails on Java 11

Because we're still on compojure-api 1.11, we have some dependencies that break on Java 11. More info on this here: https://www.deps.co/blog/how-to-upgrade-clojure-projects-to-use-java-11/#java-util-collection-toarray

so either compojure-api needs to be updated, or else somehow the necessary dependency updates need to be injected, but I'm not clear on how to do that with boot.

Refactor config to EDN files

The .cljc method creates security problems

Add app-state atom on frontend

CSS Preprocessor

Add support for one of: LESS/SCSS/SASS

build uberjar

Remove REPL connection from production build

While the potential benefits of this for live debugging are potentially worthwhile, it strikes me that this could also constitute a significant security risk if not properly configured and secured, and thus something a bit dangerous to leave in as a default.

Front-end cleanup and reorganization

The frontend code badly needs reorganized, and possibly a less ugly base template for navigation

Add API call example to frontend

Update to Flyway 6

Flyway now warns about version 5 not being tested on more recent Postgres versions.

Unfortunately, Flyway 6 has changed the configuration method, in such a way that I cannot seem to find how to express the new method in Clojure's Java interop.

For now, Flyway remains at 5.2.4 as a result, but in the future should likely be updated to ensure compatibility.

Create configuration file

environ supports a config file, and we are starting to have need of some common settings, especially if #3 gets implemented, but already the settings for REPL and web server ports need to be present to avoid a crash on production builds.

Add tests for both CLJ and CLJS

cljs-dev-tools/Dirac support

Add support for Dirac for smoother front-end dev

DB Component

Add preferably some kind of SQL support