Ashish
banner
ashish.ashish.co.ap.brid.gy
Ashish
@ashish.ashish.co.ap.brid.gy
hobby photographer, blogger, and software engineer based in amsterdam. i’m interested in the intersection of culture, and history.

🌉 bridged from ⁂ https://ashish.co/, follow @ap.brid.gy to interact
02.26 // January
ashish.co
January 11, 2026 at 5:14 AM
01.26 // January
ashish.co
January 4, 2026 at 5:01 AM
Glamorous Witness // Vondelkerk, Amsterdam
ashish.co
January 2, 2026 at 9:17 PM
Hollowed Ashes // Vondelkerk, Amsterdam
ashish.co
January 1, 2026 at 6:50 PM
The Afterparty, Vondelkerk 01.01.2026
ashish.co
January 1, 2026 at 11:21 AM
Waiting for the Tram // 24.12.2025
ashish.co
December 26, 2025 at 10:19 AM
_
ashish.co
December 20, 2025 at 9:33 AM
My Next Chapter
I am known for hyperbolic tendencies in my writing, and I hope you will forgive me on this occasion. I have some news to share. Something that has crept up on me, almost catching me by surprise. I’ve been involved every step of the way, don’t get me wrong; making the decisions leading up to this. But the achievement is now settling in… This website, this blog that I have been publishing on-and-off for about 15 years, is now a business. A digital magazine. On the 5th of this month, I had an appointment at the KVK, the Dutch Chamber of Commerce, and signed documents making it official. The paperwork itself is nothing to write home about, and there’s no approval necessary: I had to show up, verify my identity, and pay a fee. But from a personal perspective, it’s a milestone. I have aspired to be a writer for as long as I remember. This blog goes back to 2010, and has been through numerous iterations since teenage Ashish first began publishing. But it is the edition you’re reading right now which brings me the most pride. It is the culmination of years of effort and practice, and I have now become confident enough to not only put my name on my words, but also share more of my personality. To meet people, and confidently identify myself as a writer, and a publisher. My readership may be small, but I appreciate every single one of you. Thank you for being a part of my journey; I could not have done this without you. I hope to continue to use this platform to shine a light on the glittering facets of what it means to be human. Oh, and one more thing. As of 14h today, this website is listed in the annals of the _Koninklijke Bibliotheek_ , the National Library of The Netherlands. ISSN 3117-7409.
ashish.co
November 27, 2025 at 4:07 PM
Dots α
Amsterdam, NL
ashish.co
November 18, 2025 at 6:47 AM
Vibing with Autumn // 45.25
ashish.co
November 9, 2025 at 5:00 AM
08.11.2025
ashish.co
November 8, 2025 at 11:22 PM
Gasthuismolensteeg // 05.11.25
ashish.co
November 5, 2025 at 6:02 PM
Max Euweplein, Amsterdam | 27-10-25
ashish.co
November 2, 2025 at 9:02 AM
Lunch Break
ashish.co
November 1, 2025 at 12:39 PM
After the Storm
ashish.co
October 31, 2025 at 2:19 PM
Returning Home
ashish.co
October 31, 2025 at 10:28 AM
Four Microcars
ashish.co
October 30, 2025 at 8:25 PM
Autumn in Vondelpark
ashish.co
October 30, 2025 at 7:12 PM
Just an Alleyway
ashish.co
October 30, 2025 at 6:53 PM
GitHub Actions to Warm and Maintain your Website’s Cache
Most websites don’t need to warm their cache; regular traffic does the job. That first viewer might have to wait half a second longer, but it’s no big deal. In my case, that first viewer might be the only viewer I get. And I want them to have the best experience. A cool feature of GitHub Actions is that you can use them to create workflows that are odd cron jobs, run on schedule. This action is also automatically run after every deploy, so that first viewer never needs to wait. This simple script also complains when it fails, with a notification sent to my phone, which tells me that my website is not responding correctly. An uptime monitor, and a cache warmer. Two birds, one stone. name: Cache Warm on: schedule: - cron: '0 */2 * * *' workflow_run: workflows: ["Deploy"] types: [completed] branches: - master workflow_dispatch: concurrency: group: cache-warm cancel-in-progress: true permissions: contents: read jobs: cache-warm: runs-on: ubuntu-latest timeout-minutes: 2 if: github.event_name != 'workflow_run' || github.event.workflow_run.conclusion == 'success' steps: - run: | urls_to_warm=( "https://ashish.co/" "https://ashish.co/rss/" "https://ashish.co/sitemap.xml" ) curl_version=$(curl --version | head -n 1 | awk '{print $1"/"$2}') user_agent="ACacheWarmer/0.4 (+https://ashish.co; +https://github.com/${{ github.repository }}) ${curl_version}" for url in "${urls_to_warm[@]}"; do curl -fSs -o /dev/null -A "$user_agent" "$url" done
ashish.co
October 30, 2025 at 4:19 PM
43.25 // October
ashish.co
October 26, 2025 at 5:00 AM