# .circlerc, $BASH\_ENV, $ENV

**URL:** <https://discuss.circleci.com/t/circlerc-bash-env-env/25011>\
**Category:** Build Environment\
**Created:** [September 10, 2018, 10:16pm UTC](https://discuss.circleci.com/t/circlerc-bash-env-env/25011 "2018-09-10T22:16:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\
**Post date:** [September 12, 2018, 9:58am UTC](https://discuss.circleci.com/t/circlerc-bash-env-env/25011/4 "2018-09-12T09:58:06Z")

</div>

If you can use the multi-line format of the run step, adding in another line doesn’t seem too onerous. You could even have a quick linter to ensure it is present in every step:

```
  - run:
      name: Save Docker image layer cache
      command: |
        sh /tmp/run-me.sh
        mkdir -p /caches
        docker save -o /caches/${CIRCLE_PROJECT_REPONAME}.tar ${CIRCLE_PROJECT_REPONAME}

```

Adding that `run-me.sh` manually doesn’t seem to harm readability too much?

---

_[View the full topic](https://discuss.circleci.com/t/circlerc-bash-env-env/25011)._