# 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 35
# self = https://watcher.sour.is/conv/nd4ahlq
@prologic Well I built a clean build of yarnd and I can't replicate the -R problem either 🧐 Very strange, I guess something really strange happened in my first venture or I did something I can't recall. Sorry for putting you through extra testing! I do have some extra feedback I'll put down in a moment on the build process though that I encountered.
@prologic \n- The instructions given on the Yarn.social page works to build yarnd, but doesn't take care of setting the $version and $commit or building the minified css/js files. For this I used make as instructed on the git page.\n- The make generate part of the process fails with minify complaining about the -b flag. My minify doesn't have that option. (cont..)
@prologic \n- Removing the -b flag in the Makefile in minify works no problem, not sure what the -b flag does but it didn't affect anything.\n- Line 25 of Makefile should be ./cmd/yarnc/... not ./cmd/yarn/..., causes make to fail if building all including the cli target.
@prologic Can probably scratch the part about minify as I believe that's to do with how my Go environment is setup, the build process was using my system version of minify not the one pulled in by make deps :P
@eldersnake No worries! 👌
@eldersnake No worries! 👌
So I’ve broken the bucks there last night ooops 😥
So I’ve broken the bucks there last night ooops 😥
I was also lazy with the landing page😂 Lats did that! Mind giving l me a hand? 🙏
I was also lazy with the landing page😂 Lats did that! Mind giving l me a hand? 🙏
Err I meant to say I’ve broken the build 🤣
Err I meant to say I’ve broken the build 🤣
@prologic Whatcha need? I've never done a patch before but I'm sure it's not too hard.
@eldersnake Repo for that landing page is here

https://git.mills.io/adi/yarn.social

Not sure if you can edit from the Gitea interface itself and submit a patch that way?
@eldersnake Repo for that landing page is here

https://git.mills.io/adi/yarn.social

Not sure if you can edit from the Gitea interface itself and submit a patch that way?
@eldersnake Repo for that landing page is here\n\nhttps://git.mills.io/adi/yarn.social\n\nNot sure if you can edit from the Gitea interface itself and submit a patch that way?
@prologic Okay I'll have a look.
https://git.mills.io/yarnsocial/yarn.social/pulls/2



* 1dcc5ae 2021-09-22 | Fix Makefile (HEAD -> master, origin/master) [James Mills]
* cd8ef7d 2021-09-22 | Rename the Yarn command-line client to yarnc [James Mills]
\n\n
\n* 1dcc5ae 2021-09-22 | Fix Makefile (HEAD -> master, origin/master) [James Mills]\n* cd8ef7d 2021-09-22 | Rename the Yarn command-line client to yarnc [James Mills]\n



* 1dcc5ae 2021-09-22 | Fix Makefile (HEAD -> master, origin/master) [James Mills]
* cd8ef7d 2021-09-22 | Rename the Yarn command-line client to yarnc [James Mills]
@prologic Anything needed to update for Docker?

I had it working once, but for some reason the password manager I used to generate my password didn't save, so I couldn't log into my account. I purged, grabbed the repo again, and recreated my image but now I can't log in.

https://tt.vltra.plus/
@prologic Anything needed to update for Docker?\n\nI had it working once, but for some reason the password manager I used to generate my password didn't save, so I couldn't log into my account. I purged, grabbed the repo again, and recreated my image but now I can't log in.\n\nhttps://tt.vltra.plus/
@lazarus Jump on IRC and we’ll sort it out together? 🤗
@lazarus Jump on IRC and we’ll sort it out together? 🤗
@lazarus @prologic Cool domain!
@lazarus @prologic Cool domain!
@prologic Thanks, but I think I will have to save it for later or another day now :/
I have to get into some work now.

Btw, I had to change the docker-compose.yml to use dockerfile: Dockerfile and not dockerfile: Dockerfile.dev
@prologic Thanks, but I think I will have to save it for later or another day now :/\nI have to get into some work now.\n\nBtw, I had to change the docker-compose.yml to use dockerfile: Dockerfile and not dockerfile: Dockerfile.dev
@lazarus

> Btw, I had to change the docker-compose.yml to use dockerfile: Dockerfile and not dockerfile: Dockerfile.dev

Yes the docker-compose.yml is not _really_ designed for a "production" setup. The docker-stack.yml however is and is deployable to a Docker Swarm cluster or with modifications to just a machine with Docker.
@lazarus \n\n> Btw, I had to change the docker-compose.yml to use dockerfile: Dockerfile and not dockerfile: Dockerfile.dev\n\nYes the docker-compose.yml is not _really_ designed for a "production" setup. The docker-stack.yml however is and is deployable to a Docker Swarm cluster or with modifications to just a machine with Docker.
@lazarus

> Btw, I had to change the docker-compose.yml to use dockerfile: Dockerfile and not dockerfile: Dockerfile.dev

Yes the docker-compose.yml is not _really_ designed for a "production" setup. The docker-stack.yml however is and is deployable to a Docker Swarm cluster or with modifications to just a machine with Docker.
@lazarus

> Thanks, but I think I will have to save it for later or another day now :/
I have to get into some work now.

No worries bud 🤗
@lazarus \n\n> Thanks, but I think I will have to save it for later or another day now :/\nI have to get into some work now.\n\nNo worries bud 🤗
@lazarus

> Thanks, but I think I will have to save it for later or another day now :/
I have to get into some work now.

No worries bud 🤗