need to sort out logging

Author: hjwp

chapter_10_production_readiness.asciidoc

@@ -459,14 +459,42 @@ We have a container that we're ready to ship to production!
 Find out how in the next exciting installment...
 
 
-////
+
 === TODO: log files
 
-provoke a 500 error somehow and make sure we see tracebacks for it?
+
+provoke a 500 error somehow and make sure we see tracebacks for it.
+
+
+eg delete db.sqlite3
+
+Will show no logs, because by default when DEBUG=True logs are emailed to admins
+
+https://docs.djangoproject.com/en/5.0/ref/logging/#default-logging-configuration
+
+simple logging config, send everything to stdout:
+
+
+[role="sourcecode"]
+.src/superlists/settings.py (ch10l009)
+====
+[source,python]
+----
+LOGGING = {
+    "version": 1,
+    "disable_existing_loggers": False,
+    "handlers": {
+        "console": {"class": "logging.StreamHandler"},
+    },
+    "loggers": {
+        "root": {"handlers": ["console"], "level": "INFO"},
+    },
+}
+----
+====
+
 
 docker logs might be enough.
-alternatively, mount logfiles from host.
-////
 
 
 [role="pagebreak-before less_space"]

chapter_11_ansible.asciidoc

@@ -523,6 +523,17 @@ false, "AttachStdout": true, "Cmd": ["gunicorn", "--bind", ":8888",
 ----
 
 TODO: sort out macos M1/arch issues, `docker build --platform linux/amd64` etc.
+////
+    - name: Build container image locally
+      community.docker.docker_image:
+        name: superlists
+        source: build
+        state: present
+        build:
+          path: ../Dockerfile
+          platform: linux/amd64
+      delegate_to: 127.0.0.1
+////
 
 Looks ok! Let's see if that worked?
 
@@ -574,6 +585,7 @@ config either.
 DJANGO_DEBUG_FALSE=1
 DJANGO_SECRET_KEY="{{ secret_key }}"
 DJANGO_ALLOWED_HOST="{{ host }}"
+
 ----
 ====
 
@@ -583,7 +595,8 @@ DJANGO_ALLOWED_HOST="{{ host }}"
 ====
 [source,yaml]
 ----
-
+    - name: Import container image on server
+      [...]
 
     - name: Ensure .env file exists
       ansible.builtin.template:
@@ -594,6 +607,13 @@ DJANGO_ALLOWED_HOST="{{ host }}"
         secret_key: "{{ lookup('password', '/dev/null length=32 chars=ascii_letters,digits') }}"
         force: false  # do not recreate file if it already exists.
 
+    - name: Run container
+      community.docker.docker_container:
+        name: superlists
+        image: superlists
+        state: started
+        recreate: true
+        env_file: ~/superlists.env
 ----
 ====
 
@@ -616,95 +636,33 @@ show ssh, curl localhosts maybe.
 ====
 [source,yaml]
 ----
-    - name: Allow nonroot user to bind to port 80
-      ansible.posix.sysctl:
-        name: net.ipv4.ip_unprivileged_port_start
-        value: 80
-        reload: true
-      become: true
-
     - name: Run container
-      containers.podman.podman_container:
+      community.docker.docker_container:
         name: superlists
         image: superlists
         state: started
         recreate: true
-        env_file: /superlists.env
+        env_file: ~/superlists.env
         ports: 80:8888
 ----
 ====
 
 
-==== Using Systemd to Make Sure Our Container Starts on Boot
+////
+==== Making Sure Our Container Starts on Boot
 
-((("Systemd")))
 ((("Container", "automatic booting/reloading of")))
 Our final step is to make sure
 that the server starts up our container automatically on boot,
 and reloads it automatically if it crashes.
 
-Ansible and the podman plugins have some modules for this:
-
-
-[role="sourcecode"]
-.infra/ansible-provision.yaml (ch11l006)
-====
-[source,yaml]
-----
-    - name: Create container
-      containers.podman.podman_container:
-        name: superlists
-        image: superlists
-        state: stopped
-        recreate: true
-        env_file: ~/superlists.env
-        ports: 80:8888
-
-    - name: Generate Systemd config file
-      containers.podman.podman_generate_systemd:
-        name: superlists
-        dest: ~/.config/systemd/user/
-
-    - name: Container must be started and enabled on systemd
-      ansible.builtin.systemd:
-        name: container-superlists
-        daemon_reload: true
-        state: started
-        enabled: true
-----
-====
+(used to need systemd, now you can just set restart_policy.
+////
 
 
-----
-vagrant@ubuntu-jammy:~$ cat ~/.config/systemd/user/container-superlists.service
-# container-superlists.service
-# autogenerated by Podman 3.4.4
-# Wed Oct 25 10:55:38 UTC 2023
-
-[Unit]
-Description=Podman container-superlists.service
-Documentation=man:podman-generate-systemd(1)
-Wants=network-online.target
-After=network-online.target
-RequiresMountsFor=/run/user/1000/containers
-
-[Service]
-Environment=PODMAN_SYSTEMD_UNIT=%n
-Restart=on-failure
-TimeoutStopSec=70
-ExecStart=/usr/bin/podman start superlists
-ExecStop=/usr/bin/podman stop -t 10 superlists
-ExecStopPost=/usr/bin/podman stop -t 10 superlists
-PIDFile=/run/user/1000/containers/overlay-containers/c058e368b446388cf3b3faecdf1d8186d14d8b0a01fbf64bfca5714ae56d42fe/userdata/conmon.pid
-Type=forking
-
-[Install]
-WantedBy=default.target
-----
+=== Mounting the database on the server
 
-Systemd is joyously simple to configure (especially if you've ever had the
-dubious pleasure of writing an `init.d` script), and is fairly
-self-explanatory.
+TODOOooo
 
 
 [role="small-code"]
@@ -723,12 +681,14 @@ A few more places to look and things to try, now that we've introduced
 Podman and Systemd into the mix, should things not go according to plan:
 
 - You can check the Container logs using
-  `podman logs superlists`.
-  ((("debugging", "Podman")))
+  `docker logs superlists`.
+
+- You can get detailed info on the Container using
+  `docker inspect superlists`.
 
-- You can check the Systemd logs using
-  `journalctl --user -u container-superlists`.
-  ((("debugging", "Systemd")))
+- And you can inspect the image with
+  `docker image inspect superlists`.
+((("debugging", "Docker")))
 
 
 *******************************************************************************