Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checklist for rollover to v2 #22

Open
6 of 17 tasks
oxalorg opened this issue May 17, 2022 · 0 comments
Open
6 of 17 tasks

Checklist for rollover to v2 #22

oxalorg opened this issue May 17, 2022 · 0 comments
Assignees

Comments

@oxalorg
Copy link
Member

oxalorg commented May 17, 2022

Right now the v2 clojurians log is running on clojurians-log-v2.oxal.org/

The end goal is for v2 to be available at clojurians-log.clojureverse.org/

This is a (constantly updating) checklist of the things we need to do to push this live:

Must do

  • Mobile responsive
  • Searching
  • real-time logging
  • A lot of tasks in the Clojurians-log v2 dreams! #3 discussion have already been completed
  • backfill slack data, I only have slack exports from the last year or so. I need rest of the data and update that
  • import of messages from slack web api (currently only user/channel/emojis are being imported from slack web api)
  • backfill slack data idempotently using slack web api, either as a manual button or as a periodic job
  • Switch over to real time socket mode without losing too many events (slack load balances across multiple connections, or possibly add another bot?)
  • Possibly get updated zip archive from slack admins
  • Possibly become a slack admin so I can manage these things without disturbing folks, most probably don't need to do this if the real time stuff is rock solid
  • Ensure real time event data doesn't break if there is a gap in data
  • Ensure updating docker images will run migratus Run migratus on every prod-run #13
  • Mount secrets file for Docker runs #12
  • Store event / transaction logs  #15
  • Cash Update cache for new members and new channels #23

Nice to have

@oxalorg oxalorg self-assigned this May 17, 2022
@oxalorg oxalorg pinned this issue May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant