You can redeploy many times. The only problem is that when you'll deploy without postgres and create a database then you'll have a new database as the old one will remain on the droplet itself but won't be used.

You can create postgres in the cloud and then connect from local bb dev too. It will work the same as in production. Then you'll know that it will work the same after deployment.

definitely make sure it's working in dev before you bother with deploying

basically just start a new project, make sure it works, then add postmark and recaptcha config to config.edn, then hit ctrl-c on the app and run bb dev again, then see if that works

set POSTMARK_API_KEY only in secrets.env, right? Line https://github.com/jacobobryant/biff/blob/b730c8524fa113832865b6f41312dd87a514465f/example/config.edn.TEMPLATE#L16 doesn’t have the ; Leave this as-is, and update secrets.env comment like line https://github.com/jacobobryant/biff/blob/b730c8524fa113832865b6f41312dd87a514465f/example/config.edn.TEMPLATE#L9C53-L9C95 does. Just checking. That’s how I configured it last time.

correct

Just like yesterday, bb dev works fine out of the box. Again, yesterday I deployed without changing anything.

I’m configuring reCaptcha and Postmark now.

Ok. With…

secrets.env
   set POSTMARK_API_KEY
   set RECAPTCHA_SECRET_KEY

config.edn
   set :postmark/from (to match Postmark sender signature)
   set :recaptcha/site-key

% bb dev                                                       

Rebuilding...

Done in 395ms.
[main] INFO life - starting: com.biffweb$use_config@5de1b3ee
[main] INFO life - starting: com.biffweb$use_secrets@31e6ac68
[main] INFO life - starting: com.biffweb$use_xt@6b8eec09
[main] INFO xtdb.tx - Started tx-ingester
[main] INFO com.biffweb.impl.xtdb - Indexed #:xtdb.api{:tx-time #inst "2023-09-19T14:58:38.444-00:00", :tx-id 7}
[main] INFO life - starting: com.biffweb$use_queues@f24af6f
[main] INFO life - starting: com.biffweb$use_tx_listener@7194cf53
[main] INFO life - starting: com.biffweb$use_jetty@3a4b7322
[main] INFO org.eclipse.jetty.server.Server - jetty-10.0.7; built: 2021-10-06T19:34:02.766Z; git: da8a4553af9dd84080931fa0f8c678cd2d60f3d9; jvm 20.0.2.1+10-FR
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@4b6bdffe{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.AbstractConnector - Started ServerConnector@466ea2b0{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
[main] INFO org.eclipse.jetty.server.Server - Started Server@2d8554ff{STARTING}[10.0.7,sto=0] @23908ms
[main] INFO com.biffweb.impl.misc - Jetty running on 
[main] INFO life - starting: com.biffweb$use_chime@16c2ec2a
[main] INFO life - starting: com.biffweb$use_beholder@43508da7
[chime-1] INFO life.worker - There are 2 users.
[main] INFO life - System started.
[main] INFO life - Go to 
nREPL server started on port 7888 on host localhost - 
[qtp1285414362-41] INFO com.biffweb.impl.middleware -  34ms 101 get  /app/chat
[qtp1285414362-37] INFO com.biffweb.impl.middleware -  30ms 303 post /auth/signout
[qtp1285414362-39] INFO com.biffweb.impl.middleware -  14ms 200 get  /
[qtp1285414362-35] INFO com.biffweb.impl.middleware -  20ms 200 get  /js/main.js?t=1695129134913
[qtp1285414362-42] INFO com.biffweb.impl.middleware -  24ms 200 get  /css/main.css?t=1695129186719
[qtp1285414362-37] INFO com.biffweb.impl.middleware -   4ms 200 get  /signin
[qtp1285414362-39] INFO com.biffweb.impl.middleware -   6ms 200 get  /signin
[qtp1285414362-36] INFO com.biffweb.impl.middleware -   0ms 200 get  /img/glider.png
[qtp1285414362-40] INFO com.biffweb.impl.middleware -   3ms 200 get  /
[qtp1285414362-36] INFO com.biffweb.impl.middleware -   3ms 200 get  /signin
[qtp1285414362-40] INFO com.biffweb.impl.middleware -   2ms 200 get  /
[qtp1285414362-36] INFO com.biffweb.impl.middleware -   1ms 200 get  /img/glider.png
[qtp1285414362-35] INFO com.biffweb.impl.middleware -   5ms 200 get  /signin
[qtp1285414362-40] INFO com.biffweb.impl.middleware -   5ms 200 get  /
[chime-1] INFO life.worker - There are 2 users.
[qtp1285414362-37] INFO com.biffweb.impl.middleware -   3ms 200 get  /signin
[qtp1285414362-40] INFO com.biffweb.impl.middleware -   3ms 200 get  /

try opening the developer console -> network tab, then click the sign up button. does it show that a request is being triggered? if so, what are the parameters in the request?

The request isn’t triggered. I can send you the call history for each route if you’d like.

I'm guessing it's a recaptcha misconfiguration

since when recaptcha is enabled, it's in charge of triggering the request

Makes sense. I do have to register the URL. Maybe that’s it?

For dev, you just need to make sure you have localhost in your list of allowed domains

if you've done that and it's still not working, I would put some prints in this function: https://github.com/jacobobryant/biff/blob/master/example/src/com/example/home.clj#L15 e.g. (prn site-key) and also (prn ((:biff/secret ctx) :recaptcha/secret-key)) <- don't paste the result of that here since it's a secret just make sure those printed values look correct

That was it. reCaptcha needed the localhost entry. Another rookie mistake. 1000 pardons. Thank you. Deploy (without the database)?

Excellent, glad to hear it's working 🙂 . Sure, if it's working locally now, go ahead and deploy. with or without postgres is fine, up to you.

thanks again

agreed using a websocket instead of live-reload.js (I.e. polling) would be better. the approach described in the first post of that biff github issue is still how I'd do it. in fact one of the changes I recently made in v0.7.11 was to update biff/eval-files! so it returns the code refresh result instead of nil. so you can modify on-save to look at that return value. then you just need to take that data and use it to send a websocket message to the front end

I think htmx will make that fairly straightforward actually

also probably want to have some kind of config option so it only happens in local dev

if the refresh is successful, you can send a message like [:div {:_ "init call window.location.reload()"}] and if it's unsuccessful then show a heads up display with the stack trace or something

Ok thanks for pointers. I don’t yet have much experience with htmx or websockets yet, but will try.

see app.clj in the starter app for an example of using websockets with htmx, you should be able to just copy that for the most part

I dont see app.clj in biff example. https://github.com/jacobobryant/biff/tree/36cfe9b291185c9300239770059fd0e72a2bea05/example/src/com/example Where is that reference? I have one in the eelchat tutorial codeboase, but I’m not seeing the pattern there…?

Is this it? https://github.com/jacobobryant/eelchat/blob/master/src/com/eelchat/app.clj I guess that’s the codebase I am working off, but the tutorial had me already delete a lot of that stuff.. Will re-introduce.

Did you successfully configure Postmark and reCaptcha?

Haven’t got that far yet. I did a dry run hello world 4mo ago and believe I got recaptcha working then…

Is this all that’s relevent to websocket live reload from app.clj or look at more? https://github.com/jacobobryant/eelchat/blob/8faa1d1e311b323402580629ea2283acca3fb584/src/com/eelchat/app.clj#L176C1-L187C94

that bit and also https://github.com/jacobobryant/eelchat/blob/8faa1d1e311b323402580629ea2283acca3fb584/src/com/eelchat/app.clj#L159-L160, for initiating the connection

and https://github.com/jacobobryant/eelchat/blob/8faa1d1e311b323402580629ea2283acca3fb584/src/com/eelchat/app.clj#L201 for sending a message from the backend to the frontend

this is the file I was referring to: https://github.com/jacobobryant/biff/blob/master/example/src/com/example/app.clj (has basically the same websocket bits in it as eelchat; either works as an example)

Ok, thank you for the pointers. I was able to get live.js working based off your commit above!! 🙌 (a bit painful, but good practice I guess to get a feel more modifying the codebase) It’s a bit slow, still feels flakey. Html updates take 1s, css updates 4s. (Will have to time my css build fn, maybe thats the culprit…). But at least they are reloading automatically.. I will try the htmx websocket implementation when I have more time to grok the parts.

great 🙂 one caveat that just occurred to me: the on-save function by default won't run when your css file is updated. I think it'll work if you put this in config.edn:

:biff.beholder/paths ["src" "resources" "target"]
:biff.beholder/exts [".clj" ".css"]

looking sweet 🙂 love the design also

trying out neo-brutalism

this has been used as a reference https://gumroad.com/

its fun

I will probably add config.edn to source control by default actually. Originally secrets were stored verbatim in config.edn, but I moved them out because it's common for various deployment environments to let you store secrets in env vars and I wanted to make it easy to see how to make that work with biff. (whereas for regular config I'm OK with being more rigid and saying "just put it in this edn file.") Also I wanted to make it a little harder for people to accidentally expose their secrets, e.g. by pasting the contents of their config.edn when asking for help, or by logging the system map to the console and having that get stored in a logging service

Ahhh. Thank you. Thoughtful on several levels.

I proposed to move almost all of those out of secrets.edn file so that it would be consistent because some of them are loaded from env vars but others are loaded directly from secrets.edn.