If I define custom action or custom routes, its working fine. But not for blueprint with predefined actions
i have a questions for the autogenerated rest routes as well if anyone has a second. I have two models, user and club. many to many relationship
user has memberships: { collection: 'club', via: 'members' } . and club has members: { collection: 'user', via: 'memberships' } . I can get them to work for the development only shortcut routes GET /:modelIdentity/:id/:association/add/:fk , however i don't want to use shortcut routes. i want to use the example PUT /club/:id/members/add/:fk with :id being the club id and :fk being the user id and it keeps giving me not found. i'm sure i'm doing it wrong, but the boat / driver example is a little confusing. can anyone offer advice?
?
I would like to see some examples
if anyone else runs into this issue
this page in the docs says you need the /add/ as part of the url
looking closer at the add to reference doc page, https://sailsjs.com/documentation/reference/blueprint-api/add-to
you do not need the add word
so for me,
PUT /:modelIdentity/:id/:association/:fk works beautifully
I am using Sails@0.12.3 and want to serve my uploaded assets/files from a specified directory. But can not set static middleware.
Most of the solutions from stackoverflow implements a express middleware in config/http.js but in my case it's not working.
@KSDaemon redeploying the site now, cleared things up https://trello.com/c/TW3VEMJk
@KSDaemon thanks again for bringing it to my attention
https://sailsjs.com/documentation/reference/request-req/req-accepted-languages now redirects to https://sailsjs.com/documentation/reference/request-req/req-accepts-languages (and so on). Added note to upgrading guide. I think we're good here, but if anyone runs into any other related stuff from the that we missed from the Express 4 upgrade, please holler at me asap (twitter pm if necessary)! I want to get anything like that taken care of as early in the 1.0 release cycle as possible so we don't get forced to go 2.0 earlier than we'd like
Sails is forcing me to keep static file inside assets directory.
Actually I want to store my uploaded files to a directory named 'uploads' and want to serve those files as static assets in a virtual route as I said earlier.
How can view error messages on form login and sign up on form on modal?
I have a homepage that have a map, on this homepage have a navbar with some links, included login and signup. When I click on login or signup open a modal, and not a view on a new page, but on a modal dialog. On this dialog I have a form. I create action on controller for signup and login and works. Only managed errors and response json for app android, but I want use this error on form modal dialog. For example, If I do not enter username I want a error on dialog, if I write password wrong I want an error on modal dialog, etc etc
You’re looking to keep the model above the view and login without navigating away. I get that. What you could do is have a model that is triggered by a url param
mysite.com/home#login - In your controller you can redirect to this view with a list of errors you want outputting.
is it possible?
npm ERR! Linux 4.4.0-77-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "bcrypt" "--save"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! bcrypt@1.0.3 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the bcrypt@1.0.3 install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the bcrypt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs bcrypt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls bcrypt
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /root/smash_node/npm-debug.log
Hi, try install bcrypt on my machine linux and I have this error. On my pc works, but on server no...
I have node 4.x, and on my pc 9.x. It is possible that the problem it is?
couple interesting things I've noticed with Sails 1.0 today:
- model attribute unique:true does not work with mongodb v3.2. It creates an index, but does not set it as unique
module.exports = {
migrate: 'alter',
attributes: {
eventId: {
type: 'number',
unique: true
},
...My current solution is to ensureIndex in bootstrap.js and remove attribute unique:true on model attr
await Event.native(function(err, collection) {
collection.ensureIndex({eventId: 1}, {unique: true});
});sails run [scriptName] does not execute bootstrap.js (intended functionality?)
createEach() .tolerate('E_UNIQUE') (sails-mongo, mongodb v3.2) will stop creating the following records once tolerate unique is triggered. So if 10 records to createEach, and E_UNIQUE triggers at idx 5, idx > 5 will be skipped due to db server error. My attempt to brute force createEach without checking for uniqueness in DB is for a high performance ETL process. I know this is hack-ish, but I don't believe there is support for something like MYSQL's multi-row REPLACE INTO or MONGO find/upsert. I should probably go native for this...
My guess is that only #1 is a bug and #2/#3 are expected behavior. @mikermcneil @particlebanana I can file a bug for #1 if you'd like. Let me know what you think of #2 and #3 if you have a min. THX
Any solution for it???
I have a problem very big with node js
I have a server on https that started with nodejs 4.2.6 with pm2 and all works. Now i can start another project on another path on same port always on https, but use bcrypt and with nodejs 4.x doesn't works, and old project started with pm with version 8.x doesn't work. This project it is on sails js. The goal is migrate all api express on sails, but initially I want both server on execution and migration by step. Can I resolve this problem? Start 2 server on same port but different path, and problem with version of nodejs
I have a server on https that started with nodejs 4.2.6 with pm2 and all works. Now i can start another project on another path on same port always on https, but use bcrypt and with nodejs 4.x doesn't works, and old project started with pm with version 8.x doesn't work. This project it is on sails js. The goal is migrate all api express on sails, but initially I want both server on execution and migration by step. Can I resolve this problem? Start 2 server on same port but different path, and problem with version of nodejs
For bcrypt, be sure to compile with the version of nodeJs you're trying to work with.
now, if you want to keep the same https://URL:port and route requests either to ex-express or new Sails, you should set up a proxy like Nginx
