|Open||None||T125272 Epic: Create Preference Center for donors to manage email subscription preferences|
|Open||None||T263887 Email Preference Center Prototype|
|Resolved||None||T266607 Investigate email preference center prototype|
So I'm gonna have a go at adding another docker image (just to my docker-composer repo for now) with civiproxy on it & trying to connect through - maybe I need 2 images/containers to represent the 2 new machines in play (proxy & new external interface)
I started digging into civiproxy. I tried to get it set up in my local docker but it turns out to need https: so I tried to get that into the docker image. I've been trying this approach - https://blog.dcycle.com/blog/2018-10-27/local-https-docker-compose/ but at the time of writing it's not working (although the example whoami is working) - this is the code I have been trying https://github.com/eileenmcnaughton/civicrm-buildkit-docker/compare/master...eileenmcnaughton:civiproxy?expand=1 - due to the generalised lack of wild success I have just been trying on dmaster.
In terms of the 'challenge' with civiproxy - they suggest creating your own api because civiproxy doesn't ensure that required fields are populated - I can't help thinking extending the metadata to permit a min_input_length per field would resolve that.
Not sure if this is where I should post this, but after talking to Trilogy yesterday, it was brought to my attention that we currently have 2 databases on Acoustic (all_wikimedia and Major Gifts) and that those 2 should be merge in one single preferably before we launch the preference center. Is this in your radar Eileen, Dave?