Andy Duong

But `2.0.3` doesn't work with the new sassc 😢

Just an update we just figure out 1 work around way following https://github.com/asdf-vm/actions/issues/235#issuecomment-862358821 

Just an update, we could also remove the `if: steps.asdf-cache.outputs.cache-hit != 'true'` there, the `asdf-vm/actions/install@v1` could determine which plugin has been installed 

Our final solution so far ``` - name: Setup asdf uses: asdf-vm/actions/setup@v1 - name: Cache asdf uses: actions/cache@v2 with: path: | /home/runner/.asdf key: ${{ runner.os }}-asdf-${{ hashFiles('**/.tool-versions') }} restore-keys: |...

> I think you could close this @jthegedus, the cache action works well. > > ``` > steps: > - name: Checkout > uses: actions/checkout@v2 > > - name: Install...

It can works without the `if: steps.asdf-cache.outputs.cache-hit != 'true'` https://github.com/asdf-vm/actions/issues/445#issuecomment-1129738813

💯 👍 @ankitkalia1195 ❤️

On production, as default Rails is using `DATABASE_URL` format which is we can set the adapter in the URL, for example: `postgres://mdhxjqtgwtrcgu:xxx.compute-1.amazonaws.com:5432/yyy`

Hi @malparty, I'm not sure this is related to the https://github.com/nimblehq/rails-templates/issues/264 issue :D I didn't catch up with the Rails assets tooling for a while; before starting this improvement, are...

Also @malparty FYI we might improve the `asset pipeline` but for the rake task like `bin/rails i18n:js:export` it's still required all ENV 😂 because that is the Rails way FYI