Skip to content

Commit 9138754

Browse files
authored
Update README.md
1 parent a7e2cee commit 9138754

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,15 @@ Top priority of this demo is to connect a Vulcan Next frontend to an existing Me
6363
- The `meteor-backend/packages/getting-started/lib/modules/vulcanResource/vulcanResource.js` file contains common parts, ie the schema. It is reused to build the Vulcan Meteor collection, as well as the equivalent Vulcan Next model (model is the new terms for collection, and it's way more powerful, but only available in Next at the moment).
6464
We cannot put this folder as the root, as Meteor cannot import file outside of the package. So it has to live in Meteor until we find a better approach for the `common` folder.
6565

66+
- Automated emails (eg for mail verification after signup) needs to point to the Next frontend, even if they are triggered by the Next.js backend. If you use those features, you'll need to add this piece of code in the Meteor app:
67+
```js
68+
Meteor.startup(() => {
69+
Accounts.urls.resetPassword = function(token) {
70+
// where localhost:3000 is your Next.js app
71+
return 'http://localhost:3000/reset-password/' + token;
72+
};
73+
```
74+
(TODO: we should add this feature in this repo and make it more configurable based on a Meteor setting)
6675
6776
## Full-stack = progressively use Next as your backend
6877

0 commit comments

Comments
 (0)