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

Bring into line with master repo #8

Merged
merged 154 commits into from
Sep 28, 2023
Merged

Conversation

ndepaola
Copy link

  • As discussed on discord, pulling these changes will involve switching your database over to Postgres
  • You mentioned your upgrade steps will be:
    1. Make a hard backup of the card DB (just in case) and export_sources to csv
    2. Install postgres create a DB for use with mpcfill
    3. Pull changes, pip install updated requirements.txt
    4. Update ENV with new postgres database info, add GAME env variable (as MTG)
    5. Run migrate
    6. Run collectstatic and rebuild front end
    7. Run import_sources to import from our exported csv
    8. Run update_database
    9. Restart gunicorn and hope site is deployed without issues
  • and I also recommended creating a backup of your VPS image before commencing any of this work

the only change to tests here is wrapping things in a layout
because that's where the change query modal has moved to.
…-names

Allow editing individual card names
might have to tweak these more later
going to deploy this, test against mpcfill.com, then make any
necessary adjustments. can't easily test this locally.
…ctly-by-elasticsearch

handle accents in elasticsearch
by waiting until the sample cards query has finished before
commencing the animation
ndepaola and others added 19 commits September 9, 2023 14:13
yes, my sentry DSN is hard-coded into django settings.
i want to track uncaught exceptions in any deployment of this project
through sentry, and sentry reckons the DSN is fine to have publicly
listed: https://docs.sentry.io/product/sentry-basics/dsn-explainer/
still rendering things as a flat list here - maintaining parity
will render tags as a tree view in the next commit
i reckon we'll have too many tags on each card for this to be practical
i thought i made this change a little while ago, but it must
have gotten lost in translation
the intention here is to maximise flexibility for backend deployments
so they can configure tags however they want.
@Investigamer Investigamer merged commit 9212296 into Investigamer:master Sep 28, 2023
2 of 3 checks passed
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

Successfully merging this pull request may close these issues.

4 participants