Yes, you should use the master branch, which is in sync with production.
The beta might not.
The provided container is made with the master branch, not sure why you
are at beta ?
Later, one can switch to the beta one and do a migrate.
Am 21.12.25 um 02:58 schrieb Simone Nardi:
> Hi,
> I tried to start the container. For now, no installation errors occur,
> but at the end of the execution an error is reported.
>
> The dump currently in use is ***incompatible with the beta branch***: a
> column required by the code is missing from the database, therefore
> repeating the import with the same file cannot resolve the error.
>
> The column required by the code is:
>
> ***`gcd_issue.indicia_printer_not_printed`***
>
> This column is explicitly mentioned in the error message and is missing
> from the current dump.
>
> To proceed, a **dump compatible with the beta branch** that includes the
> specified column is required.
> In the absence of an alternative compatible dump, the activity must stop
> in compliance with the defined constraints.
>
> Kind regards
> Simone
>
> Il giorno sab 20 dic 2025 alle ore 11:49 'Jochen G.' via gcd-tech <gcd-
>
te...@googlegroups.com <mailto:
gcd-...@googlegroups.com>> ha scritto:
>
https://github.com/GrandComicsDatabase/gcd-django-docker <https://
>
github.com/GrandComicsDatabase/gcd-django-docker>:
>
> 4. start services, or use -d in detached mode to see the logs - docker
> compose up
> 5. run migrations - docker compose run web /usr/local/bin/python
> gcd-django/manage.py migrate
>
> Jochen
>
> Am 16.12.25 um 17:39 schrieb Simone Nardi:
> > Hi,
> > I propose publishing the clean development environment container on
> > Docker Hub so anyone can start it immediately from VS Code using
> F1 →
> > Dev Containers : Attach to Running Container.
> >
> > This way, only the dump file configuration in a volume is left out.
> >
> > What do you think?
> >
> > Simone
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "gcd-tech" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send
> > an email to
gcd-tech+u...@googlegroups.com <mailto:
gcd-
>
tech%2Bunsu...@googlegroups.com> <mailto:
gcd- <mailto:
gcd->
> >
tech+uns...@googlegroups.com
> <mailto:
tech%2Bunsu...@googlegroups.com>>.
> gcd- <
https://groups.google.com/d/msgid/gcd->
> > tech/0f6fec08-2247-41bf-aac0-7dde11ba12f5n%
40googlegroups.com
> <
http://40googlegroups.com> <https://
> >
groups.google.com/d/msgid/gcd-tech/0f6fec08-2247-41bf- <http://
>
groups.google.com/d/msgid/gcd-tech/0f6fec08-2247-41bf->
> > aac0-7dde11ba12f5n%
40googlegroups.com?
> utm_medium=email&utm_source=footer <
http://40googlegroups.com?
> utm_medium=email&utm_source=footer>>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "gcd-tech" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to
gcd-tech+u...@googlegroups.com <mailto:
gcd-
>
tech%2Bunsu...@googlegroups.com>.
> tech/566cb91a-1974-4b18-ab6d-8f0af1fa06dd%
40garcke.de <https://
>
groups.google.com/d/msgid/gcd-tech/566cb91a-1974-4b18-
> ab6d-8f0af1fa06dd%
40garcke.de>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "gcd-tech" group.
> To unsubscribe from this group and stop receiving emails from it, send
> tech/CAN%2BuuQMSu04q0%2BjJu8fE%3DnsP2UNcC-
> Sr-7NtovSq_sLge2WjUg%
40mail.gmail.com <
https://groups.google.com/d/
> msgid/gcd-tech/CAN%2BuuQMSu04q0%2BjJu8fE%3DnsP2UNcC-
> Sr-7NtovSq_sLge2WjUg%
40mail.gmail.com?utm_medium=email&utm_source=footer>.