Updated the linode example to include publisher. Updated the changelog.

CHANGELOG.md

@@ -10,6 +10,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 * [#35 Conversation replies](https://gitlab.com/ngerakines/tavern/-/issues/35)
 
+  This implements Note subscriptions through `Follow/Note` and `Undo/Follow/Note` activity processing. See the [FEDERATION.md](FEDERATION.md) file for more information on how inbox forwarding is implemented for `Create/Note`, `Announce/Note`, and `Delete/Note` activities.
+
+* [#66 Broadcast agent](https://gitlab.com/ngerakines/tavern/-/issues/66)
+
+  Issue #66 introduces the `publisher` command that allows for async processing of publish operations.
+
 ### Fixed
 
 * Fixed a bug where generated error translations file was incorrectly named.

examples/linode/README.md

@@ -48,10 +48,12 @@ Have the following things ready:
 
          $ cat >> web.env <<EOF
          ENABLE_SVGER=true
+         ENABLE_PUBLISHER=true
          DOMAIN=your.domain
          SVGER=http://svger:9100/
          LISTEN=0.0.0.0:9000
          ASSET_STORAGE_REMOTE_DENY=*
+         PUBLISHER=http://publisher:9200/
          EOF
 
 6. Create the init SQL file used to create the database when postgres starts.
@@ -94,6 +96,21 @@ Have the following things ready:
              environment:
                - PORT=9100
          
+           publisher:
+             image: ngerakines/tavern:0.1.0-rc2
+             restart: on-failure
+             networks:
+               - internal_network
+             healthcheck:
+               test: ["CMD-SHELL", "wget -q --spider --proxy=off localhost:9200 || exit 1"]
+               interval: 5m
+               timeout: 10s
+             ports:
+               - "9200:9200"
+             environment:
+               - LISTEN=0.0.0.0:9200
+               - PUBLISHER_CALLBACK=ttp://web:9000/webhooks/publisher
+         
            web:
              image: ngerakines/tavern:0.1.0-rc2
              restart: on-failure
@@ -122,7 +139,7 @@ Have the following things ready:
 
 8. Start the database and wait for it to become available.
 
-        $ docker-compose up -d db svger
+        $ docker-compose up -d db svger publisher
         $ docker-compose logs -f db
 
 9. Run database migrations.