Hi all, just wondering what makes Quorra a better choice than Sails for example? Thanks.
Hi all, has anyone had this issue ?
yes, you are right @oliworx
its because of wrong model configuration
email field should be like:
email: {
required: true,
email: true,
type: 'string'
}or
email: {
required: true,
type: 'email'
}
I will update the User model.. Thanks
@oliworx My mysql schema I posted above is not based on any standard. I just created it to test sails-mysql. As you said there is no need to keep remember_token field as not null
@erkan1991 Are you sure psql server is running on your machine
Could you please try to connect to psql server from terminal and see if that works?
@harishanchu but why is your remember token a int(100) ?
@oliworx as I said I just created user table to test sails-mysql
remember_token column should be varchar(60)
Also there was an error in remember_token generation.. the length was wrong, which I have fixed and published.
Hi all, what's the main difference between Quorra and Sails?
Quorra have different request processing architecture
you can read about how quorra functions from the doc: https://quorrajs.org/docs/v1/getting-started/request-lifecycle.html
Sails is built on top of express
and it functions with some kind of hook based architecure
I have used sails in some of my projects and I felt it like a hack over express
its not easy to understand what really going on behind sails
control flow and all
but with quorra its very trasnparent.. everythign is in control
unlike other frameworks quorra uses javascript prototype pattern in most of its code base
hence code looks cleaner and its more maintainable
We are also concerned about application performance
Quorra got a better application performance
Interesting, are there any benchmarks?
once I ran perfomance test with apache benchmark.. and I found quorra perfroms better
I don't remember the figures
but its very easy to test with apache benchamark
command
ab -t 10 -c 10 <applicaiton url> will instruct Apache Benchmark to run for 10 seconds with 10 concurrent requests happening.
Please see the rough test results:
Quorra:
sails:
Please note that I just ran this tests on a new installation of quorra and sails
I haven't done any configurations other than changing the conents of landing route(/) to:
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello World');
so actual results may vary on both frameworks after configurations and perfromance optimzations
For comparison, here’s a regular Express app with some usual middleware loaded.
I don’t know how Quorra handled more reqs in the same time.
@harishanchu Interesting though.
yup
How do I retrieve old data from the session in a view?
I will do a detailed performance comparison once after we release our first stable version
:+1:
you have to configure session first: https://quorrajs.org/docs/v1/middlewares/session.html
You can get old data by flashing data to session
So I always specify the key & value?
yes, but for input data there are other methods: https://quorrajs.org/docs/v1/getting-started/requests-&-input.html#old-input
much handy
How do I access that in a view?
Or do I have to flash it?
eg.
req.session.flash(‘oldUsername', req.input.old('username’))
Is that right?
nope
when you do
req.input.flash(); all input data is already in flash
that can be accessd later with
req.input.old('username');
Ok, but how do I access that in a view?
as
username?
basically methods
req.input.flash and req.session.flash does the same thing
it depends on template system you use
you have to call method
req.input.old('username'); from the view to retrieve it
for that you may pass the req.input object to your view as view option or through res.locals
or you may retrieve the value from route and pass the value to the view
It would be nice if old session data was automatically exposed to the views
Also, the same for validation errors.
Good suggestion. I will note it down
hey, I gotta go now.. will get back later
So, if using Jade/Pug I could do
if errors
…
etc.
It would be nice if we moved to ES6 syntax
Yup.
Code base is written in es5
Is it just you working on it @harishanchu?
Even though it uses es5 in codebase users can use es 6 code on their app
In routes n all
Agreed, maybe a good place to start is by updating the initial generated app code.
Yes.
Yes it's me working on quorra
You’ve done a great job!
Started this as my side project
Thank you 😃
I wish I had more experience to help more.
My friend @nikhilben is also helping me with some of the things
Hey thanks for showing interest in this
No problem. I’m currently using Express & Mongoose, but I like fullstack frameworks :)
:+1:
Might be good to update Jade to Pug also.
What future plans do you have for Quorra?
Yes
There is already an issue registered for this in github
There are lot of things to be done before first stable release
Is there a list?
There is no public list yet
I would help if I could.
Yes, will do once this is stable
I have to create a service loading strategy
Now everything is loaded in a flat file in order during server lift
Oh, services will be nice! :)
I'm tryingto implement application testing now
need to document how to test application
after that I have to upgrade outdated dependecies
Awesome, Ava looks nice - https://github.com/avajs/ava
I have already done this
What do you mean?
I configured quorra to use mocah + should
Ah
its already there
I have to write docs
there is a sample test defined in quorra
I might try build a simple app with Quorra and log issues/suggestions as I go along. What do you think?
you can run tests now itself with npm test from quorra project root
Does Quorra use Express?
@erkan1991 It looks like Postgres isn’t running
Nope.. it donot use express
Ok, so I cannot use Express middleware such as Passport for social logins? :(
I have used express's request and response helper methods in quorra
Not sure how I’d do social logins so.
It's not a big deal
How so?
You can do some wraparound express middlewares to make it work for quorra
In fact quorra already uses some middlewares like such
G
For example body-parser
Please c quorra middlewares documentation to understand how to write middlewares for quorra
Ok, so I’ve to write my own middleware?
Looking at
BodyParserMiddleware.js now
quorra uses prototype pattern for middleware too
gives some standard and structure
The alternative would be ES6 classes, right?
yes
its easy to wrap any express middleware to this structure
I don’t know how comfortable/good I am to wrap Passport social login strategies. :(
yup
I'm planning to write wrappers for some popular express middlewares
for passport too
That would be a great help
you can create custom middleware and register it: https://quorrajs.org/docs/v1/getting-started/middleware.html#registering-middleware
Sure, I just don’t know how I’d wrap Passport and the different strategies.
ok
see this one
it uses
cookie-parser middleware inside
when quorra grows old there will be inbuit support for most of the popular express middlewares
for the rest you can create custom middlewares
That would be fantastic. A tutorial on how to wrap popular middleware would even help.
yup
Thanks @niallobrien. All working now.
@erkan1991 http://postgresapp.com/
I like to use that.
@niallobrien he pm ed me that his issues are resolved
Glad to hear :)
When do you plan to officially release v1?
I didn't fix a date yet.
I have following things to complete before v1 release:
- Application test setup and documentation
- Implement a better internal service load strategy
- Update outdated dependencies
- Filewatch support for quorra-cli
Filewatch? I just use
nodemon
yeah
that is what I suggest for now:
but I will integrate it with cli tool if its not a big deal
nodemon has to be installed globally afaik, so that might not be a good idea
but if you once install it gloabally, can be used for any other projects too
and its only for now
I'm planning to have our own implementation
Yes