I guess the benefit of piku comes with the ease of use for developers who don't know lots about system administration/infrastructure. Spinning up a server and installing a repo on it is easy. Depends on your use case…
Technology won't save us. Hoping that someday soon^tm someone will come up with something that makes all the current mess go away is a dangerous path. In germany they call it 'Technologieoffen' - and even some political…
Mine still runs happily on a PI Model B Plus with no downtime except for maintenance. Some DNS/Netwrk fallbacks on the DSL Router. Imho the risk/consequences of a downtime don't justify having some hardware draining…
I still miss browser bouncers: "Sorry kiddo. No Netscape in here. Boss created this stuff for IE only."
What happend to the good'ol sitemap.xml? You'll probably find an npm package with lots of dependencies that'll generate that sitemap for you if that's what you need...
I guess the benefit of piku comes with the ease of use for developers who don't know lots about system administration/infrastructure. Spinning up a server and installing a repo on it is easy. Depends on your use case…
Technology won't save us. Hoping that someday soon^tm someone will come up with something that makes all the current mess go away is a dangerous path. In germany they call it 'Technologieoffen' - and even some political…
Mine still runs happily on a PI Model B Plus with no downtime except for maintenance. Some DNS/Netwrk fallbacks on the DSL Router. Imho the risk/consequences of a downtime don't justify having some hardware draining…
I still miss browser bouncers: "Sorry kiddo. No Netscape in here. Boss created this stuff for IE only."
What happend to the good'ol sitemap.xml? You'll probably find an npm package with lots of dependencies that'll generate that sitemap for you if that's what you need...