65
edits
Difference between revisions of "Membermatters"
→Need to Setup, Immediate Actions
| (16 intermediate revisions by the same user not shown) | |||
| Line 41: | Line 41: | ||
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml | # 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml | ||
# `cd ./docker` | # `cd ./docker` | ||
# `docker pull` (this make take a while) | # `docker compose pull` (this make take a while) | ||
# `docker compose up -d` to start your docker image | # `docker compose up -d` to start your docker image | ||
# `docker ps` will list your running containers processes that are created by the docker yaml file | # `docker ps` will list your running containers processes that are created by the docker yaml file | ||
# `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) | # `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) | ||
== Some in-progress notetaking == | |||
# 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 | # 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 | ||
# 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 [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that | # 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 [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that | ||
| Line 59: | Line 59: | ||
Django logs are doing a bunch of Warnings about not finding various /api stuff? | Django logs are doing a bunch of Warnings about not finding various /api stuff? | ||
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff | Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff? | ||
Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun | Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning. | ||
Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters. | |||
== Currently ( 2026-02-07 ) == | |||
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps | Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps | ||
= Membership Plan Setup = | |||
== Adding a Membership Payment Plan == | |||
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members' | |||
== Adding a new tier to the existing payment plans == | |||
Click the plan you made, click ''that'' plus icon. | |||
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount | |||
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end) | |||
= MEMBERSHIP PROCESS- DISCUSSION = | = MEMBERSHIP PROCESS- DISCUSSION = | ||
| Line 72: | Line 82: | ||
* subscription statuses can be: active (currently paying) / inactive (not paying) | * 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) | * 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) | ||
* 2026-02-10 | |||
ivan and martin and nick did a truth table to figure out statuses: | |||
Membership Status / Subscription status | |||
* Active / Active -> Member | |||
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc) | |||
* Noob / Active -> Induction | |||
* Noob / Inactive -> Induction | |||
* Inactive / Active -> Supporter | |||
* Inactive / Inactive -> Former Member | |||
=== I want to become a member!! Onboarding Steps === | === I want to become a member!! Onboarding Steps === | ||
| Line 89: | Line 110: | ||
=== Need to Setup, Immediate Actions === | === Need to Setup, Immediate Actions === | ||
# Set up membership tiers | # Set up membership tiers - done? we only have one | ||
# Set up payment plans | # Set up payment plans - also done, mirroring the ones on sudohumans | ||
=== Pain points: We need to fix these issues ... later === | === Pain points: We need to fix these issues ... later === | ||
# ''need to check for verification email from member matters'' | # ''need to check for verification email from member matters'' | ||
# ''get access card process needs work'' | # ''get access card process needs work'' | ||
# ''members can see each others activities on member matters'' | # ''members can see each others activities on member matters'' | ||
# ''update welcome and alert emails'' | # ''update welcome and alert emails'' | ||
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend'' | |||
= TODO = | |||
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!) | |||
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow? | |||