dracidoupe / graveyard Goto Github PK

NoReverseMatch: Reverse for 'common-article-detail' with keyword arguments '{'creative_page_slug': 'clanky', 'article_id': 2677, 'article_slug': ''}' not found. 1 pattern(s) tried: ['rubriky\/(?P<creative_page_slug>[^/]+)\/(?P<article_id>[0-9]+)\-(?P<article_slug>[^/]+)\/$']

Once views are stable, use defer('text') everywhere.

By breaking down the model field, more apps with unidirectional dependency graph shall be considered:

• Creations
• Social
• Chat (rewritten)

• Add returnto argument to http://nove.dracidoupe.cz/nastaveni/zmena-skinu/?skin=light
• Do not forget to validate it's on the same server to prevent redirect hijacking

Although reliably, I'd probably still add JS counter for the amount of people who printed using the button :)

Article name should be h1, figure out good element / class for sections.

Allow editors to be set for CreativePages and drive the permissions from there. Fix the problem with migrations.

(or should it be directly derived by permissions on CreativePage?)

Currently, they are randomly linked and not editable by editors, that's relatively easy to fix and helps migration.

• Displaying basic info
• Handle permissions
• Reputation summary and reputation detail page (Part of task #126 )
  - [ ] Newbies&Mentats
• Runes

Example articles and overall content should be provided for other devs.

Turn off styles, verify responsiveness and accessibility guidelines.

Properly paginate lists.

Because of modern technology, static media can now be deployed on a different domain and moved to CDN.

Move them out of model and reuse them in views instead of relying on "a" and "n" as magical constants.

Celery now has direct Django support: http://docs.celeryproject.org/en/latest/django/first-steps-with-django.html

Level system computations etc. should be handled using that (with Admin interface as a bonus). If Graveyard works properly™, that should actually be done while the old version is still running.

As a follow-up for #3 , provide a way for user to upload their own media (to a certain size limit) and link to them from within articles).

What is the best (and future-proof way) to query a database in a way where misencoded fields are managed transparently?

See http://ddcz.readthedocs.io/en/latest/migration.html#database-encoding and https://github.com/dracidoupe/graveyard/blob/master/ddcz/models/magic.py for context.

Seems like newer schema migration framework or some other component is incompatible with mysql 5.5, which is unfortunately used on old production: https://circleci.com/gh/dracidoupe/graveyard/113

This means especially:

• Custom uploaded "article" content in obr_pris
• Downloady

This needs to work around the Django vulnerability in >2.0<2.2.x version.

OK, number of integrity problems are coming up and all the 500s/logging.fatals need to be reported to developer.

Figure out how to do that. Sentry is a good contestant, but try to be GDPR-conscious and try to use least amount of 3rd party infrastructure possible.

Send a warning / error on UserProfile.slug being empty

Unify them:

• Common ancestor Creation
• Unified Templates
• Common View correctly named
• Create fixtures for current hardcoded model
• Prevent runtime from messing it up
• Fix article detail

What needs to be configurable?

• Template for particular Creation Page (probably more readable than dynamic magic around fields)
• Template could probably be hardcoded / set on CreativePage model attribute directly

Considerations:

• Solve creations with custom media being uploaded

Rating stars have the g'old feeling...that doesn't scale to new monitors. Also, GIFs.

Redo those as scalable SVGs.

Hi there,

You are receiving this email because you are an active member of one or more projects building on CircleCI that do not have pipelines enabled. Below are the settings URLs for these projects:

[https://circleci.com/gh/dracidoupe/graveyard/edit#advanced-settings]

We will be automatically turning on pipelines for these projects starting March 9th, 2020.

If you are an admin for any of these projects, please visit Project Settings > Advanced Settings (or use the URLs above) and enable the “pipelines” setting for the project. A pipeline contains all of the workflows (and the jobs inside those workflows) that CircleCI runs after a trigger on your project. A pipeline can be triggered by a pull request, a commit, or even an API call.

Enabling pipelines will offer the following improvements to your CircleCI experience:

Access to our new user interface
Auto-cancel redundant builds on non-default branches
Ability to reuse config and share config using orbs
New API endpoints (v2 API)
Our goal is to make this transition seamless, but we encourage you to enable pipelines manually at your earliest convenience to mitigate any unforeseen errors.

If you run into any issues, check out this Discuss post for more resources. You can also register for this webinar on March 5th where a member of our team will walk you through enabling pipelines and the advantages of pipelines.

Thank you!
The team at CircleCI

G'old article filters as the old DDCZ had it.

(originally, there are creations with sources (zdroje) without authors)

In the current state, some Creations have associated media (usually images). In the current implementation, those are uploaded separately into a directory and referred to from Creation text via HTML tag.

No association is stored; than only happens in cases where the media is the article (i.e. Gallery).

Find a way to look those up and keep track of the relation in order to be migrate the media to other store reliably.

• We should sent emails as we did
• Email settings should be respected (and make extra sure unsubscribes still work)

Actually two issues:

• Transactional emails #90
• Mailing lists

See how Django does it and look for official documentation.

• Have an official enumerator for them
• Allow people to use database for things that are now implemented as ad-hoc templates (i.e. rules for adding articles)

Housekeeping:

• Have separate Creation Author profile
• Redirect profiles to normative URL in case of user nick slug mismatch
• Creation models should know their canonical link & add link to profile page
  • Migrate Downloads and Quests to use the unified Creation views (and URLs and links) and rename the URL patterns appropriately (commonarticle -> creation)
  • Consider using get_creation_canonical_url in list templates as well
• User icon on user profile
• Consider template tag for displaying authors
• Fix a particular author going to unknown http://zeruel:8000/rubriky/galerie/966-truhlice-ii/
• Handle News authors properly
• Handle Authors without corresponding User properly
• Sanity integration check for all creativepages on example writings
• Link to Author's profile from User's profile

Old routes must resolve to new once.

Hence, one big fat index.php dispatcher is needed to route to new URLs.

Given the amount of handwaving, do a consistency check command that would check underlying assumptions.

Examples:

[ ] Items for downloady are where it's assumed

• Hřbitov
• Dovednosti
• Linky
• Alchymistické předměty
• Hraničářská kouzla
• Kouzelnická kouzla
• Předměty
• Downloady
  • Display the current state
  • Reconcile migrations with the fix-items branch/master
  • Correct download as in the original version
  • Make new version-specific download counter
  • Migrate to django-storage and handling uploads
  • Figure out local development and display
  • [ ] Prepare the final migration script for merging download counts (-> #100 )
• Dobrodružství

• Check in database/codebase what Dovednosti.hlasoval is used for
• Update infrastructure documentation with S3 and env var setup
• Verify on production current state of predmety.precteno attribute/db column

--

Design for Dobrodruzstvi (Quests) and Downloady (Downloads):

• s3sync cron on the original server to synchronize two way with a bucket from which we'll serve the data
• handled on the graveyard side by using django-storages

1.0 is getting sunset: https://circleci.com/sunset1-0/#migration-steps

This can be done without db migration since db column can be overruled. It will make codebase more consistent and readable.

• Tavern @Almad
• News @Almad
• Creations @Almad
• Discussion @Almad
• Social @Almad
• Users @Almad

Fuckup recovery

• Save original branch for easy final version copypasting
• Squash original translation blob
• Copypaste back all original column names
• Create db_column AlterColumn migrations
• Copy all models from the original final branch
• yes | rename migrations
• Verify tests 😬

• Extend CreativePageSection:

class CreativePageSection(models.Model):
    """ Section within a Creative Page """
    name = models.CharField(max_length=30)
    slug = models.SlugField(max_length=30)
    creative_page = models.ForeignKey(CreativePage)

• Put all existing sections into pages.yaml / new sections.yaml fixture
• Link all existing creation pages to it
• Write migration for existing data

• CommonArticle
• Graveyard
• (Photo)Gallery
• Skills
• Monster Manual
• Campaigns
• Items
• Downloads
• Links
• Alchemist tools
• Ranger's magic
• Sorcerer's magic
• Dating
• Advertising

Only a subset is supported now. Support the full range of HTML weirdness.

Current requirements:

• Proper th/tr/td colspan/rowspan handling

Follow-up todo:

• Check for need for addslashes
• Make sure we are handling check on tag pair on input correctly

• Delete the hardcoded port from Selenium class
• Figure out the assigned port range and allow it in django-compose