I’ll have a look at this. 

I've tried a few times and haven't been able to replicate the issue. What browser are you using? Can you try in an incognito/private mode to see if that makes a difference? You may try signing out and signing in again too. The weird part is that it is saying that the origin is https://driftingruby.com instead of https://www.driftingruby.com because I do have a perm redirect from the root to www.

What have been some of your pain points when working with docker in your development environment?

I’m not fully versed on GDPR but one idea is to not track the IP or other identifiable information. What purpose does the logs serve for you and do you need the identifiable information in it?

If you do need to retain this information then you could set some limits wherever they’re shipping to. I haven’t looked much locally, but typically the logs are “gone” after a deployment via kamal. 

  Sigfrid  i don’t pass the SSH key in the deploy.yml file but rather in a GitHub action secret in their GUI.