This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-22
Channels
- # announcements (2)
- # babashka (18)
- # beginners (87)
- # calva (22)
- # chlorine-clover (5)
- # cider (11)
- # clj-kondo (10)
- # clojure (71)
- # clojure-austin (1)
- # clojure-norway (6)
- # clojure-uk (13)
- # clojurescript (3)
- # core-async (10)
- # data-science (17)
- # datascript (1)
- # datomic (22)
- # emacs (10)
- # fulcro (32)
- # hoplon (8)
- # jobs-discuss (2)
- # malli (5)
- # meander (5)
- # nrepl (35)
- # off-topic (8)
- # pathom (38)
- # planck (21)
- # re-frame (10)
- # reagent (17)
- # reitit (7)
- # shadow-cljs (26)
- # tools-deps (3)
- # xtdb (7)
I am putting a clojure backend on my own server, what workflow would you suggest for deployment? I want something close to heroku workflow in terms of convenience, and also want to be able to run it locally in an environment closest to the server. Have only worked with heroku before, and have trouble googling this stuff.
I know that, I want to use my own server.
http://dokku.viewdocs.io/dokku/ The smallest PaaS implementation you've ever seen
I have seen it, but how do I reproduce the environment locally?
you uberjar your project and sftp it to the server when you deploy or push the most up to date version to a hosted git repo (hub/lab/etc) and build on your server
you'll probably need a few small shell scripts to manage database migrations and so on.
Docker is not the worst if you want the same env locally and in production.