Which backend for Quasar ?

Incremental

@dobbel Hi, I’m very interested by the websockets and I watched a lot of things on the web but don’t understand how I could modify an existing Quasar app with https://github.com/Urigo/meteor-client-bundler

I understood that Mongo DB is working with collections, but is there a tool to design collections and relationships, or should it be done always with a text editor inside the server code ?
Meteor concept is fine, but not very ergonomic…
Thanks

dobbel

@incremental said in Which backend for Quasar ?:

existing Quasar app with https://github.com/Urigo/meteor-client-bundler

I never said you should. Not recommended to go complicated the first time you use a new tech you don’t yet fully understand. Start small.

I you’re really interested in Meteor you should read up the meteor site docs for a few days and try to get a general idea what it can do and how it works. Play with their examples /demos. Then try to get this repo starter kit going:
https://github.com/alexandesigner/quasar-meteor

build a corporate site, like meteor’s one ? I haven’t find a kind of market place…

Nobody has ever build a beautiful corporate site with Quasar. You create web applications with Quasar not landing pages / corporate design heavy sites. Quasar is awesome but pretty useless for creating unique custom design / beautiful looking landing pages.( never seen any)

have a backend to design database like in Strapi and with GraphQL

Yes. Read the meteor site doc.

have a Quasar app with features like (authent/security, data sync and queries)

Yes. Read the meteor site doc.

Meteor concept is fine, but not very ergonomic…
In other words, should I rebuild anything from scratch with a text editor ?
or should it be done always with a text editor inside the server code ?

I am not going / don’t know how to respond to this

If you want more support about Quasar + Meteor you will have to do some self study first.

DamienDeville

@dobbel said in Which backend for Quasar ?:

For Meteor I used this starter kit to show me the way:
https://github.com/alexandesigner/quasar-meteor
It’s a bit outdated but still works ( with some minor tweaks). I today locally created a new app with this repo and updated it to the latest Qv1 and Meteor V2. If you’re interested in using Meteor I could share this up to date starter kit.

@dobbel
I would be interested in a starter-kit based on Quasar CLI and Urigo’s meteor-client-bundler with … explanations, since I never quite managed to understand Alexandesigner’s.

Among other confusing stuff:
a) The commands to create the project do not mention neither meteor nor quasar

b) The code in quasar-meteor/api/client/main.js/ contains Blaze code; why should it be needed it if the client is made of Quasar/Vue components?

c) It does not use the standard meteor-vue integration packages [https://github.com/meteor-vue/vue-meteor](link url) and therefore it does not use the meteor vue option provided by these packages, but rather calls meteor code by using a $meteor special variable anywhere in the Vue view (e.g., method option, created hook).

Any clarification on all those points would greatly help.

DamienDeville

@damiendeville said in Which backend for Quasar ?:

c) It does not use the standard meteor-vue integration packages [https://github.com/meteor-vue/vue-meteor](link url) and therefore it does not use the meteor vue option provided by these packages, but rather calls meteor code by using a $meteor special variable anywhere in the Vue view (e.g., method option, created hook).

@dobbel
Thinking more about it, I guess those vue-meteor packages are needed to let the meteor build tool recognize the .vue files and the lang=pug, lang=ts, lang=stylus and such attributes in the .vue files and call the appropriate transpilers for each piece of code inside those .vue files.

Now if one creates an app using the Quasar build tool, it does all this source code analysis, transpiling and build stuff out-of-the-box and therefore there is no need to use those packages and thanks to the meteor-client-bundler any function of the meteor object can be called anywhere in the Quasar client app instead of being circumscribed to the meteor vue option created by the vue-meteor-tracker package.

Hence, all this hard work by the 25 contributors of the vue-meteor project is only needed when one creates a Quasar-Meteor stack project as a Meteor app using Quasar as front-end but if one creates a Quasar-Meteor stack project as a Quasar app using Meteor as back-end all is needed is the meteor-client-bundler module.

Is that correct?

dobbel

@damiendeville

100% correct.

dobbel

@damiendeville

a) The commands to create the project do not mention neither meteor nor quasar

Every thing under api is managed by meteor. So for example to start the meteor backend you use Meteor CLI to start it. Also to update meteor you use meteor cli. And of course Quasar Cli is used to manage and start client.

The code in quasar-meteor/api/client/main.js/ contains Blaze code; why should it be needed it if the client is made of Quasar/Vue components?

I have not seen that, because I run meteor headless. But you could create a gui in the api backend part of meteor, for admin things. Its’ optional/just a bonus.

Zenmarc

I am using Quasar with Cloudways Managed WordPress hosting platform and they have the feature of daily and monthly backup that makes auto and manual it depends on the user’s decision.

cynderkromi

@damiendeville
This has been confusing me as well!
I also need an online database backend for Quasar and have been looking at Meteor. But there is really no information about that

“a) The commands to create the project do not mention neither meteor nor quasar”

alexmalcova

sonicviz

I’m trying to solve this problem too!

I was interested to see Meteor suggested. I used that years ago for a while, and was interesting with a big vision but ultimately it died on the launching pad. I didn’t even know it was still a thing.

I did pull down https://github.com/alexandesigner/quasar-meteor and tried to get it running, and immediatly ran into Meteor issues, which reminded me of why I dropped it in the end. The readme is very minimal, which always makes me wary, especially when it doesn’t run OOTB as advertised.

Posted about it here: https://github.com/quasarframework/quasar/discussions/15100 but will copy/paster it:
Any suggestions for robust backends that you could hook up to Quasar to jumpstart a SAAS?
Apart from Firebase. Looking for robust open source SAAS (ie: multi tenant) solutions that have the following (or some) of the core features:

Authentication
Security
User and Role management
Payments (Stripe preferred OOTB)
Audit Logs
Settings
I18n
Debugging

A couple I’ve looked at, with reasons:

https://scaffoldhub.io/ Not updated for a while, Vue2/Vuex going to be discontinued (React only now). Nodejs 16 only.
https://pocketbase.io/docs/ Very neat minimalist with a Quasar starter kit https://github.com/benallfree/awesome-pocketbase but could be a touch early for production use as it’s under active development to V1 still.
https://strapi.io/ seems possible, but might be too heavyweight? Anyone with experience of this using it for a SAAS?
WordPress headless, via Atlas https://github.com/wpengine/faustjs or similar

Would appreciate any other suggestions to seriously consider. Thanks!

No More Posting New Topics!

Which backend for Quasar ?