20240523

• Added celery in my personal project
• Tried to write a Github Actions configuration file for a gigantic Django project, but failed to resolve issues. Tired.
  • print() in migration files are in stdout, so the preparation of test database should be working fine, but facing errors when running tests after the mgiration
  • database configuration in settings.py looks very fine to me

/opt/hostedtoolcache/Python/3.11.9/x64/lib/python3.11/site-packages/django/db/backends/base/base.py:289: in ensure_connection
    self.connect()
/opt/hostedtoolcache/Python/3.11.9/x64/lib/python3.11/site-packages/django/utils/asyncio.py:26: in inner
    return func(*args, **kwargs)
/opt/hostedtoolcache/Python/3.11.9/x64/lib/python3.11/site-packages/django/db/backends/base/base.py:270: in connect
    self.connection = self.get_new_connection(conn_params)
/opt/hostedtoolcache/Python/3.11.9/x64/lib/python3.11/site-packages/django/utils/asyncio.py:26: in inner
    return func(*args, **kwargs)
/opt/hostedtoolcache/Python/3.11.9/x64/lib/python3.11/site-packages/django/db/backends/postgresql/base.py:275: in get_new_connection
    connection = self.Database.connect(**conn_params)
/opt/hostedtoolcache/Python/3.11.9/x64/lib/python3.11/site-packages/psycopg/connection.py:728: in connect
    attempts = conninfo_attempts(params)
/opt/hostedtoolcache/Python/3.11.9/x64/lib/python3.11/site-packages/psycopg/_conninfo_attempts.py:45: in conninfo_attempts
    raise e.OperationalError(str(last_exc))
E   psycopg.OperationalError: [Errno -3] Temporary failure in name resolution

Git Aliases to switch user profile

I added these aliases in ~/.gitconfig to switch user profiles for work and personal time

[alias]
    suffer = !git config --global user.email '[email protected]'
    bail-out = !git config --global user.email '[email protected]'

Now I can easily switch user profiles. I've been involvd in multiple projects/repositories, and found it difficult to manage user configurations.

Enabling HTTP/2 and HTTP/3

Enabling HTTP/2 or HTTP/3 for my web application involves configuring the web server that serves the application.

Enabling HTTP/2 with Nginx

1. Update Nginx to 1.9.5 or later

In my case, my Nginx container should be able to serve with HTTP/2

https://github.com/huyfififi/mastodon/blob/main/docker-compose.yml#L136

services:
  nginx:
    image: nginx:1.25.3

2. Update the configuration for port 443 (HTTPS)

HTTP/2 seems to require TLS (encryption for HTTP connections)

• Stack OverFlow: Why do browser implementations of HTTP/2 require TLS?
• Stack Overflow: Is TLS mandatory for HTTP/2?

Therefore, it will go under port 443

It seems I already turned on HTTP/2

https://github.com/huyfififi/mastodon/blob/main/dist/nginx.conf <- It’s completely messy. I better review and update it.

  server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;
    server_name ocalaavenue.net;

but it seems this also works

  server {
    listen 443 ssl http2;

3. Restart the server and check the protocol used in response

# curl -I --http2 https://ocalaavenue.net
HTTP/2 200

I can see that HTTP/2 is in response headers, meaning that my Mastodon instance is already served with HTTP/2

Enabling HTTP/3 with Nginx

nginx: Support for QUIC and HTTP/3

It seems I better check QUIC before trying to digest the configuration. It looks intimidating.

Sushi bowl 800 Avocado 200 Yogurt 300 Kombucha 100 Bubble tea 100

Total 1500 kcal

TODO:

• Amazon Elastic Kubernetes Service (Amazon EKS)
  • https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html

index 20240522 20240524