How exactly do you use sails to send mails?
See original GitHub issueI have used the template that comes when sails new is used, I originally thought that changing the config of verifyEmail would do what I need after adding the mailgun creds but this is not happening, this is my package.json
{
"name": "happyfitt",
"private": true,
"version": "1.1.7",
"description": "Happyfitt made using sails and react",
"keywords": [],
"dependencies": {
"@sailshq/connect-redis": "^3.2.1",
"@sailshq/lodash": "^3.10.3",
"@sailshq/socket.io-redis": "^5.2.0",
"moment": "^2.24.0",
"qr-image": "^3.2.0",
"sails": "^1.1.0",
"sails-hook-apianalytics": "^2.0.3",
"sails-hook-organics": "^0.15.0",
"sails-hook-orm": "^2.1.1",
"sails-hook-sockets": "^1.5.5",
"sails-mongo": "^1.0.1"
},
"devDependencies": {
"@sailshq/eslint": "^4.19.3",
"@sailshq/htmlhint": "^0.9.16",
"@sailshq/lesshint": "^4.6.6",
"chai": "^4.2.0",
"grunt": "1.0.1",
"istanbul": "^0.4.5",
"mocha": "^6.1.4",
"sails-hook-fixtures": "^1.0.1",
"sails-hook-grunt": "^3.1.0",
"supertest": "^4.0.2"
},
"scripts": {
"start": "NODE_ENV=production node app.js",
"test-eslint": "npm run lint -s && echo 'Done.'",
"lint": "eslint . --max-warnings=0 --report-unused-disable-directives && echo '✔ Your .js files look so good.' ",
"debug": "node debug app.js",
"test": "mocha test",
"coverage": "istanbul cover _mocha -- -t 10000 -R spec tests/boostrap.test.js test/**/*.test.js",
"deploy": "echo 'This script assumes a dead-simple, opinionated setup on Heroku.' && echo 'But, of course, you can deploy your app anywhere you like.' && echo '(Node.js/Sails.js apps are supported on all modern hosting platforms.)' && echo && echo 'Warning: Specifically, this script assumes you are on the master branch, and that your app can be deployed simply by force-pushing on top of the *deploy* branch. It will also temporarily use a local *predeploy* branch for preparing assets, that it will delete after it finishes. Please make sure there is nothing you care about on either of these two branches!!!' && echo '' && echo '' && echo 'Preparing to deploy...' && echo '--' && git status && echo '' && echo '--' && echo 'I hope you are on the master branch and have everything committed/pulled/pushed and are completely up to date and stuff.' && echo '********************************************' && echo '** IF NOT THEN PLEASE PRESS <CTRL+C> NOW! **' && echo '********************************************' && echo 'Press CTRL+C to cancel.' && echo '(you have five seconds)' && sleep 1 && echo '...4' && sleep 1 && echo '...3' && sleep 1 && echo '...2' && sleep 1 && echo '...1' && sleep 1 && echo '' && echo 'Alright, here we go. No turning back now!' && echo 'Trying to switch to master branch...' && git checkout master && echo && echo 'OK. Now wiping node_modules/ and running npm install...' && rm -rf node_modules && rm -rf package-lock.json && npm install && (git add package-lock.json && git commit -am 'AUTOMATED COMMIT: Did fresh npm install before deploying, and it caused something relevant (probably the package-lock.json file) to change! This commit tracks that change.' || true) && echo 'Deploying as version:' && npm version patch && echo '' && git push origin master && git push --tags && (git branch -D predeploy > /dev/null 2>&1 || true) && git checkout -b predeploy && (echo 'Now building+minifying assets for production...' && echo '(Hang tight, this could take a while.)' && echo && node node_modules/grunt/bin/grunt buildProd || (echo && echo '------------------------------------------' && echo 'IMPORTANT! IMPORTANT! IMPORTANT!' && echo 'ERROR: Could not compile assets for production!' && echo && echo 'Attempting to recover automatically by stashing, ' && echo 'switching back to the master branch, and then ' && echo 'deleting the predeploy branch... ' && echo && echo 'After this, please fix the issues logged above' && echo 'and push that up. Then, try deploying again.' && echo '------------------------------------------' && echo && echo 'Staging, deleting the predeploy branch, and switching back to master...' && git stash && git checkout master && git branch -D predeploy && false)) && mv www .www && git add .www && node -e 'sailsrc = JSON.parse(require(\"fs\").readFileSync(\"./.sailsrc\", \"utf8\")); if (sailsrc.paths&&sailsrc.paths.public !== undefined || sailsrc.hooks&&sailsrc.hooks.grunt !== undefined) { throw new Error(\"Cannot complete deployment script: .sailsrc file has conflicting contents! Please throw away this midway-complete deployment, switch back to your original branch (master), remove the conflicting stuff from .sailsrc, then commit and push that up.\"); } sailsrc.paths = sailsrc.paths || {}; sailsrc.paths.public = \"./.www\"; sailsrc.hooks = sailsrc.hooks || {}; sailsrc.hooks.grunt = false; require(\"fs\").writeFileSync(\"./.sailsrc\", JSON.stringify(sailsrc))' && git commit -am 'AUTOMATED COMMIT: Automatically bundling compiled assets as part of deploy, updating the EJS layout and .sailsrc file accordingly.' && git push origin predeploy && git checkout master && git push origin +predeploy:deploy && git push --tags && git branch -D predeploy && git push origin :predeploy && echo '' && echo '--' && echo 'OK, done. It should be live momentarily on your staging environment.' && echo '(if you get impatient, check the Heroku dashboard for status)' && echo && echo 'Staging environment:' && echo ' 🌐–• https://staging.example.com' && echo ' (hold ⌘ and click to open links in the terminal)' && echo && echo 'Please review that to make sure it looks good.' && echo 'When you are ready to go to production, visit your pipeline on Heroku and press the PROMOTE TO PRODUCTION button.'"
},
"main": "app.js",
"repository": {
"type": "git",
"url": "https://github.com/highskillzz/Happyfitt.git"
},
"author": "Vikranth Kanumuru",
"license": "",
"engines": {
"node": "^10.15"
}
}
and I also don’t see mailgun anywhere. How do I do this exactly?
Thank you
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Email at Sea - a Cruising Guide on the World ... - Cruisers Wiki
Some mail programs (e.g. XGate) will automatically start the connection, synchronise all mail needing to be sent, and then close the connection ...
Read more >How to Fold, Send, and Ship Your Sails for Sail Cleaning or ...
Step Six: Fold the sail over and over about 18 to 20 inches or small enough to fit the box you are going...
Read more >balderdashy/sails-hook-email - GitHub
Templates are generated using your configured Sails View Engine, allowing for multiple template engines and layouts. If Sails Views are disabled, will fallback ......
Read more >On the server - Sails.js
Sails blueprints use Resourceful PubSub to automatically send out notifications about new model instances and changes to existing instances, but you can use...
Read more >Understanding Sails helpers - The Sailscasts Blog
Sails provides you with a mechanism to share code in different places in your applications. This mechanism is called helpers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Anyone?
@highskillzz Hi! I think that Mailgun gives you up to 12,000 emails per month free. The Sails web app template also provides send template email, which is designed to be maximally customizable.
See:
helpers/send-template-email.js