Here’s an high-level overview of local storage, popular options to get started on local storage in Vue, and how to choose an option that works for you. Local Storage and Browsers Browsers are windows to your web application. While it is easier to manage data access on your own servers, super secure and all, getting users to connect to the server for each and every task can be tiring and lead to a bad user experience.
In this post let us see how we can leverage the power of Express with a sprinkling of Alpine JS to create a quick URL shortener application. But, why? Express is the most popular server-side framework and my “go to” choice for creating anything really quick. Building a front-end for Express is as easy as using handlebars (or anything really) that goes in HTML served by Express.
I recently had to pick up an old project on Wordpress and deploy the site on a CPanel server. So, I thought it was just the right time to document the steps needed to migrate Wordpress site from one host to the other, or from one domain to the other. While there are references to CPanel, the migration is almost the same for any control panels (or even when you don’t use one).
I switched to Caddy recently on one of our servers to host multiple applications and am super happy about its simplicity and ease of use. Here’s how I use Caddy with Quasar. What is Caddy? Caddy is a web server much like Nginx. It calls itself “a new kind of extensible platform for server apps”.
I create virtual private servers at least 8-12 times an year for client and personal projects. The steps to go live remain the same - Get a cheapo VPS on Digital Ocean, Vultr (get $100 credit), Hetzner, OVH, and friends - I end up choosing Ubuntu as the OS Secure your server Setup app server, database server and tools Stitch together various components through configuration files I have thought about switching to Docker (or Caprover) for months, but keep putting off any kind of automation.
WSL2 was released yesterday along with Windows10 May 2020 update (v2004). WSL2 enables to work with Linux kernels within Windows, and it brings some crazy possibilities for those of us who refuse to dual boot or switch over completely to Linux. I am assuming that you already have installed Windows v2004 through the normal Windows update channel, or through the update assistant.
I had to work on a MVP where there were specific instructions to use Vue directly from a CDN. The Vue build available in this way is also called UMD (Universal Module Definition) build since you can use Vue from anywhere and the project does not need specific setup to build and package your code.
Here’s a quick way to use Vue plugins in Quasar. Use Case: Frappe Charts in Vue Let’s consider a simple use case for using Vue plugins - we want to use Frappe charts. We can simply use vue2-frappe to easily do that. Just install the package in your project -
Quasar CLI structures project differently as compared to a standard Vue CLI app. As a result, you cannot just follow examples on the Internets blindly and use Vue.use(), or start changing code in main.js. There are, however, great ways of addressing the same problems with slightly different solutions. Enter boot files.
Here’s a quick demo of how you can convert XML to JSON in NodeJS. Problem You are given a slew of XML files and you have to convert them to JSON. But why JSON? It takes lesser space Faster and easier to work with What are we dealing with here?
Quasar is great. But, it is also a bit different when it comes to accessing the Vuex store from your code. Why is Quasar any different? “Is it not just Vue?” Well, yes. But.. the project structure created by Quasar CLI differs from a “normal” that by Vue CLI. Quasar CLI builds on top of Vue as well but may not follow similar practices to other frameworks / libraries using Vue.