HEAD
per ~5mins + 1 GET
if your feed has changed_) _may_ hit your PageKite rate limits? π€ I'm not sure... Maybe... It's sometime to optimize, which I'm hoping to learn from the experience of the Yarns search engine crawler over time and re-integrate the same logic into Yarn pods. π€~
HEAD
per ~5mins + 1 GET
if your feed has changed_) _may_ hit your PageKite rate limits? π€ I'm not sure... Maybe... It's sometime to optimize, which I'm hoping to learn from the experience of the Yarns search engine crawler over time and re-integrate the same logic into Yarn pods. π€~
txtxt.txt
file is π€ I did a find
everywhere, lol!
$ ./yarnd -D -R 2>&1 | grep 'Open Registrations'
time="2021-09-18T14:29:36+10:00" level=info msg="Open Registrations: true"
Are you positive it was ignoring the flag? π€ What was the symtpoms?
\n$ ./yarnd -D -R 2>&1 | grep 'Open Registrations'\ntime="2021-09-18T14:29:36+10:00" level=info msg="Open Registrations: true"\n
\n\nAre you positive it was ignoring the flag? π€ What was the symtpoms?
$ ./yarnd -D -R 2>&1 | grep 'Open Registrations'
time="2021-09-18T14:29:36+10:00" level=info msg="Open Registrations: true"
Are you positive it was ignoring the flag? π€ What was the symtpoms?
> The main thing I canβt work out for the life of me is where the raw user txtxt.txt file is π€ I did a find everywhere, lol!
In the
data
directory, which is controlled by the -d/--data
flag or DATA
env var. π
data
directory, which is controlled by the -d/--data
flag or DATA
env var. π
> The main thing I canβt work out for the life of me is where the raw user txtxt.txt file is π€ I did a find everywhere, lol!
In the
data
directory, which is controlled by the -d/--data
flag or DATA
env var. π
yarnd
it would report registrations as being closed and saying neither of the flags were supplied (they were). And sure enough it was showing as closed on the actual webpage. Changing the default in options.go
let me register my account, and then turning off Open Registrations in Pod Settings worked to turn if off again.
open_registrations: true
in settings.yaml also wouldn't work unless the default was compiled to true in options.go
first, but it respects it being turned true|false afterwards. Hmm.