cusdis
cusdis copied to clipboard
Documentation for integration
- [x] Docsify
- [ ] Jekyll
- [ ] Gatsby
- [x] Hexo
- [ ] Docusaurus
- [ ] MkDocs (PR welcome!)
- [x] nextjs-notion-starter-kit
- [ ] Ghost
- [x] Hugo
Or if you want to know how does Cusdis intergrate with other services, just leave a comment.
这怎么配合这个项目使用?https://github.com/transitive-bullshit/nextjs-notion-starter-kit
@wz1616 Hi! I will have a look at notion-starter-kit and write an integrate document for it.
Thank You Very Much! Waiting For It!
@lbcnz Awesome!
I read the PR, you properly miss a double quote. I've commented in the PR review.
And in your blog post, the app-id is missing too. Is it because the missing double quote?
@wz1616 Hi! I will have a look at notion-starter-kit and write an integrate document for it.
Have you finished it, please?
@lbcnz Awesome!
I read the PR, you properly miss a double quote. I've commented in the PR review.
And in your blog post, the app-id is missing too. Is it because the missing double quote?
Due to sleepiness and lack of testing. I have fixed it.
The quotes are 'optional' as there is no whitespace in the strings but all the variable names were wrong. 😄
@wz1616 I've finished the document of JS SDK, if you understand how it works, you may know how to integrate it in notion-starter-kit by yourself.
https://cusdis.com/doc#/advanced/sdk
Anyway I will check this later.
Would love to see MkDocs with mkdocs-material
and Docusaurus added to the list!
I'm working to integrate it into Next JS with SSG, the comments keep fixed when I navigate between screens, if i refresh everything is ok. Would love to see and example of it. Anyway I'm going to keep trying to handle the issue.
@eric-hc Sure! I don't use python so I'd like to leave MkDocs to the community. But I would try to integrate with Docusaurus.
(Feel free to contribute if someone can do the MkDocs integration. ❤️)
@pablopvsky Thank you! I think the Docsify plugin implementation would help you
https://github.com/djyde/cusdis/blob/master/public/js/cusdis.docsify.js#L33
I expose a renderCusdis
method on window
so that the SPA can call it to rerender the widget (Sorry I didn't mention it on the JS SDK document):
https://github.com/djyde/cusdis/blob/master/widget/index.js#L15
现在问题是我不知道该把代码放到哪个文件,还得麻烦您看看> @wz1616 I've finished the document of JS SDK, if you understand how it works, you may know how to integrate it in notion-starter-kit by yourself.
https://cusdis.com/doc#/advanced/sdk
Anyway I will check this later.
您好?请问进度如何了?> @wz1616 I've finished the document of JS SDK, if you understand how it works, you may know how to integrate it in notion-starter-kit by yourself.
https://cusdis.com/doc#/advanced/sdk
Anyway I will check this later.
@pablopvsky You can check about react-cusdis! https://github.com/Cusdis/sdk/tree/master/packages/react-cusdis
@wz1616 I just create a PR to nextjs-notion-starter-kit.
If you want to integrate in your existed project, just follow what I did in File Changed
https://github.com/transitive-bullshit/nextjs-notion-starter-kit/pull/102/files
真的非常感谢您!辛苦了! Thank you very much! Thank you for your hard work!
@wz1616 I just create a PR to nextjs-notion-starter-kit.
If you want to integrate in your existed project, just follow what I did in
File Changed
https://github.com/transitive-bullshit/nextjs-notion-starter-kit/pull/102/files
Could you provide your repo?
wz1616 @.***>於 2021年4月24日 週六,下午8:32寫道:
I tried again.Here are logs [image: image] https://user-images.githubusercontent.com/62297116/115958924-21493a00-a53c-11eb-87ba-e1e7eff85660.jpeg> @wz1616 https://github.com/wz1616 I just create a PR to nextjs-notion-starter-kit.
If you want to integrate in your existed project, just follow what I did in File Changed https://github.com/transitive-bullshit/nextjs-notion-starter-kit/pull/102/files
—
You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/djyde/cusdis/issues/22#issuecomment-826086042, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAG7HGPTOCB2ZOMZBYR74LDTKK257ANCNFSM43KJZT5A .
Could you provide your repo?
wz1616 @.***>於 2021年4月24日 週六,下午8:32寫道:
I tried again.Here are logs [image: image] https://user-images.githubusercontent.com/62297116/115958924-21493a00-a53c-11eb-87ba-e1e7eff85660.jpeg> @wz1616 https://github.com/wz1616 I just create a PR to nextjs-notion-starter-kit.
If you want to integrate in your existed project, just follow what I did in File Changed https://github.com/transitive-bullshit/nextjs-notion-starter-kit/pull/102/files
—
You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/djyde/cusdis/issues/22#issuecomment-826086042, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAG7HGPTOCB2ZOMZBYR74LDTKK257ANCNFSM43KJZT5A .
I encountered some problems before, and after checking, I found that it was a code formatting error. It's settled now. thank you.
@wz1616 Cool! If still have problem in nextjs-notion-starter-kit, you can create a new issue, instead of this issue 😇
Thanks Again! How About This?https://github.com/djyde/cusdis/issues/49> @wz1616 Cool! If still have problem in nextjs-notion-starter-kit, you can create a new issue, instead of this issue 😇
@djyde It would be great if it can be integrated with Nextra Blog Theme.
Related nextra issue: https://github.com/shuding/nextra/issues/139
@djyde It would be great if it can be integrated with Nextra Blog Theme.
Related nextra issue: shuding/nextra#139
https://github.com/shuding/nextra/pull/143 @YikSanChan
I integrated Cusdis with my Hugo-generated static site, I configured the code with these parameters:
data-page-id="{{ .Permalink }}"
data-page-url="{{ .Permalink }}"
data-page-title="{{ .Title }}"
It works fine, but I can't get any email for new comments... does it work for you?
Hosted or self-host version?
scag1io @.***>於 2021年4月29日 週四,上午2:53寫道:
I integrated Cusdis with my Hugo-generated static site, I configured the code with these parameters:
data-page-id="{{ .Permalink }}" data-page-url="{{ .Permalink }}" data-page-title="{{ .Title }}"
It works fine, but I can't get any email for new comments... does it work for you?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/djyde/cusdis/issues/22#issuecomment-828699512, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAG7HGLJEB2ZVRQJ4U7BKSDTLBKTLANCNFSM43KJZT5A .
Hosted on Vercel, I cloned your repository yesterday. PostgreSQL DB is self-hosted reachable with DuckDNS.
Hosted on Vercel, I cloned your repository yesterday. PostgreSQL DB is self-hosted reachable with DuckDNS.
You need to configure SMTP in self-host version. See https://cusdis.com/doc#/features/notification?id=self-host
You need to configure SMTP in self-host version. See https://cusdis.com/doc#/features/notification?id=self-host
I already did it. You mean Vercel Environment Variables, right? I am trying with Gmail:
SMTP_HOST
set to "smtp.gmail.com"
SMTP_USER
set to "[email protected]"
SMTP_PASSWORD
set to an "App password" by Gmail
SMTP_SENDER
set to "[email protected]"
I did not set SMTP_PORT
and SMTP_SECURE
.
The email is not sent when the comment is posted, I can see that the "App password" is not used. Obviously I redeployed the Vercel app.
What should be the correct syntax for HOST
? "example.com"?
You need to configure SMTP in self-host version. See https://cusdis.com/doc#/features/notification?id=self-host
I already did it. You mean Vercel Environment Variables, right? I am trying with Gmail:
SMTP_HOST
set to "smtp.gmail.com"SMTP_USER
set to "[email protected]"SMTP_PASSWORD
set to an "App password" by GmailSMTP_SENDER
set to "[email protected]" I did not setSMTP_PORT
andSMTP_SECURE
.The email is not sent when the comment is posted, I can see that the "App password" is not used. Obviously I redeployed the Vercel app.
What should be the correct syntax for
HOST
? "example.com"?
This is because Gmail's security settings. See https://github.com/djyde/cusdis/issues/47#issuecomment-826563398
This is because Gmail's security settings. See #47 (comment)
Nope, because I tested the credentials with another SMTP tester and it works. I'll do some more tests later.