# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 18
# self = https://watcher.sour.is/conv/choqthq
adi
twtxt.net
View Thread
I wonder why

> doas /usr/local/bin/python3.8 -m synapse.app.homeserver -c /var/synapse/homeserver.yaml --generate-config --server-name=adi.onl --repor t-stats=no

generates paths with the current directory in it.
adi
twtxt.net
View Thread
@adi @jlj Ideas?
adi
f.adi.onl
View Thread
@adi @jlj Ideas?
adi
twtxt.net
View Thread
@adi @jlj Also, @lohn?
adi
f.adi.onl
View Thread
@adi @jlj Also, @lohn?
jlj
twt.nfld.uk
View Thread
@adi @lohn H'm... Strange. I did play with their Matrix<>IRC bridge code for a bit, so I'm not completely unfamiliar with that means of invoking it, but, for my homeserver, for example, I'm just running it through synctl, which does actually look for all the yaml config, etc. in the current working directory.\n\nI'll be interested to see how you get on, though, as I'm also looking to run Synapse on OpenBSD in the near future, for IRCNow.org.
lohn
tw.lohn.in
View Thread
@adi @jlj I'm not so sure, but the -c doesn't have to be --config-path?
lohn
tw.lohn.in
View Thread
@adi @jlj I'm guessing by memory. As I meant before I use the spantaleev ansible version because I'm lazy.
adi
twtxt.net
View Thread
@lohn @jlj usage: homeserver.py [-h] [-c CONFIG_FILE] [--generate-config] [--generate-missing-configs] [-H SERVER_NAME]
[--report-stats {yes,no}] [--config-directory DIRECTORY] [--data-directory DIRECTORY]
[--open-private-ports] [-D] [--print-pidfile] [--manhole PORT] [-d SQLITE_DATABASE_PATH] [-n]
[--enable-registration]

Guess I'll have to use those directory options.
adi
f.adi.onl
View Thread
@lohn @jlj usage: homeserver.py [-h] [-c CONFIG_FILE] [--generate-config] [--generate-missing-configs] [-H SERVER_NAME]
[--report-stats {yes,no}] [--config-directory DIRECTORY] [--data-directory DIRECTORY]
[--open-private-ports] [-D] [--print-pidfile] [--manhole PORT] [-d SQLITE_DATABASE_PATH] [-n]
[--enable-registration]
\nGuess I'll have to use those directory options.
adi
twtxt.net
View Thread
@lohn @jlj usage: homeserver.py \n \n \n \n \n
\n \n \n
\n \n \n \n \n \n
\n

Guess I'll have to use those directory options.
adi
twtxt.net
View Thread
@lohn @jlj usage: homeserver.py [-h] [-c CONFIG_FILE] [--generate-config] [--generate-missing-configs] [-H SERVER_NAME]
[--report-stats {yes,no}] [--config-directory DIRECTORY] [--data-directory DIRECTORY]
[--open-private-ports] [-D] [--print-pidfile] [--manhole PORT] [-d SQLITE_DATABASE_PATH] [-n]
[--enable-registration]
\nGuess I'll have to use those directory options.
lohn
tw.lohn.in
View Thread
@adi @jlj (#choqthq) Ok, I removed the dust from my python install and made some tests.\nYou have to use --config-directory and --data-directory when generate config or it will fallback to current dir.
lohn
tw.lohn.in
View Thread
@lohn @adi @jlj --config-directory will hold the crypto keys, the log config and eventually other future configs.\n--data-directory will hold the PID, the database (of you use SQLite), and the media store.
adi
twtxt.net
View Thread
@lohn @jlj I'm just tempted to put everything in /var/synapse'.
adi
f.adi.onl
View Thread
@lohn @jlj I'm just tempted to put everything in /var/synapse.
adi
twtxt.net
View Thread
@lohn @jlj I'm just tempted to put everything in /var/synapse.
lohn
tw.lohn.in
View Thread
@jlj @adi sincerely, in mine, everything is under /matrix