alemi/aioappsrv
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: added readme

Browse source
This commit is contained in:
əlemi 2024-01-31 05:08:37 +01:00
parent 822a6426ab
commit 7b385e3103
Signed by: alemi
GPG key ID: A4895B84D311642C
1 changed files with 34 additions and 99 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

133
README.md
View file

@ -1,111 +1,46 @@
## Installation # aioappsrv
a tiny async library made with aiohttp to build matrix automation using its appservice api
`pip install -r requirements.txt`
## Usage
* Run `main.py` to generate `appservice.json`
* Edit `appservice.json`:
## installation
currently not on PyPI, clone this repo and pip install it:
``` ```
{ git clone https://git.alemi.dev/aioappsrv
"as_token": "my-secret-as-token", cd aioappsrv
"hs_token": "my-secret-hs-token", pip install .
"user_id": "appservice-discord",
"homeserver": "http://127.0.0.1:8008",
"server_name": "localhost",
"discord_token": "my-secret-discord-token",
"port": 5000,
"database": "/path/to/bridge.db"
}
``` ```
`as_token`: The token sent by the appservice to the homeserver with events. ## usage
you should first instantiate an AppService object providing `as`/`hs` tokens and your homeserver url:
```python
from aioappsrv.app import AppService
`hs_token`: The token sent by the homeserver to the appservice with events. app = AppService(
homeserver="matrix.org",
`user_id`: The username of the appservice user, it should match the `sender_localpart` in `appservice.yaml`. as_token="YOUR-APPSERVICE-TOKEN",
hs_token="YOUR-HOMESERVER-TOKEN",
`homeserver`: A URL including the port where the homeserver is listening on. The default should work in most cases where the homeserver is running locally and listening for non-TLS connections on port `8008`. )
`server_name`: The server's name, it is the part after `:` in MXIDs. As an example, `kde.org` is the server name in `@testuser:kde.org`.
`discord_token`: The Discord bot's token.
`port`: The port where `bottle` will listen for events.
`database`: Full path to the bridge's database.
Both `as_token` and `hs_token` MUST be the same as their values in `appservice.yaml`. Their value can be set to anything, refer to the [spec](https://matrix.org/docs/spec/application_service/r0.1.2#registration).
* Create `appservice.yaml` and add it to your homeserver:
```
id: "discord"
url: "http://127.0.0.1:5000"
as_token: "my-secret-as-token"
hs_token: "my-secret-hs-token"
sender_localpart: "appservice-discord"
namespaces:
users:
- exclusive: true
regex: "@_discord.*"
- exclusive: true
regex: "@appservice-discord"
aliases:
- exclusive: true
regex: "#_discord.*"
rooms: []
``` ```
The following lines should be added to the homeserver configuration. The full path to `appservice.yaml` might be required: to execute actions use AppService's helper methods:
```python
* `synapse`: mxid = "@_appsrv_firstuser:matrix.org"
room = "#my-epic-room:matrix.org"
``` await app.register_mxid(mxid)
# A list of application service config files to use await app.set_nick(mxid, "First User")
# await app.invite_to_room(room, mxid)
app_service_config_files: await app.join_room(room, mxid)
- appservice.yaml await app.send_message(room, "<b>hello world!</b>")
``` ```
* `dendrite`: to subscribe to room events use the callback decorator:
```python
from aioappsrv.matrix import Event
``` room = "#my-epic-room:matrix.org"
app_service_api: @app.callback(room)
internal_api: async def my_cb(event: Event):
# ... print(f"{event.sender}: {event.content['body']}")
database:
# ...
config_files: [appservice.yaml]
``` ```
A path can optionally be passed as the first argument to `main.py`. This path will be used as the base directory for the database and log file. ## state
this is quite early in development, i want to keep the general usage flow of this but don't get attached to import paths because they will change (:
Eg. Running `python3 main.py /path/to/my/dir` will store the database and logs in `/path/to/my/dir`.
`$PWD` is used by default if no path is specified.
After setting up the bridge, send a direct message to `@appservice-discord:domain.tld` containing the channel ID to be bridged (`!bridge 123456`).
This bridge is written with:
* `bottle`: Receiving events from the homeserver.
* `urllib3`: Sending requests, thread safety.
* `websockets`: Connecting to Discord. (Big thanks to an anonymous person "nesslersreagent" for figuring out the initial connection mess.)
## NOTES
* A basic sqlite database is used for keeping track of bridged rooms.
* Discord users can be tagged only by mentioning the dummy Matrix user, which requires the client to send a formatted body containing HTML. Partial mentions are not used to avoid unreliable queries to the websocket.
* Logs are saved to the `appservice.log` file in `$PWD` or the specified directory.
* For avatars to show up on Discord, you must have a [reverse proxy](https://github.com/matrix-org/dendrite/blob/master/docs/nginx/monolith-sample.conf) set up on your homeserver as the bridge does not specify the homeserver port when passing the avatar url.
* It is not possible to add "normal" Discord bot functionality like commands as this bridge does not use `discord.py`.
* [Privileged Intents](https://discordpy.readthedocs.io/en/latest/intents.html#privileged-intents) for members and presence must be enabled for your Discord bot.
* This Appservice might not work well for bridging a large number of rooms since it is mostly synchronous. However, it wouldn't take much effort to port it to `asyncio` and `aiohttp` if desired.