Your new project at http://localhost:3000
Username: [email protected]
Password: admin
- Run
lein joplin migrate sql-dev-env
in the newly created project (This will add an admin user with username: [email protected] and password: admin to a new database) - Run
lein cljx once
to compile the cljx files - Run
lein repl
and then(start-dev-system)
to run the application in dev mode. This will also compile the clojurescript. - Run
lein rel-jar
to generate a runnable jar file.
- closp-crud integration
- H2 database on filesystem as a default
- Joplin for database migrations
- Selmer as templating solution
- http-kit as a server
- cljx support
- Figwheel with clojurescript live reloading
- Reloading support for templates and clojure code
- Configuration with nomad
- User management with login/logout/registration with email activation (provided by postal)
- Authentication provided by buddy
- reagent and datascript on frontend side
- Ring Antiforgery middleware
- Clojure miniprofiler example
- Componentized application
- Datascript with reagent example
- Booststrap css styles
There is a dockerfile attached which will fetch the latest version and run an example project.
There is a closp.edn file in the resources folder which should be adapted accordingly.
Closp uses nomad https://github.com/james-henderson/nomad, so you can configure everything as you can do with nomad.
When you start your project from the repl it will load the default closp.edn
from resources
folder, which fits
for development.
For a different config in another environment you can pass in a file path via system environment setting like so:
java -jar -Dclosp-config-path=C:\\path\\to\\iwf-prod.edn closp.jar
.
Please think of changing the :env key in the config to :prod instead of :dev when changing to a different
environment.
This is a module that generates html, routing and sql files for a given table definition. For more information please look here: https://github.com/sveri/closp.
Closp per default is configured to connect to a file H2 database.
Additionally I added support for joplin https://github.com/juxt/joplin to handle migration of sql scripts.
To get started run lein joplin migrate sql-dev-env
in the project folder. This is enough to get running.
Changing the jdbc url in the closp.edn file will switch to another database. But keep in mind you will have to
run the migration step again and change the jdbc url in the project.clj too.
The connection is handled by jdbc https://github.com/clojure/java.jdbc so everything that jdbc supports is supported
by closp out of the box.
Closp comes with korma https://github.com/korma/Korma for an abstraction layer over jdbc. See db\users.clj
for
how it is used.
We use the buddy (https://github.com/funcool/buddy) library for this.
Configuration is done in ns.service.auth
There is a concept of roles, admin and none are alreaded provided, you can add more in the auth namespace.
Or, create a database storage for this.
Next you can find a rules def in the auth namespace which defines the access rules for every available link. For
more information please look at the buddy documentation.
Closp ships with selmer https://github.com/yogthos/Selmer (django inspired) templating solution.
There is a signup workflow implemented that sends out an email after regristration with a link to activate the account. Until the account is activated the user won't be able to login.
The signup form is protected by recaptcha. To make it work:
- add your public key to signup.html
- Add your private key and domain to routes/user.clj#connectReCaptch
Closp ships with an administrator interface (/admin/users) to activate / deactivate users and set roles accordingly. There is also an option to add new users.
In dev mode changes the clojure code will be recompiled and reloaded on page refresh. The same is true for the templates. Theoretically this results development without server restarts.
Closp will automatically compile cljx https://github.com/lynaghk/cljx files in the cljx
folder and add them to
the clj / cljs classpath.
When running in dev mode cljs files will be auto compiled and sent to the browser via figwheel https://github.com/bhauman/lein-figwheel
Closp uses postal https://github.com/drewr/postal for sending authentication links. This can be configured in closp.edn.
Closp comes with some predefined components https://github.com/danielsz/system
- Handler component
- Configuration component
- Database component
- Webserver component
To restart the components just hit (reset)
in the running repl.
https://github.com/weavejester/ring-anti-forgery is enabled per default for every shipped form. If you use ajax post / put / ... calls you need to provide a :X-CSRF-Token in the header. With cljs-ajax for example it would look like this:
(ajax/ajax-request
{:uri url
:method method
:params content
:headers {:X-CSRF-Token (get-value "glob_anti_forgery")}})
Closp includes a reagent https://github.com/reagent-project/reagent and datascript https://github.com/tonsky/datascript example taken from https://gist.github.com/allgress/11348685 to get started with frontend development.
To use it call (layout/flash-result "success message" "alert-success") and on the next page load a div will appear with the success message on top of the page.
There is a leiningen task defined in the project.clj to generate an uberjar. Just execute lein uberjar
.
By default this will include your closp.edn config file in the build from resources folder. You should at least change
the :env entry to :prod or something else than :dev.
There are several ways to setup a more separated dev / staging / prod environment. Please lookup nomad for that.
- Miniprofiler https://github.com/yeller/clojure-miniprofiler example in
routes\user.clj -> admin-page function
. The profiler is enabled in development only - Namspace support: Add
-n name.space
option tolein new closp projectname
to provide a namespace for the source files. - Self registration can be turned on or off in the closp.edn file in the resources folder.
- CRUD plugin to generate frontend to database CRUD for entities
- Whatever seems useful in the future.
I get this warning: Uncaught Error: Invariant Violation: _registerComponent(...): Target container is not a DOM element.
This will happen only in dev mode for every page where you did not explicitly register your clojurescript with.
Look at dev.cljs for this line :jsload-callback (fn [] (core/main))
and change the call to (core/main)
how you
need it for the page you are working on right now.
Copyright © 2015 Sven Richter
Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.