Watch out! It’s the Angular Thought Police!

So, yesterday I was visiting Angular’s discord server, because after a little over a month with Vue I was missing Angular’s components and way to express event listeners and 2-way binding of variables as well as the class based approach.
Vue2 is a simple, super productive framework, especially with Quasar, with a rich ecosystem and excellent libraries like vuex-orm, which is really fantastic, mind blowing.
It’s not perfect, nothing in this world is. The same way that Angular isn’t perfect or React or Svelte.
The worst part of Angular is the forced rxjs, if you’re doing anything more complex than a Hello World application anyway.
Continue reading “Watch out! It’s the Angular Thought Police!”

Keycloak-js client with Quasar (now updated for v2)

So you’d like to use openid-connect (oidc), especially keycloak (kc) in your Quasar app.

There’s a package, @dsb-norge/vue-keycloak-js . I’d recommend you fork it and create your own version with the keycloak-js version that matches your Keycloak server. However it also works with just the version used in this git repository.

The git repository is available at
https://github.com/dsb-norge/vue-keycloak-js

This is for Quasar v1

Alright let’s get started.

1. Create a file named silent-check-sso.html with the following content:

Put that file in the public directory as its path is
public/silent-check-sso.html.

2. Create boot/keycloak.js

3. Reference the created boot file in quasar.conf.js

And that’s really all there is to it.

After this is done you can access the keycloak object via $keycloak in your template.

This is for Qusasar v2:

Thanks a bunch to Excel1 and yusufkandemir for figuring it out.

First you have to upgrade or use the v2 branch of @dsb-norge/vue-keycloak-js.
e.g. npm i @dsb-norge/vue-keycloak-js@2
or use your own fork

But essentially you do whatever you would do for v1 only the boot/keycloak.js file is different

The boot/keycloak.js file

and of course don’t forget to add it to the boot array in quasar.conf.js

vue dev server with nginx

The Nginx conf is the same for any sock-js site. It can be used for Vue and Angular and Svelte, not sure about React but I’d guess it uses sock-js as well.

My dev domain is qxdsladmin.local in this example.

/etc/nginx/conf.d/qxdsladmin.local.conf

This location ~ ^/api/v1/.* is a mountpoint for the backend http api, which in my case is a RESTful Go API.

The vue part, create a file named vue.config.js in the project’s root dir.
So if you used vue create vxdsladmin it’s the directory you go to when doing cd vxdsladmin.

This works for me, but maybe it can be improved. Let me know if that’s the case.

There is not a single proper database

I’m so tired of it.
I’m using MongoDB and you can store files, great. But the Go driver, the official one sucks.
And the mgo driver is abandoned. The official driver is also slow, slower than Postgresql. 3.2ms for querying a dataset of 5k entries and another {“_id”: {“$in”: [“list”, “of”, “objectids”]}} that’s 1-20 long and 3 on average?
Compared to PHP that’s lightning fast I guess, but for Go standards it isn’t.

There is not one single database system that does it all.
Files, JSON, simple query language, no schema migrations required and most of all distributed and change detection and notification of.

I guess it’s all part of the job but I really wish humanity would advance and not take 1 step forward, 2 steps back to bullshit jargon the next step ahead as innovation where in reality it’s just fixing the bs that they had produced in the first place.

diesel: Failed with: relation “__diesel_schema_migrations” does not exist

If you’re exporting an existing database with pg_dump and trying to use that exported SQL with diesel and your initial migration, even after diesel setup has been done and get this message:

Failed with: relation "__diesel_schema_migrations" does not exist

Then you likely have the following line in your postgreSQL dump:

it needs to be changed to

in order for the import to work.