- Be able to run services on _any_ node in my cluster and let Docker Swarm pick whatever node it likes (_instead of now where I have to pin some workloads to specific nodes, as that's where their local storage volume is_)
- Manage the scalability of data and growth over time instead of what I do now which is to extend EXT4 filesystems on my Docker Swarm nodes every few years.
- Be able to run services on _any_ node in my cluster and let Docker Swarm pick whatever node it likes (_instead of now where I have to pin some workloads to specific nodes, as that's where their local storage volume is_)
- Manage the scalability of data and growth over time instead of what I do now which is to extend EXT4 filesystems on my Docker Swarm nodes every few years.
yarns how to crawl and index archived feeds ๐ค
yarns how to crawl and index archived feeds ๐ค
$ curl 'https://twtxt.net/external?uri=https://google.com&nick=lovetocode999'
Feed Not Found
After nuking that from my cache. I forgot to nuke my own cache myself because it's quite destructive and takes a few mins to rebuild on my pod ๐คฃ There's a tool in
tools for deleting a specific feed from the cache that I've been using.
$ curl 'https://twtxt.net/external?uri=https://google.com&nick=lovetocode999'
Feed Not Found
After nuking that from my cache. I forgot to nuke my own cache myself because it's quite destructive and takes a few mins to rebuild on my pod ๐คฃ There's a tool in
tools for deleting a specific feed from the cache that I've been using.
/external endpoint/view is to refactor how it works a bit and add some HTMX magicโข so it has a nice snappy UX to it as it dynamically tries to validate the feed and provide useful feedback to the user, that way I can avoid injecting it into the cache unnecessarily in the first place!
/external endpoint/view is to refactor how it works a bit and add some HTMX magicโข so it has a nice snappy UX to it as it dynamically tries to validate the feed and provide useful feedback to the user, that way I can avoid injecting it into the cache unnecessarily in the first place!
https://google.com has been removed from the cache (_without nuking the entire cache_) @abucci if you need to selectively do this for some reason, there's a script in the tools directory for this:
$ ./tools/cache_delete_feed.sh 'https://google.com'
Anyway, that's gone. This is much much harder to exploit now, even if you're an authenticated user.
https://google.com has been removed from the cache (_without nuking the entire cache_) @abucci if you need to selectively do this for some reason, there's a script in the tools directory for this:
$ ./tools/cache_delete_feed.sh 'https://google.com'
Anyway, that's gone. This is much much harder to exploit now, even if you're an authenticated user.
text//plain content-type or b) it errored out and was a new fetch of a HTTP feed.