Membermatters

this is the notes for the membermatters installation

https://backers.sudoroom.org

to create a new user

• https://backers.sudoroom.org/register

to check the logs from the docker instance

• sudo less /var/lib/docker/containers/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log
• https://backers.sudoroom.org/logs/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log

github

• the changes juul made to add sendmail as an option
• the changes rechner and jake made to build our docker for postgres
• we are using the sudoroom branch in our docker
• we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
• we are working on mounting the docker image with git on the server, so we can make changes to production and try them
• we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

we are not spam

• emails sent by this system for people to validate their account, or reset their password, are important
• emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
• we should look for ways to find out why the emails are rejected by some servers
• we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
• Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
• emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
• we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
• we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

certbot

• juul used pipx to install, and then had to manually make a systemd job to check it twice a day

Help us build and test

• prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
• submit a bug: https://github.com/sudoroom/MemberMatters/issues

Making a dev environment

(this assumes you already have git installed and docker setup!)

1. `cd` to a directory you want to put the repo
2. `git clone https://github.com/sudoroom/MemberMatters.git`
3. `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
4. `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
5. `cd ./docker`
6. `docker pull` (this make take a while)
7. `docker up -d` to start your docker image
8. `docker ps` will list your running containers processes that are created by the docker yaml file
9. `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

where I got to/next steps

1. doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
2. there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the docker-compose.yml ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

MEMBERSHIP PROCESS- DISCUSSION

ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:

• subscription statuses can be: active (currently paying) / inactive (not paying)
• member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

I want to become a member!! Onboarding Steps

1. Hang Out, attend an event, join lists, discord
2. I Like this! - Fill out the Intent to Join Form!!!
3. Attend the next meeting, and get endorsements
4. Get a mentor!!

Setup payment on Member Matters

1. Create an account, verify via email
2. I'm on Sudo Humans, what do I do?
3. I use PayPal, or checks, or Bitcoin. What do I do?

Get door access

1. Get an email?
2. How many door access systems will we have?

Need to Setup, Immediate Actions

1. Set up membership tiers
2. Set up payment plans

Pain points: We need to fix these issues ... later

1. need to check for verification email from member matters
2. free accounts need billing info
3. get access card process needs work
4. members can see each others activities on member matters
5. need to edit dashboard, landing page
6. update welcome and alert emails