2 replies
I have disabled all in globals object
req.file('avatar').upload({
dirname: require('path').resolve(sails.config.appPath, 'assets/uploads')
}, function whenDone(err, uploadedFile) {
console.log(uploadedFile.length)
return res.ok()
});
}POST /sendFile HTTP/1.1
Host: localhost:1337
Connection: keep-alive
Content-Length: 595119
sec-ch-ua: "Google Chrome";v="93", " Not;A Brand";v="99", "Chromium";v="93"
Accept: application/json, text/plain, */*
Content-Type: multipart/form-data;
sec-ch-ua-mobile: ?0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36
sec-ch-ua-platform: "Windows"
Origin: http://localhost:1337
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Referer: http://localhost:1337/job
Accept-Encoding: gzip, deflate, br
Accept-Language: en,pl-PL;q=0.9,pl;q=0.8,en-US;q=0.7,pt;q=0.6,fr;q=0.5,es;q=0.4------WebKitFormBoundaryB5mB9neeX4AxoFYB
Content-Disposition: form-data; name="file"; filename="Fake CV.pdf"
Content-Type: application/pdf
--------
Hello All! I'm having an issue with MongoDB and GridFS. I have an action who upload a photo and then create a new entry using the fd id of the previous file uploaded (I'm using the Ration project as example). But mongo is throwing an error:
verbo: MongoError: pool is draining, new operations prohibited
Upstream (file upload: photo) emitted an error: MongoError: pool is draining, new operations prohibited
I'm using the sails-hook-upload package to do upload operations.
For example, if you need to implement user-level or role-based permissions in your application, the most straightforward solution is to take care of the relevant checks at the top of your controller action—either inline or by calling out to a helper. Following this best practice will significantly improve the maintainability of your code.
policies) failed to load!Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
require('/home/neonpixe/node/dashboard/api/policies/isLoggedIn.js'), but an error occurred:
I am in the process of updating an existing Sails 0.12.x application to a sails 1.x application. In some of my views, I access req.options.controller to set the id of a div. Then, when loading a page, I check in the associated loaded javascript files using jquery if such a div exists in order to determine whether or not to run certain logic on that page.
For example, say have the following route in routes.js:GET /foo/bar {
controller: FooBarController,
action: index
}
I then have in a view something like <div id='<% req.options.controller %>'></div> using EJS
Then, in the javascript that gets loaded on that page, I have something likeif($('#foo/bar').length > 0){
// id detected on page, run this javascript block
}
However, it seems that the behavior of req.options.controller has changed between 0.12 and 0.1.x. It looks like it used to return foo/bar, but it now returns FooBarController as it should. Is there a way to replicate the previous behavior or a different property that will work similar to how req.options.controller used to work?
So here is an interesting problem
I want to load sails configuration from the ORM datastore
The workaround I am currently using, is starting sails twice
First to get the saved config from the datastore, then use that data to start sails again
Any ideas how to do it in a proper manner?
I was thinking of perhaps using the hook configure method, but then we also still don't have access to the ORM
I would recommend having an endpoint that reads the configuration from the datastore, then spawns a detached child process running the new sails instance, and kills the parent. You can use environment variables in your env/config files, like I did here, and spawn / kill like this:
const { spawn } = require('child_process');
environmentVariables = _.merge({}, process.env, {
BASE_URL: 'insert new custom value here',
PORT: newPortVariable
});
const child = spawn('sails', ['lift'], {
detached: true,
stdio: 'ignore',
env: environmentVariables
});
child.unref(); // allow the parent to die, and the child will live on
process.exit(0);Since sails does take a minute to load, this should work, even if the port doesn't change.