practicalli / practicalli/clojure

Development environments and deps.edn projects

Open
#168 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

clojure cli
Dominant language
Makefile
Stars
117
Forks
36
PR merge metrics
No merged PRs in 30d

Description

Suggestions on how to run a deps.edn project for different environments (dev, test, pre-prod, production)

call to clj using normal shell methods
use CLJ_CONFIG to define different configurations
https://ask.clojure.org/index.php/8440/equivalent-of-leiningens-managed-dependencies-in-deps-edn
https://github.com/ajoberstar/ClojureTools/issues/1

deps.edn alias
one option is to create an alias that adds an :extra-paths and then load config via a resource
an alias can also set Java system properties
so those are two paths to have an alias add extra config
be careful that you're not putting sensitive values in your deps.edn
have a system property that point to a file (or env var) to read a sensitive value

https://direnv.net/
direnv is an extension for your shell. It augments existing shells with a new feature that can load and unload environment variables depending on the current directory.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the linked ask.clojure.org and ClojureTools discussions, along with the listed CLJ_CONFIG, deps.edn alias, system-property, and direnv approaches. Document practical guidance for dev, test, pre-production, and production environments, including how to keep sensitive values out of deps.edn; completion should leave a clear, actionable section for readers.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure, shell
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.