Hi,
If anybody from the Sails team sees this I would very much appreciate an insight.
I a few months I’ll be finishing my first major Node project (web app, admin app, IOS and Android apps).
For the web app I chose Sails and despite of a steep learning curve I don’t regret it.
But since is very likely that in the second part of the year I’ll switch to a new major Node project I wonder if I could still choose Sails for its web part.
This depends on two factors:
- If I find a way to include Vue plugins and I mean multi-component plugins not just SFC components because these work, did that already but so far I haven’t been able to add multi-components.
- The approach the Sails team uses in regards of the soon to be Vue 3 with its composition API.
What will the Sails team do? Join this or avoid it and stick with Vue 2+?
I don’t really expect an answer for the #1 but the #2 is really important to me and maybe to others in my shoes so please, Sails team, let us know what you think!
We’ve avoided adding social auth to “caviar” (the web app template) thus far because that stuff tends to get out of date pretty quickly. I would feel comfortable including opt-in social login for one reference provider at some point though
That said, I’ve found you usually end up delivering way more business value by punting on social auth altogether until you have a completely-tested, bug-free, working beta version of your application deployed on a production server someplace and being actively used by non-technical testers or friendly early adopters. In my experience, that’s been true whether it’s the product for a simple startup or a complicated, industry-specific consumer tool for an established brand
@mikermcneil
Is there any boiler-plate/guide on implementing authentication with session management(backed by redis) without passport js
right?
connect-redis as a common persistent store for your session. When session management is enabled (it is enabled by default) sails will automatically attach your session object to the req object. You can use this session object to read and add properties wherever you have access to req object, in controllers, policies, middleware, etc.
Hi,
If anybody from the Sails team sees this I would very much appreciate an insight.
I a few months I’ll be finishing my first major Node project (web app, admin app, IOS and Android apps).
For the web app I chose Sails and despite of a steep learning curve I don’t regret it.
But since is very likely that in the second part of the year I’ll switch to a new major Node project I wonder if I could still choose Sails for its web part.
This depends on two factors:
- If I find a way to include Vue plugins and I mean multi-component plugins not just SFC components because these work, did that already but so far I haven’t been able to add multi-components.
- The approach the Sails team uses in regards of the soon to be Vue 3 with its composition API.
What will the Sails team do? Join this or avoid it and stick with Vue 2+?I don’t really expect an answer for the #1 but the #2 is really important to me and maybe to others in my shoes so please, Sails team, let us know what you think!
@rachaelshaw @mikermcneil please guys, an opinion about it?
@shobhitsinghal624 Not quite. I think it's express sending back an ETag header with your requests. Then when your browser requests the same resource again the browser sends an If-None-Match header with the ETag from the first request. Your app generates the output, express ends up generating the same ETag, decides the content hasn't changed becuase it matches the ETag sent with your request and sets the 304 response code.
There's no magic to stop it from hitting your database for each request.
Not sure if helpful :)
but am unable to reach please let me know if i'm doing wrong
here is the link where i try to get image
http://localhost:1338/images/04b57035-743f-48c0-a192-9957852c619f.jpg
.sendNativeQuery(). As per docs .native() is deprecated. Follow this link to execute raw queries https://sailsjs.com/documentation/reference/waterline-orm/datastores/manager
await new Promise(async (acp, rjt) => {
await Banks._adapter.mongodb(config.database.host, async (err, db) => {
if (err) {
rjt();
}
let data = await db.collection("accounts").aggregate(where);
acp(await data.toArray());
});
});
"use strict";
const bluebird = require('bluebird')
module.exports = sails => {
return {
initialize: cb => {
sails.on('ready', function() {
Object.keys(sails.services).forEach(function (key) {
bluebird.promisifyAll(sails.services[key])
})
})
return cb();
}
}
}