20241009

latest copies of “ケンガンオメガ” & “灼熱カバディ”!

Understanding Mastodon System Components

This is compose.yaml I use to run my server, and it should not be so different from what others use.

Please note that some values and services are omitted to save space. For example es (Elastic Search) service can be deployed to Mastodon, but I don't use it to make things simple.

(The compose.yaml just makes sense… it's embarassing that I didn't understand when I first deployed the services…)

services:
  db:
    image: postgres:14-alpine

  redis:
    container_name: redis
    image: redis:7-alpine

  web:
    build: .
    image: ghcr.io/mastodon/mastodon:v4.3.0
    depends_on:
      - db
      - redis

  streaming:
    build: .
    image: ghcr.io/mastodon/mastodon:v4.3.0
    depends_on:
      - db
      - redis

  sidekiq:
    build: .
    image: ghcr.io/mastodon/mastodon:v4.3.0
    depends_on:
      - db
      - redis

  nginx:
    image: nginx:1.25.3
    depends_on:
      - web
      - streaming

Main Application

ActivityPub

Servers that speak ActivityPub send requests back and forth. To handle those requests, background jobs are used.

As simple as it is. Still, it's hard for me to manage the infrastructure, but for those who have experience in web applications, its design should not be something that are very different from the industrial standard.


Chips 350 m&m's 250 Salad 400 Pasta 600 Nori 100 Berries 300

Total 2000 kcal


MUST:

TODO:


index 20241008 20241010