update beeper-linkedin 0.5.3 -> 0.5.4

development
Aine 2 years ago
parent f731bcb5eb
commit 8b2a86e35e
No known key found for this signature in database
GPG Key ID: 34969C908CCA2804

@ -4,7 +4,7 @@
matrix_beeper_linkedin_enabled: true
matrix_beeper_linkedin_version: v0.5.3
matrix_beeper_linkedin_version: v0.5.4
# See: https://github.com/beeper/linkedin/pkgs/container/linkedin
matrix_beeper_linkedin_docker_image: "{{ matrix_beeper_linkedin_docker_image_name_prefix }}beeper/linkedin:{{ matrix_beeper_linkedin_docker_image_tag }}"
@ -27,6 +27,8 @@ matrix_beeper_linkedin_appservice_address: "http://matrix-beeper-linkedin:29319"
matrix_beeper_linkedin_bridge_presence: true
matrix_beeper_linkedin_bridge_space_support_enable: true
matrix_beeper_linkedin_command_prefix: "!li"
matrix_beeper_linkedin_bridge_permissions: |

@ -88,15 +88,15 @@ manhole:
# Bridge config
bridge:
# Localpart template of MXIDs for LinkedIn users.
# {userid} is replaced with the user ID of the LinkedIn user
username_template: "linkedin_{userid}"
# Displayname template for LinkedIn users.
# Localpart template for per-user room grouping community IDs.
# The bridge will create these communities and add all of the specific user's portals to the community.
# {localpart} is the MXID localpart and {server} is the MXID server part of the user.
# (Note that, by default, non-admins might not have your homeserver's permission to create
# communities. You should set `enable_group_creation: true` in homeserver.yaml to fix this.)
# `linkedin_{localpart}={server}` is a good value.
community_template: null
# Settings for creating a space for every user.
space_support:
# Whether or not to enable creating a space per user and inviting the
# user (as well as all of the puppets) to that space.
enable: {{ matrix_beeper_linkedin_bridge_space_support_enable|to_json }}
# The name of the space
name: "LinkedIn"
# Displayname template for LinkedIn users.
# {displayname} is replaced with the display name of the LinkedIn user

Loading…
Cancel
Save