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

[FR]Do we need to surpass NocoDB? #615

Open
Monsterlin2018 opened this issue May 22, 2024 · 2 comments
Open

[FR]Do we need to surpass NocoDB? #615

Monsterlin2018 opened this issue May 22, 2024 · 2 comments

Comments

@Monsterlin2018
Copy link

Monsterlin2018 commented May 22, 2024

I believe this project is very similar to NocoDB, facing direct competition without having a distinct advantage. Could we support some features that NocoDB doesn't have to attract more users?

For example, NocoDB's attitude towards SSO is very dismissive. We all know that OIDC is not an enterprise feature, and their stance prevents me from adopting NocoDB. If we could support OIDC, there would be many scenarios where Teatable could be used.

In everyday work scenarios, a large amount of data is unstructured, such as attachments. In my company, this proportion reaches over 80%. I strongly recommend supporting object storage, especially MinIO.


我认为这个项目与NocoDB非常相似,面临直接竞争,但没有明显的优势。我们是否可以支持一些 NocoDB 不需要的功能来吸引更多用户?
比如NocoDB对于SSO的态度就是非常不屑一顾。我们都知道OIDC不是企业功能,他们的立场阻止我采用NocoDB。如果我们能够支持 OIDC,那么 Teatable 的使用场景就会有很多。
在日常工作场景中,大量数据是非结构化的,例如附件。在我的公司,这个比例达到了80%以上。我强烈建议支持对象存储,尤其是 MinIO。

@tea-artist
Copy link
Contributor

We just submitted an OIDC support so you can see if it meets your needs #617 .
In addition, attachment fields are supported, and the docker examples include examples deployed with minio.

@Monsterlin2018
Copy link
Author

This is absolutely amazing! Thank you so much for all your hard work!

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

2 participants