• 1 Post
  • 10 Comments
Joined 22 days ago
cake
Cake day: January 22nd, 2026

help-circle


  • If you like compose files: https://www.composerize.com/

    docker run -it --rm -v <your-data-path>:/data -e SYNAPSE_SERVER_NAME=<your-public-address-subdomain> -e SYNAPSE_REPORT_STATS=no matrixdotorg/synapse:v1.136.0 generate:

    name: <your project name>
    services:
        synapse:
            stdin_open: true
            tty: true
            volumes:
                - <your-data-path>:/data
            environment:
                - SYNAPSE_SERVER_NAME=<your-public-address-subdomain>
                - SYNAPSE_REPORT_STATS=no
            image: matrixdotorg/synapse:v1.136.0
            command: generate
    

    docker run -d --restart=always --name synapse -e SYNAPSE_REPORT_STATS=no -v <your-data-path>:/data -p 8008:8008 matrixdotorg/synapse:v1.136.0:

    name: <your project name>
    services:
        synapse:
            restart: always
            container_name: synapse
            environment:
                - SYNAPSE_REPORT_STATS=no
            volumes:
                - <your-data-path>:/data
            ports:
                - 8008:8008
            image: matrixdotorg/synapse:v1.136.0
    
    






  • It also includes other functions that is not NSFW. Nothing that I personally care about but might be a deal breaker for bigger communities.

    Discord breaks down the restrictions as follows:

    • Content Filters: Discord users will need to be age-assured as adults in order to unblur sensitive content or turn off the setting.
    • Age-gated Spaces: – Only users who are age-assured as adults will be able to access age-restricted channels, servers, and app commands.
    • Message Request Inbox: Direct messages from people a user may not know are routed to a separate inbox by default, and access to modify this setting is limited to age-assured adult users.
    • Friend Request Alerts: People will receive warning prompts for friend requests from users they may not know.
    • Stage Restrictions: Only age-assured adults may speak on stage in servers.


  • A snapshot is like copying a the files in the snapshot to another location, while the original files remain as is and can be written to or read from.

    As an example, if you have a folder, let’s say /important/secret/stuff, and you want to take a backup of it. You have to make sure that nothing is writing to those files while the backup is running, otherwise the backup risk being corrupted. (This is because if the backup starts to read the file, and halfway through the first part of the file changes, you now have a backuped file that half the old and half the new file).

    With a snapshop, you can “copy” /important/secret/stuff to some other location, run a backup reading from this other location and then remove it. Any changes to the original files will not affect the backup since the backup is reading from the “copied” files (snapshot).

    So what you do is take a snapshot before running the backup, have the backup read from the snapshot and when it is complete, remove the snapshot.