Skip to content

Sharkey

The source for sharkey can be on github. See also the projects landing page https://joinsharkey.org/.

You can install the Fediverse pasture via

git clone https://codeberg.org/helge/funfedidev.git
cd funfedidev/fediverse-pasture

Start sharkey via

docker compose --file sharkey.yml --profile nginx up

Once the application has started correctly, you have to create a user via the web UI. In order to do this, you need to add the following to /etc/hosts

/etc/hosts
127.0.0.1         sharkey_web

We recommend choosing the username admin and password password. Afterwards you can get an access token from

Settings -> API -> Generate Access Token -> Enable All -> Name pasture

By adding the token to the function sharkey_app, you can then run the support table method.

work.apps.sharkey_app(session) async

Source code in work/apps.py 
77
78
79
80
81
82
83
84
85
async def sharkey_app(session):
    app = await activity_for_firefish("sharkey_web", "admin", session)
    actor_uri = app.actor_uri
    app = await activity_for_mastodon(
        "sharkey_web", "admin", "q7lo8J3stiwxB6Qk4ezfe6ggyryAfZgx", session
    )
    app.actor_uri = actor_uri
    app.application_name = "sharkey"
    return app

Access Data

Property Value
User handle admin
Password password
Account URI acct:admin@sharkey_web

Configuration notes

The first two settings in

fediverse-pasture/sharkey.yml
environment:
    NODE_ENV: dev
    MK_VERBOSE: true
    MISSKEY_WEBFINGER_USE_HTTP: true

increase the level of logging. To reduce the console logging, set NOdE_ENV to production. The last setting ensures that one can use webfinger with http.

Second the patch fediverse-pasture/dockerfiles/sharkey/algo.patch is currently necessary to allow the Content digest to start with sha256= instead of SHA-256=.