# 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 28
# self = https://watcher.sour.is/conv/c6kechq
lohn
tw.lohn.in
View Thread
5. I learned a lot of Hugo looking as other's solutions. Do you have some other theme option for #mkws?
adi
twtxt.net
View Thread
@lohn

> I learned a lot of Hugo looking as otherโ€™s solutions. Do you have some other theme option for #mkws?

For now I have all the source files also on https://mkws.sh/ and https://adi.onl (s/html/upphtml/g in urls, e.g. https://mkws.sh/index.html https://mkws.sh/index.upphtml, https://mkws.sh/docs.upphtml) maybe @eldersnake could also give you his sources, he was also very satisfied, the other weren't so brave. ๐Ÿ˜›

I recommend distributing the sources of the website, you can hide sensitive information in environment variables.
adi
twtxt.net
View Thread
@lohn \n\n> I learned a lot of Hugo looking as otherโ€™s solutions. Do you have some other theme option for #mkws?\n\nFor now I have all the source files also on https://mkws.sh/ and https://adi.onl (s/html/upphtml/g in urls, e.g. https://mkws.sh/index.html https://mkws.sh/index.upphtml, https://mkws.sh/docs.upphtml) maybe @eldersnake could also give you his sources, he was also very satisfied, the other weren't so brave. ๐Ÿ˜›\n\nI recommend distributing the sources of the website, you can hide sensitive information in environment variables.
adi
f.adi.onl
View Thread
@lohn \n\n> I learned a lot of Hugo looking as otherโ€™s solutions. Do you have some other theme option for #mkws?\n\nFor now I have all the source files also on https://mkws.sh/ and https://adi.onl (s/html/upphtml/g in urls, e.g. https://mkws.sh/index.html https://mkws.sh/index.upphtml, https://mkws.sh/docs.upphtml) maybe @eldersnake could also give you his sources, he was also very satisfied, the other weren't so brave. ๐Ÿ˜›\n\nI recommend distributing the sources of the website, you can hide sensitive information in environment variables.
adi
f.adi.onl
View Thread
@adi @eldersnake @lohn \n\n> Any thing about internationalization? Make #mkws runs in multiple languages and generate multilanguage content?\n\nDidn't get to that yet! It's not that hard! You could use the https://www.gnu.org/software/gettext/ utilities. I, personally, would/will write a CLI version of https://man.openbsd.org/catgets
adi
twtxt.net
View Thread
@adi @eldersnake @lohn

> Any thing about internationalization? Make #mkws runs in multiple languages and generate multilanguage content?

Didn't get to that yet! It's not that hard! You could use the https://www.gnu.org/software/gettext/ utilities. I, personally, would/will write a CLI version of https://man.openbsd.org/catgets
adi
twtxt.net
View Thread
@adi @eldersnake @lohn \n\n> Any thing about internationalization? Make #mkws runs in multiple languages and generate multilanguage content?\n\nDidn't get to that yet! It's not that hard! You could use the https://www.gnu.org/software/gettext/ utilities. I, personally, would/will write a CLI version of https://man.openbsd.org/catgets
adi
twtxt.net
View Thread
@adi @lohn @eldersnake

> A common practice in SSG is to separate the code/content/siteready. As I understand now, #mkws puts almost everything in the root dir. There is a way to separate those things?

You could do, assuming mkws is in your $PATH, do something like:

MKWSTHEMEDIR=/path/to/share/dir mkws https://example.com /path/to/src/dir

It would get you the output in the current directory tho.

You could also just output elsewhere from bin/mkws.

I however recommend publishing the sources also, keeping sensitive info in ENV vars.=
adi
f.adi.onl
View Thread
@adi @lohn @eldersnake \n\n> A common practice in SSG is to separate the code/content/siteready. As I understand now, #mkws puts almost everything in the root dir. There is a way to separate those things?\n\nYou could do, assuming mkws is in your $PATH, do something like:\n\n MKWSTHEMEDIR=/path/to/share/dir mkws https://example.com /path/to/src/dir\n\nIt would get you the output in the current directory tho.\n\nYou could also just output elsewhere from bin/mkws.\n\nI however recommend publishing the sources also, keeping sensitive info in ENV vars.=
adi
twtxt.net
View Thread
@adi @lohn @eldersnake \n\n> A common practice in SSG is to separate the code/content/siteready. As I understand now, #mkws puts almost everything in the root dir. There is a way to separate those things?\n\nYou could do, assuming mkws is in your $PATH, do something like:\n\n MKWSTHEMEDIR=/path/to/share/dir mkws https://example.com /path/to/src/dir\n\nIt would get you the output in the current directory tho.\n\nYou could also just output elsewhere from bin/mkws.\n\nI however recommend publishing the sources also, keeping sensitive info in ENV vars.=
adi
f.adi.onl
View Thread
@adi @lohn @eldersnake Thanks for the questions @lohn! Looking forward to continuing the conversation, but I'm out for tonight as I'm beat! ๐Ÿ›Œ๐Ÿ˜ด
adi
twtxt.net
View Thread
@adi @lohn @eldersnake Thanks for the questions @lohn! Looking forward to continuing the conversation, but I'm out for tonight as I'm beat! ๐Ÿ›Œ๐Ÿ˜ด
adi
twtxt.net
View Thread
@adi @lohn @eldersnake Before I go, I have some other stuff you could look at at https://mkws.sh/bin/dv, _dev_ script, starts a simple webserver https://mkws.sh/https/https.go, uses https://livejs.com/ for live reloading and https://eradman.com/entrproject/ for file monitoring.
adi
f.adi.onl
View Thread
@adi @lohn @eldersnake Before I go, I have some other stuff you could look at at https://mkws.sh/bin/dv, _dev_ script, starts a simple webserver https://mkws.sh/https/https.go, uses https://livejs.com/ for live reloading and https://eradman.com/entrproject/ for file monitoring.
adi
f.adi.onl
View Thread
@adi @lohn @eldersnake Linting https://mkws.sh/bin/precommit, deploy script https://mkws.sh/bin/up.
adi
twtxt.net
View Thread
@adi @lohn @eldersnake Linting https://mkws.sh/bin/precommit, deploy script https://mkws.sh/bin/up.
adi
f.adi.onl
View Thread
@lohn @eldersnake @adi Stuff has some comments and may be a little broken (from the unpublished stuff I showed you) because I added selectively serving .gz, .br, uncompressed files tonight so it's a good idea to fix some scripts.
adi
twtxt.net
View Thread
@lohn @eldersnake @adi Stuff has some comments and may be a little broken (from the unpublished stuff I showed you) because I added selectively serving .gz, .br, uncompressed files tonight so it's a good idea to fix some scripts.
lohn
tw.lohn.in
View Thread
@adi @eldersnake Just to note, I'm developing using the tools you recommended (dv+http.go+live.js). Easy Peasy.
adi
f.adi.onl
View Thread
@lohn @eldersnake I really have to package dv, live.js, https.go nicely some day.
adi
twtxt.net
View Thread
@lohn @eldersnake I really have to package dv, live.js, https.go nicely some day.
mckinley
twtxt.net
View Thread
@adi @lohn @eldersnake I put Live.js in a userscript for http://127.0.0.1:1337 and it works like a charm
mckinley
twtxt.net
View Thread
@adi @lohn @eldersnake I put Live.js in a userscript for http://127.0.0.1:1337 and it works like a charm
mckinley
twtxt.net
View Thread
@adi @lohn @eldersnake I put Live.js in a userscript for http://127.0.0.1:1337 and it works like a charm
mckinley
twtxt.net
View Thread
@adi @lohn @eldersnake I put Live.js in a userscript for http://127.0.0.1:1337 and it works like a charm
mckinley
twtxt.net
View Thread
@adi @lohn @eldersnake I put Live.js in a userscript for http://127.0.0.1:1337 and it works like a charm
adi
f.adi.onl
View Thread
@mckinley @lohn @eldersnake Yeah, live.js is pretty cool.
adi
twtxt.net
View Thread
@mckinley @lohn @eldersnake Yeah, live.js is pretty cool.