Two frontends, both alike in dignity, in fair VHS where we lay our scene.

[coryalder]

In an effort to land the feat/writing-a-lot-of-code-for-v2.0-and-all-I-got-was-this-lousy-branch-name branch, with it's majestic react frontend lovelyness.

My plan was (and still is) to deploy both frontends -

• https://membership.vanhack.ca/ the new react version
• https://membership.vanhack.ca/v1/ the old angular version

todo:

• react admin can't edit a member's privs, broken
• react admin can't create new privs, missing
• react admin can't delete privs, missing
• react user can't search users on grant privileges page, broken
• react user can't grant privs, broken
• add an "old interface" button somewhere, so you can escape if needed
• deploy!

[acruise]

outfuckingstanding PR title

[EricNelson12]

@coryalder trying to understand all the differences in your branch. Are you moving to a single docker file instead of the docker-compose.sh switch?

And image: mariadb:11.4 , does this switch the DB from mysql to mariadb? is that an easy migration?

I was able to get the master branch working, but not this one so far haha

also i'm terrible at responding on github 😬

[coryalder]

Yeah, I ended up nuking the customized docker compose script in favour of a single docker compose file. I got rid of a bunch of the extra services that were being run, so it didn't seem super useful to keep the script around. I'm VERY open to other opinions here tho, so if you think it's worth keeping we could roll that stuff back.

As I said in slack DMs, the mariadb switch was because I encountered a problem upgrading mysql - something about database adapters, that is lost to the sands of time.