You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Systemd to monitor workers (we already use it to monitor Scrapyd)
python manage.py migrate should create:
CREATE TABLE public.django_migrations (
id integer NOT NULL,
app character varying(255) NOT NULL,
name character varying(255) NOT NULL,
applied timestamp with time zone NOT NULL
);
CREATE SEQUENCE public.django_migrations_id_seq
AS integer
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1;
ALTER SEQUENCE public.django_migrations_id_seq OWNED BY public.django_migrations.id;
ALTER TABLE ONLY public.django_migrations ALTER COLUMN id SET DEFAULT nextval('public.django_migrations_id_seq'::regclass);
ALTER TABLE ONLY public.django_migrations
ADD CONSTRAINT django_migrations_pkey PRIMARY KEY (id);
We deployed this to the data registry, and will deploy it to a fresh server for the helpdesk (rather than the more difficult original plan to migrate the deployment to the new version).
PostgreSQL uses UTC.
Docker is used to monitor workers.
The tables listed as being droppable don't exist in the new version.
https://docs.djangoproject.com/en/3.0/howto/deployment/
Go through checklist, notably:
https://pypi.org/project/dj-database-url/
Set environment variables from Salt:
Miscellaneous:
python manage.py migrate
should create:We can later manually drop:
As follow-up to #242, we can also drop:
The text was updated successfully, but these errors were encountered: