cb109

mount c ~/dosgames
imgmount d "~/dosgames/conqstND/cd/Conquest.cue" -t iso -fs iso
c:
cd CONQSTND
cnwmain.exe -usecd

cb109

cb109

Location for in game save files on Onion OS:

/mnt/SDCARD/Saves/CurrentProfile/saves/Gambatte/Mystic Quest (Europe).srm

Location for in game save files on DrUm78's Funkey OS:

/mnt/Funkey/.picoarch/data/gambatte/Mystic Quest (Europe).sav

Despite the different file extensions, these files are interchangeable. You can copy from one location to another and rename the file extension for the system (e.g. with Dingux Commander) and the emulator/game should detect it

cb109

#!/bin/bash

# In this example we want to execute 'git pull' on the local 'master' branch, but we
# want to make sure that pull won't introduce conflicts and by that a broken checkout.
# The script below will do an in-memory merge of the upstream master and local master
# and exit with a non-zero code if that merge produced any conflicts.
#
# A snippet like this is useful for deployment scripts that involve 'git pull' to 
# prevent breaking production if for some reason a conflict has bypassed CI.
#

cb109

When receiving AJAX responses that contain Set-Cookie headers from a different origin/domain, by default these headers conflict with the browser's same origin policy and are rejected/not set. We must specify withCredentials: true or similar flags on the request to allow for this (e.g. to receive a CSRF token as a cookie that we can then read back and attach to each POST request):

• XMLHttpRequest
  • withCredentials: true
  • https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/withCredentials
• axios
  • withCredentials: true
  • https://flaviocopes.com/axios-credentials/
• fetch
• credentials: 'include'

cb109

Let me point out that losing migration files is a very bad situation and should be avoided at all costs, but if it happens, having a step-by-step way to preserve the database is a good thing to have. It is a terrible situation to be in if your database/models/migrations are a shared state across multiple team members, and that would require a coordinated halt and cleanup so everyone can move forward from the same base state again, with a proper migration files workflow from then on.

Let's assume you have models, any number of migration files, all of those applied to your existing database. Now for some reason, poof!, all the migration files are gone.

cb109

Partially ignore table fields on a Django model

There may come a day where your table includes a field that your Django app should ignore and not even be aware of, while other clients may still need to use that field in production through normal SQL commands. How to achieve this?

Removing a model field will give you a migration step like this:

        migrations.RemoveField(
 model_name="mymodel",

cb109

import subprocess

def add_progressbar_on_top_of_video(
    input_video_filepath: str,
    output_video_filepath: str,
    width: int,
    height: int,
    duration: float,
    fps: float = 25.0,
    progressbar_height: int = 8,

cb109

class Bar:
    def __init__(self):
        self.parent_class_attr_name = None


class LetClassAttributesKnowTheirName(type):
    def __new__(mcs, name, bases, attributes):
        for attr_name, attr_value in attributes.items():
            if isinstance(attr_value, Bar):
                attr_value.parent_class_attr_name = attr_name

cb109

{% extends "admin/base_site.html" %}

{% block usertools %}
  {% url 'admin:index' as admin_index_url %}
  {% if request.get_full_path == admin_index_url %}
    <input
      type="text"
      id="admin_base_search"
      placeholder="Search..."
      autofocus