@Hawkeye64 happy to help! If you need a hand with docs / guides feel free to drop message

I’ve been using them in conjunction for most projects.

As mentioned above REST is the way to go.

You’d use django-rest-framework as your backend API and Quasar as your frontend and deploy both separately.

If you’re unfamiliar with drf it’s worth getting to grips with Django first before jumping into RESTful APIs. Once your comfortable with Django you’d used drf in order to make API calls from your front end .

For example you can chose to use axios in your quasar app, which in turn would be used to make request to your REST API.

For example axios.get('http://localhost:8000/api/...)

This makes a GET request to your local Django server which returns some information.

Some additional notes:
Django rest is really powerful. Much like Django there are generic views and model “views” (serializers) that make things really easy. There are some great extensions for social auth like django-rest-auth

Hi there, In order to use the components and pages of both projects I’d look into vue-router

const routes = [
      {
        path: "/",
        component: () => import("layouts/MyLayout.vue"),
        children: [
          {
            path: "",
            name: "drive",
            component: () => import("pages/drive/Index.vue"),
          },
          {
            path: "",
            name: "calendar",
            component: () => import("pages/calendar/Index.vue"),
          },
        ]
      }
    ];

and in your pages import the respective components via:

import calendarcomp from "components/calendar/calendarcomp.vue";

For more info here’s a link to the docs for vue-router

Hi all, this is my unofficial guide on how to use the quasar dotenv extension.

1. Install the quasar app extension:

   $ quasar ext add @quasar/dotenv            

2. Follow the setup instructions, here you’ll specify the names for your production and development .env files ex: dev.env // prod.env

3. Create files in your root directory based on the names specified in step (2)

   // dev.env              

   FOO=bar   

4. You’re all set, you can access these vars in any file via process.env.<var-name>

   // src/components/example.vue         
    
    ...
    mounted() {
      console.log(process.env.FOO)            
    },
    ...

For more information check out:

• Github repo

Why I wrote the post:

• This is very similar to the steps in the github repo but it wasn’t immediatley clear that I had to make new files and how the variables I specified would be accessible in my files.

If anythings missing feel free to correct me below / add to the knowledge of how to use this great framework

Hi all, I’ve run into the following error a couple of times and thought I’d share a solution in-case anyone else has experienced this issue.

Error message:

events.js:173
      throw er; // Unhandled 'error' event
      ^

  Error: ENOSPC: System limit for number of file watchers reached, watch '/home/<user-name>/vue-apps/twitter/quasar.conf.js'

Solution:

From the command line run the following

$ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

$ sudo sysctl --system

Alternatively a reboot will fix the issue

For more information please see:

• stackoverflow post

HI there, great article!

I’ve played around with hellojs and although it is really useful for OAuth2, I’d approach with caution if you are trying to use it for OAuth 1 (for example with providers like twitter)

I also found that for SPAs hellojs may not be the best solution due to the nature of SPA urls i.e.

http://localhost:8000/#/<route>

Typically hellojs would hang as the callback url for OAuth 1 providers leads to no routes as they are:

http://localhost:8000/callback?token=<--------> ....

If anyone has any solution to this it would be great to hear?

Edit
I forgot to mention that using history mode is a good solution to the issue but needs some server side work when deploying.

@gil
Sounds good, best of luck!

@gil
Ah I see (and correct me if I’m wrong)

So you’re running an electron app that uses socket.io-server.

And you’ll then be connecting to that local app from other apps and machines on the network

Figure:

                Main Electron App (server)
                 /           |            \
               /             |              \
             App            App.            App        

I’m not sure what’s an efficient way to go about doing this, as I haven’t played around with electron before, but I’ll look into it further as this sounds pretty interesting

Feel free to contact me if you come up with a solution and I’ll see what I manage to come up with

@gil
Glad to hear!
Unfortunately I don’t think I can offer sound help for you.
It might be worth asking what you’re trying to achieve?

For instance if you are using socket.io to connect to a back-end service or run a socket.io server internally for use with-in your electron app?

Regards,
mko

This is kind of hacky however I used the following although this uses a dialog instead:

<q-dialog v-model="date">
     <q-date v-model="post.date" today-btn @click="date=false" />
</q-dialog>