[{"data":1,"prerenderedAt":355},["ShallowReactive",2],{"articles-page-1":3},{"articles":4,"total":354},[5,57,102,146,182,233,277],{"path":6,"title":7,"description":8,"image":9,"createdAt":10,"authorKey":11,"tags":12,"codeLinks":19,"readingTime":23,"excerpt":24},"\u002Farticles\u002F20230404-vue3-toastify-inertia","Vue3-Toastify in a Laravel\u002FInertia\u002FVue project","Integrate vue3-toastify into VILT (Vue3, Inertia.js, Laravel, Tailwind) stack.","\u002Fimages\u002Fcovers\u002Fvue3-toastify-inertia.jpg","2023-04-04 00:35","philip",[13,14,15,16,17,18],"frontend","backend","vue.js","laravel","inertia.js","js",[20],{"link":21,"desc":22},"https:\u002F\u002Fgist.github.com\u002Fonlime\u002F4fc0e3e34dd54f0e70130419d93f125c","Gist",7,{"type":25,"value":26},"minimark",[27,42],[28,29,30,31],"p",{},"Need a full-featured toast notification component for your next Vue.js project? Don't look any further: ",[32,33,34,41],"strong",{},[35,36,40],"a",{"href":37,"rel":38},"https:\u002F\u002Fgithub.com\u002Fjerrywu001\u002Fvue3-toastify",[39],"nofollow","Vue3-Toastify"," beats it all!",[28,43,44,45,50,51,56],{},"Previously I have tried ",[35,46,49],{"href":47,"rel":48},"https:\u002F\u002Fvue-toastification.maronato.dev\u002F",[39],"Vue Toastification"," («Light, easy and beautiful toasts») and ",[35,52,55],{"href":53,"rel":54},"https:\u002F\u002Fszboynono.github.io\u002Fmosha-vue-toastify\u002F",[39],"Mosha Vue Toastify"," («A light weight and fun Vue 3 toast or notification or snack bar») but they are both kind of outdated and abandoned projects with latest releases dating back to prehistoric 2021. Let me show you how to integrate great looking and easy to use toast notifications into your VILT stack!",{"path":58,"title":59,"description":60,"image":61,"createdAt":62,"authorKey":11,"tags":63,"codeLinks":64,"readingTime":23,"excerpt":65},"\u002Farticles\u002F20220714-vue3-v-model-binding","Vue.js 3 v-model two-way data binding for Dummies","How to make your custom Vue 3 form components v-model capable.","\u002Fimages\u002Fcovers\u002Fvue3-v-model-binding.png","2022-07-14 12:00",[13,15,18],null,{"type":25,"value":66},[67,79,85],[28,68,69,70,74,75,78],{},"Vue ",[71,72,73],"code",{},"v-model"," is a directive that creates a two-way data binding between a value in our template and a value in our data properties, while ",[71,76,77],{},"v-bind"," only binds data one way. A common use case for using v-model is when designing forms and inputs.",[28,80,81,82,84],{},"While the core concept of ",[71,83,73],{}," is quite straightforward, you might struggle with it when building advanced custom form components. Personally, this was my main pain point when learning Vue, especially since there are so many different ways this can be handled and tutorials diverge quite a bit.",[28,86,87,88,95,96,98,99],{},"Vue's official ",[35,89,92,93],{"href":90,"rel":91},"https:\u002F\u002Fvuejs.org\u002Fguide\u002Fcomponents\u002Fevents.html#usage-with-v-model",[39],"Components In-Depth > Events > Usage with ",[71,94,73],{}," documentation only covers the most basic usage without providing any advanced examples. So I put together some use cases for you to learn more about ",[71,97,73],{},". The main question is: ",[32,100,101],{},"How can I make that custom component reusable so that it can be used as a form component with two-way data binding?",{"path":103,"title":104,"description":105,"image":106,"createdAt":107,"authorKey":11,"tags":108,"codeLinks":110,"readingTime":113,"excerpt":114},"\u002Farticles\u002F20220103-eslint-prettier-vue3","Configure ESLint and Prettier for Vue.js 3 in VS Code","Quick and dirty VS Code setup of ESLint and Prettier for your next Vue 3 project.","\u002Fimages\u002Fcovers\u002Fprettier.jpg","2022-01-03 17:30",[13,15,18,109],"vscode",[111],{"link":112,"desc":22},"https:\u002F\u002Fgist.github.com\u002Fonlime\u002F37cac1471fd33d8d6661187cd7b18d3a",4,{"type":25,"value":115},[116,143],[28,117,118,119,124,125,130,131,136,137,142],{},"I'd like to share my recommended ",[35,120,123],{"href":121,"rel":122},"https:\u002F\u002Feslint.org\u002F",[39],"ESLint"," and ",[35,126,129],{"href":127,"rel":128},"https:\u002F\u002Fprettier.io\u002F",[39],"Prettier"," configuration for a ",[35,132,135],{"href":133,"rel":134},"https:\u002F\u002Fv3.vuejs.org\u002F",[39],"Vue.js 3"," project. The two are not mutually exclusive – ESLint is for linting and Prettier handles code formatting. Believe me, you're going to use both! As preferred IDE, I am using ",[35,138,141],{"href":139,"rel":140},"https:\u002F\u002Fcode.visualstudio.com\u002F",[39],"VS Code",". This article is just considered as simple dev notes without digging any deeper, and it's based on my current \"best practices\".",[28,144,145],{},"We're going to install Prettier first and ensure it's running fine. After that, we're going to install ESLint which is a bit trickier and needs some fine-tuning so that it won't conflict with any rules that Prettier already handles.",{"path":147,"title":148,"description":149,"image":150,"createdAt":151,"authorKey":11,"tags":152,"codeLinks":155,"readingTime":113,"excerpt":158},"\u002Farticles\u002F20211203-laravel-mailer-log-eml","Log emails as *.eml in Laravel Mailer","Log complete email messages that are sent out by Laravel's Mailer.","\u002Fimages\u002Fcovers\u002Flaravel-mailer.jpg","2021-12-03",[16,153,14,154],"php","email",[156],{"link":157,"desc":22},"https:\u002F\u002Fgist.github.com\u002Fonlime\u002F79ec3693281066c5fa997e34bf05f00a",{"type":25,"value":159},[160],[28,161,162,163,166,167,175,176,181],{},"How to log full email messages into ",[71,164,165],{},"*.eml"," files on filesystem in your Laravel project? We would like to log full message bodies for all messages, no matter if they are sent out directly using Laravel's ",[35,168,171,174],{"href":169,"rel":170},"https:\u002F\u002Flaravel.com\u002Fdocs\u002F8.x\u002Fmail",[39],[71,172,173],{},"Mail"," facade"," or as ",[35,177,180],{"href":178,"rel":179},"https:\u002F\u002Flaravel.com\u002Fdocs\u002F8.x\u002Fnotifications#mail-notifications",[39],"Mail Notifications",". That can actually be implemented in a super easy way, but it was so hard to find any good documentation or tutorial about this.",{"path":183,"title":184,"description":185,"image":186,"createdAt":187,"authorKey":11,"tags":188,"codeLinks":193,"readingTime":196,"excerpt":197},"\u002Farticles\u002F20210915-fail2ban-apache-dos","Fail2ban jail to mitigate DoS attacks against Apache","Using a Fail2ban jail to mitigate simple DoS attacks against Apache.","\u002Fimages\u002Fcovers\u002Ffail2ban-apache-dos.jpg","2021-09-15",[189,190,191,192],"sysadmin","linux","security","fail2ban",[194],{"link":195,"desc":22},"https:\u002F\u002Fgist.github.com\u002Fonlime\u002Ff5108c23e9f4dfbb88fba2c9386cd219",5,{"type":25,"value":198},[199,226],[28,200,201,202,207,208,213,214,217,218,221,222,225],{},"Recently, one of our shared hosting webservers at ",[35,203,206],{"href":204,"rel":205},"https:\u002F\u002Fwww.onlime.ch\u002F",[39],"Onlime GmbH"," got hit by a DoS attack. The attacker started a larger vulnerability scan against common Wordpress security issues. We already had common brute-force attack patterns on Wordpress covered by a custom ",[35,209,212],{"href":210,"rel":211},"https:\u002F\u002Fwww.fail2ban.org",[39],"Fail2Ban"," jail, which mainly trapped ",[71,215,216],{},"POST"," requests to ",[71,219,220],{},"xmlrpc.php"," or ",[71,223,224],{},"wp-login.php"," (the usual dumb WP brute-force attacks...). But this DoS attack had hundreds of customer sites as target and did not get trapped by our existing rules.",[28,227,228,229,232],{},"After having blocked the attacker's IP (glad this was no large-scale DDoS!), I wrote an extra Fail2Ban jail which traps such simple DoS attacks. It's a very basic Fail2Ban jail that should cover common attacks and should not cause any false positives as it is only getting triggered by a large amount of failed ",[71,230,231],{},"GET"," requests.",{"path":234,"title":235,"description":236,"image":237,"createdAt":238,"authorKey":11,"tags":239,"codeLinks":64,"readingTime":196,"excerpt":243},"\u002Farticles\u002F20210901-gitlab-postgresql-recovery","GitLab PostgreSQL Data Recovery","Recovering PostgreSQL data for GitLab by a full dump\u002Frestore.","\u002Fimages\u002Fcovers\u002Fgitlab-meets-postgresql.png","2021-09-01",[189,190,240,241,242],"backup","gitlab","postgresql",{"type":25,"value":244},[245,262],[28,246,247,248,253,254,257,258,261],{},"Today, shit happened on a larger on-premise ",[35,249,252],{"href":250,"rel":251},"https:\u002F\u002Fabout.gitlab.com\u002F",[39],"GitLab EE"," instance of one of our ",[35,255,206],{"href":204,"rel":256},[39]," customers. GitLab's production.log started to fill up with ",[71,259,260],{},"PG::Error (FATAL: the database system is in recovery mode)"," errors which were somehow related to LFS operations. That definitely didn't sound cool and smelled like data corruption. The customer noticed it by failed CI jobs with 500 Internal Server Errors, and let me know immediately.",[28,263,264,265,270,271,276],{},"As we have that GitLab server running in a LXC container on a ",[35,266,269],{"href":267,"rel":268},"https:\u002F\u002Fopenzfs.org",[39],"ZFS"," based system (",[35,272,275],{"href":273,"rel":274},"https:\u002F\u002Fproxmox.com\u002Fen\u002Fproxmox-ve",[39],"Proxmox VE","), it was easy to pull a clone of the full system and play around with PostgreSQL data recovery before working on live data. I decided to go for a full data restore by dumping and loading it from scratch in a freshly initialized PostgreSQL data dir.",{"path":278,"title":279,"description":280,"image":281,"createdAt":282,"authorKey":11,"tags":283,"codeLinks":285,"readingTime":292,"excerpt":293},"\u002Farticles\u002F20210830-algolia-vue-instantsearch","Integrate Algolia InstantSearch into a Vue Project","Integrate Algolia InstantSearch into a Vue project using Nuxt\u002Fcontent.","\u002Fimages\u002Fcovers\u002Falgolia-vue-instantsearch.png","2021-08-30",[13,15,284,18],"nuxt.js",[286,289],{"link":287,"desc":288},"https:\u002F\u002Fgitlab.com\u002Fonlime\u002Fdemo\u002Fnuxt-content-blog","nuxt-content-blog",{"link":290,"desc":291},"https:\u002F\u002Fdemo.pipo.blog\u002F","Demo",11,{"type":25,"value":294},[295,326],[28,296,297,298,303,304,309,310,315,316,321,322,325],{},"This TechBlog is based on ",[35,299,302],{"href":300,"rel":301},"https:\u002F\u002Fvuejs.org\u002F",[39],"Vue.js"," & ",[35,305,308],{"href":306,"rel":307},"https:\u002F\u002Fnuxtjs.org\u002F",[39],"Nuxt.js",", using ",[35,311,314],{"href":312,"rel":313},"https:\u002F\u002Fcontent.nuxtjs.org\u002F",[39],"nuxt\u002Fcontent"," as a Git-based headless CMS, ",[35,317,320],{"href":318,"rel":319},"https:\u002F\u002Ftailwindcss.com\u002F",[39],"Tailwind CSS"," for styling. Today, we want to talk about full-text search integration. ",[35,323,314],{"href":312,"rel":324},[39]," actually has a built-in search which indexes your pages\u002Farticles and does full-text lookups that are super easy to integrate. But I had quite a bad experience with it, content search delivering wrong search results (that did not even contain the query string or anything similar at all), and making it hard to extract a snippet of surrounding words\u002Fsentences of the search results.",[28,327,328,333,334,339,340,124,345,349,350,353],{},[35,329,332],{"href":330,"rel":331},"https:\u002F\u002Fwww.algolia.com\u002F",[39],"Algolia"," offers a super powerful and flexible search with ready to use ",[35,335,338],{"href":336,"rel":337},"https:\u002F\u002Fwww.algolia.com\u002Fproducts\u002Fsearch-and-discovery\u002Fui-component-libraries\u002F",[39],"InstantSearch"," UI components for ",[35,341,344],{"href":342,"rel":343},"https:\u002F\u002Freactjs.org\u002F",[39],"React",[35,346,348],{"href":300,"rel":347},[39],"Vue",". It was quite easy to write my own ",[71,351,352],{},"AlgoliaSearch"," component for this blog, but Algolia's InstantSearch defaults were so horribly resource-hungry and it took me a while to figure out how to fine-tune this.",29,1794781277524]