Unfortunately 4clojure is shutting down: https://twitter.com/borkdude/status/1412117420173561861
Original thread that explains why 4clojure is shutting down: https://groups.google.com/g/clojure/c/ZWmDEzvn-Js
Now that 4clojure is shutting down (thanks for all the year of hosting it!), perhaps it's time to consider some alternatives. - borkdude
@borkdude suggested this in his tweet:
Another alternative would be to port it to self-hosted CLJS or sci and host it on Github pages and use localstorage. No need to maintain a running JVM server somewhere that way. Perhaps with the option to download your solutions as an archive.
And so I made it, using the awesome sci and special thanks to 4bb from where I copied the problems edn.
Deployed at https://4clojure.oxal.org/
You can view the solutions from each individual page eg: https://4clojure.oxal.org/#/problem/102/solutions
The archive repo is available at: https://github.com/oxalorg/4clojure-solutions-archive/
The easiest way to start up a local server would be to install Babashka and run the dev script defined in bb.edn:
bb dev
Alternatively, you can carry out the instructions of the Babashka script manually:
npm install # only needed once
cp "public/index.template.html" "public/index.html"
npx shadow-cljs watch :my-build
If you are a fan of emacs and cider, then you can open up emacs and run
cider-jack-in-cljs. It will automatically start shadow-cljs in watch
mode.
shadow hosts the dev server at http://localhost:8000
You can deploy your own instance via GitHub Actions:
- Go to Settings -> Pages
- Choose Build and deployment -> Github Actions
- Upload your repository or trigger the build
- Ship a crude version
- Make it noice!
- use localstorage to store solutions
- easy navigation
- scrape problem difficulty (can perhaps also get ranks data?)
- better alerts (modals?)
- show user which problems they have solved
- import /export data of the user in a .edn file
- github actions auto deployment
- create a new section of problems "community powered questions"
- add new community problems directly via github
