Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Gitlab #96

Closed
rootkea opened this issue Dec 14, 2018 · 9 comments
Closed

Support for Gitlab #96

rootkea opened this issue Dec 14, 2018 · 9 comments

Comments

@rootkea
Copy link

rootkea commented Dec 14, 2018

Hi!

I would like to own the data (comments) posted on my website by using the self-hosted Gitlab instance. So is it possible to use Gitlab issues instead of Github issues?

Thanks!

@VincentTam
Copy link

Why not use Staticman? Since eduardoboucas/staticman#219, it's possible to embed comments into the site.

@rootkea
Copy link
Author

rootkea commented Dec 15, 2018

@VincentTam Thank you for suggesting StaticMan!

I'm toying with it now and will get back to you once I'm done. :)

@jdanyow
Copy link
Member

jdanyow commented Dec 16, 2018

staticman 👍

@robb-romans
Copy link

Also would love to have GitLab support

@donaldboulton
Copy link
Contributor

donaldboulton commented Apr 27, 2019

Staticman died no response from Staticman or Vincent Tams Staticman Lab on invite or usage!
Staticman does not work any more and if you can get it to work it is overused and timeout errors are constant.
Been using Staticman for years, about 8 months ago it died and so Staticman no more.
Stickman got into it with GraphQl and components were flying everywhere, a gruesome scene; >_<> Staicmand Died!
You could fork the repo, updated it = github graphql V-4.
And then have your own

@VincentTam
Copy link

@donaldboulton I'm sorry to hear about your experience. I'm always pingable by @VincentTam, and @staticmanlab is active on GitHub and GitLab.com.

P.S. Four months ago, I've deployed another instance on Framagit at https://staticman-frama.herokuapp.com/ associated with the user @staticmanlab1 after some user(s) had failed to add Staticman to their static sites on Framagit.

@sunk818
Copy link

sunk818 commented Nov 5, 2019

I'd like GitLab support because of the additional ways you can login using social media accounts. This will make commenting easier than just a github login. My instance is self-hosted so it is not using GitHub, GitLab, etc.

@phaitonican
Copy link

same here would be awesome. RN i have my pages hosted on gitlab and my utternance points to github its kind of strange but does not really matterr, i stttill prefer gitlab over github

@mrsnakeoil
Copy link

I would very much like to see this supported for a number of reasons (below). As for what I can offer, whilst I'm not up to making the changes, can help QA, support, documentation, and provide cookies/pizza by post!

  1. Broader Reach and Inclusivity: Not all developers and organizations use GitHub; some prefer GitLab for various reasons, including its open-source nature and unique features. Supporting GitLab would make Utterances accessible to a wider audience.
  2. Diversification of Platform Dependencies: Relying solely on GitHub might pose risks if there are service disruptions or policy changes. Supporting GitLab provides a backup, ensuring continuous service availability.
  3. Open Source Alignment: Like GitHub, GitLab is popular in the open-source community. Supporting it aligns with the ethos of open-source development and broadens the tool's appeal to open-source projects.
  4. Competitive Edge: By supporting multiple platforms, Utterances can differentiate itself from other commenting widgets that may only support one platform, thus attracting users looking for multi-platform solutions.
  5. Community Building: Supporting GitLab can help build a community of users who are enthusiastic about GitLab, fostering a sense of inclusivity and diversity in the user base.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants