haruska / madness Goto Github PK

See discussion https://discuss.hotwired.dev/t/button-to-not-showing-the-data-confirm/2046

DHH says it's fixed in hotwired/stimulus-rails#29 but it doesn't seem to be.

the links are getting hijacked in iPhone sub-browsers. Make it a code to type in instead.

• Set up Docker and Docker Compose
• #32

https://github.com/rails/kredis

Could be interesting to replace some high-use ActiveRecord attributes or to store the Tournament.

Might be interesting to allow users to see everyone who has brackets but not their picks before tipoff.

• Update top header and nav: created logo in 2019 (on nas )
• Bracket list as table ... something better?
• Add team logos
• Mobile views for tourney/bracket
• non-hamburger menu for desktop

"remember me" cookies don't seem persistent on safari. there is also the issue of the link being captured by gmail app. need to rethink general authentication and maybe move to a more traditional username/password model in devise. People would have to go through the "forgotten password" flow. Could possibly send out links next year with that imbedded.

Might also want a way to "sign up" but that must be approved by the admin. Would eliminate needing to invite people. Maybe a free-form text of "who invited you"

ToDo:

• set rememberable and timeoutable module config
• set validatable config
• Format Errors
• Forgotten password flow

Currently signing out ends up as a noop:

16:59:59 web.1    | Can't verify CSRF token authenticity.
16:59:59 web.1    | Completed 422 Unprocessable Entity in 3ms (ActiveRecord: 0.4ms | Allocations: 1808)
16:59:59 web.1    | ActionController::InvalidAuthenticityToken (Can't verify CSRF token authenticity.)

• Decisions: react, relay, found/farce, dart-sass, rebuild, rails 7
• Bitwise logic, what are the different slots, different calculations that are possible
• Faster scoring
• Sessions vs JWT
• Removing factories
  • New tournament helpers in tests
  • running seeds in test
• Admin dashboard setup and customization
• Stylesheets and style generation, use of Bourbon (without neat or bitters)
• Rails secrets (with master.key in password manager)
• use of Pundit with no guests
• user errors in GraphQL
• images in sass/rails (wood background)
• Move to typescript
• use of react hooks for AppContext
• moving tournament, teams, current user to AppContext
• disabling Turbolinks (why?)
• use of font awesome... downloaded all for sass and fonts in public

Relay still needs babel. Will still use js-bundling rails https://github.com/rails/jsbundling-rails

Would like a set of email addresses to email:

• All users
• Users with no brackets
• Users with unpaid brackets
• Users that never logged in

Need better messaging on the authentication emails.

The tiebreaker is not really used (and confuses people.) Remove it and just split the winnings in the event of a tie.

• Better emails / messaging
• remove extra click to login

Some fields are virtual (seed, region) but the admin dashboard tries to search over them.

There are changes to how live reload and watch work that are incompatible with the current setup. Came out in Jan 2023.

See:

• https://esbuild.github.io/api/#watch
• https://github.com/evanw/esbuild/releases/tag/v0.17.0

After all games are played, remove "possible" finishes and points. Also don't cross out eliminated final four teams (maybe not show the final four teams at all?)

• Do not create/destroy tree on every change.
• Move to all static functions working on slot number.
• Remove all data from tournament that can be calculated

According to pundit admin can manage all brackets. This is still needed for the admin dashboard. However, for the user frontend, we should further scope down to the current user's brackets unless it's past tipoff.

There has been good development on Ruby and Rust interop. Look into speeding up elimination calculations using Rust.

See: https://github.com/matsadler/magnus

At a minimum for mailers. Other jobs (scores, elimination, etc.) as well.

• Generate random passwords for current users
• downcase all emails in db

Faktory allows for polygot workers. Would like to optimize some jobs using Go instead of Ruby. Moving to Faktory allows both Ruby and Go (and Rust) workers.

• Stick with Heroku
• Need CDN for rails assets (or Cloudflare passthrough?)
• Email: sendgrid? GMail SMTP? Auth emails from another account?

For CDN, ensure things in public are there as well (web fonts, etc)

• Need error and performance monitoring (Sentry.io, Airbrake, New Relic?)
• Product monitoring? (Mixpanel / proxy)

There are self-hosted as well: GlitchTip