Thanks for the heads up; that must have slipped by. The two blocks are functionally equivalent in any case.

Just updated the tutorial.

Great, thanks!

Check the :biff.tasks/server setting in config.edn. Looks like it's currently set to

I forgot to mention that, it is also (already) correctly set to my custom domain.

hm, that's interesting

Could you paste the whole :tasks section of config.edn?

feel free to redact e.g. domain if you prefer

Also what's your biff version in tasks/deps.edn?

:tasks {;; Set this if the auto-detection doesn't work
         ;; Possible values: macos-x64, macos-arm64, linux-x64, linux-arm64
         :biff.tasks/tailwind-build nil
         :biff.tasks/clj-args ["-J-XX:-OmitStackTraceInFastThrow"
                               "-J-XX:+CrashOnOutOfMemoryError"
                               "-J-Duser.timezone=UTC"
                               "-M" "-m" "com.eelchat"
                               "--port" "7888"
                               "--middleware" "[cider.nrepl/cider-middleware,refactor-nrepl.middleware/wrap-refactor]"]
         :biff.tasks/on-soft-deploy "\"(com.eelchat/on-save @com.eelchat/system)\""
         ;; Replace "master" with e.g. "main:master" or "dev:master" if you
         ;; want to deploy a different branch, for example:
         ;:biff.tasks/deploy-cmd ["git" "push" "prod" "main:master"]
         :biff.tasks/deploy-cmd ["git" "push" "prod" "master"]
         :biff.tasks/server ""}}

This is the implementation of bb deploy for current version of biff: https://github.com/jacobobryant/biff/blob/master/tasks/src/com/biffweb/tasks.clj#L192. If :biff.tasks/server is set correctly, I wonder if there's an issue with :biff.tasks/deploy-cmd or :biff.tasks/{deploy-to,deploy-from} . Actually since your error message includes the term "repository" it seems like it probably is an issue with the git command... That config section looks fine; I wonder if the url for the git remote is set to . Looking up the command to check that now...

does git remote show prod look correct? For one of my apps it looks like this:

$ git remote show prod
* remote prod
  Fetch URL: 
  Push  URL: 
  HEAD branch: master
  Remote branch:
    master tracked
  Local ref configured for 'git push':
    master pushes to master (fast-forwardable)

it should look the same for you, with being replaced by your domain

Actually git remote -v would be a better command to run

I get this:

$ git remote -v
origin  [email protected]:jacobobryant/yakread.git (fetch)
origin  [email protected]:jacobobryant/yakread.git (push)
prod     (fetch)
prod     (push)

My bad, I must have copied

$ git remote add prod 

No problem! It's an easy mistake to make 🙂

I have a few more issues - is it o.k. to add them in this thread? Recaptcha fails after adding the keys to secrets.env

export POSTMARK_API_KEY=af1ee...
export RECAPTCHA_SECRET_KEY=LcDHJ...

$ bb logs
...
Jun 14 17:39:18 mhrdd-dev sh[3906]: [qtp2017659546-19] INFO com.biffweb.impl.middleware - 771ms 303 post /auth/send-link
Jun 14 17:39:18 mhrdd-dev sh[3906]: [qtp2017659546-23] INFO com.biffweb.impl.middleware -  13ms 200 get  /?error=recaptcha
Jun 14 17:41:08 mhrdd-dev sh[3906]: [qtp2017659546-18] INFO com.biffweb.impl.middleware -   0ms 405 post /
Jun 14 17:41:08 mhrdd-dev sh[3906]: [qtp2017659546-20] INFO com.biffweb.impl.middleware -   1ms 404 get  /.env

$ bb logs
...
Jun 14 17:28:48 mhrdd-dev sh[3408]: [qtp1500545021-20] INFO com.biffweb.impl.middleware - 154ms 303 post /auth/send-link
Jun 14 17:28:48 mhrdd-dev sh[3408]: [qtp1500545021-16] INFO com.biffweb.impl.middleware -   8ms 200 get  /[email protected]

> I have a few more issues - is it o.k. to add them in this thread? Sure thing 🙂 After you update secrets.env, have you restarted the app (`bb restart`)? You'll need to do that for environment variables to take effect. Same for updating config.edn, though in that case a bb refresh also works and is a bit faster (i.e. restart the application code, but leave the JVM running). I would be surprised for adding the keys directly to config.edn to not trigger an error--biff will only use those keys as names of environment variables... actually I see that in that case, Biff will bypass the recaptcha check altogether (https://github.com/jacobobryant/biff/blob/master/src/com/biffweb/impl/auth.clj#L17). In any case, I would switch the values in config.edn back to be the environment variable names and try to fix the recaptcha error first, then we can see if email sending is still not working. For debugging recaptcha, you could make a dummy endpoint that does the recaptcha test, and see what parameters + output you're getting:

(defn debug-recaptcha [{:keys [biff/secret params]}]
  (prn (:g-recaptcha-response params))
  (prn (secret :recaptcha/secret-key))
  (prn (:body (http/post ""
                         {:form-params {:secret (secret :recaptcha/secret-key)
                                        :response (:g-recaptcha-response params)}
                          :as :json})))
  [:div "ok"])

(def plugin
  {:routes [["/debug-recaptcha" {:post debug-recaptcha}]
            ...]})

For debugging the email sending, the auth plugin calls whatever function you have set at :biff/send-email (see https://github.com/jacobobryant/biff/blob/master/src/com/biffweb/impl/auth.clj#L65), which by default is in the email.clj file in your project: https://github.com/jacobobryant/biff/blob/master/example/src/com/example/email.clj#L82. So you can put some print statements in there to see what's going on.

The event log inside of Postmark/whatever email provider you're using is also handy for checking to see if an email got sent.

If the input parameters for the recaptcha http call look correct, it might be that you haven't added your domain to recaptcha's whitelist. You can go to the recaptcha admin console (https://www.google.com/recaptcha/admin) -> settings page to check that.