but deleting post is working tho π€
π₯² Somehow my update post function is not working again.
Interesting problem of Next.JS SSG (or any SSG I guess) when number of pages that we want to generate is too many (let say million of it) causing the disk full. I guess we shouldn't treat SSG or ISR as a cache like what's Vercel promoted it for because it doesn't have any limit boundary on the number or size of this type of storage at all.
π€ Maybe it's time to move my blog api out of Vercel too.
bike.shimano.com/nl-NL/productβ¦ 5 titanium, 6 steel or recon-harry.com.tw/products_deβ¦ 10 titanium, 1 steel π€
but Recon doesn't have 11-30 π₯²
Cleaning my bike today and spot my cassette has some rust on it π₯²
Maybe it's time to change it after 30,000 km. π
Caught on a camera for a second π
Need an option to disable markdown when posting. π
and 4,000 cyclist π€―
16,000 runner on last sundy π€―
One of a good morning spring in Amsterdam βοΈπ±
After a bad horrible weekend which I have cycling event. It's sunny and not windy today π©
28 days! π± this is quite a long break
I think there are a lot of cycling events here than in Singapore and it's quite cheap ~β¬20. In Singapore if I want to cycling like today it's usually around S$100+
Just finished the ride today for 100km. It's one of the Le Champion event which I usually join since Dam to Dam two years ago.
Probably try again next year if the weather is not so bad like this year but I did say that for dam tot dam too which I still join for two years now even though the weather was horrible both year (less than Omloop tho)
Heading back to Amsterdam π
Itβs the worst day coming to Zandvoort but I finished it!
100km with 43kph wind speed average and 70kph gust speed.
Today train to Zandvoort is packed with bikes!
Ready? Nope π¬
The sad thing is the weather is getting cold this weekend π₯²
Maybe it's time to rewrite my storage to use Firestore batch get. Each query is around 100ms which is not much but multiply it with number of status in timeline making it's a bit too much to wait for all result return.
One thing tho, Google Cloud Trace is quite nice. Switch the exporter to cloud trace and done. (Will try to not looking at my billing yet π)
Latency doesn't get better much tho π₯²
That's actually a main goal why moving to Cloud Run, expecting that Firestore will be a bit faster here.
π€ Cloud Run day 1, max memory ~310MB but average at around 256MB. CPU is also around 50%
I will go back to Thailand next month but the Cloud Run is deployed in Europe region. Wondering how slow it will be. π€
Upload image feels faster but will need to increase the limit.
Last weekend with trailer!
Especially, when I post after I don't open the page for sometime.
π€ With almost one container always run. It feels a bit faster with Cloud Run vs Vercel.
β Move all domains to Cloud Run. π Vercel pro
Actually, Cloud Run supports apex mapping!
π€ Still have root domain with Vercel which Cloud Run domain mapping doesn't seem to support. Not sure yet how to migrate the last domain to GCP.
One option is, having a CDN/API Gateway/Load Balancing in front of the Cloud Run I guess.