coop-cloud/nocodb
1
0
Fork 1
Code Issues 2 Pull Requests 2 Packages Projects Releases Wiki Activity

Added enterprise functionality #8

Merged
jjsfunhouse merged 2 commits from jjsfunhouse/nocodb:enterprise-update into main 2026-03-25 20:34:14 +00:00
Conversation 1 Commits 2 Files Changed 5 +80
jjsfunhouse commented 2026-03-23 20:47:02 +00:00
Owner
Copy Link

Created override compose.yml file in order to enable recipe operators to utilize enterprise versions of NocoDB.
They can do this through

  • Adding their license key
  • Generating a JWT token for auth in NocoDB
  • Deploying the enterprise Docker image through the app config.

Also updated README to reflect this change.

Created override compose.yml file in order to enable recipe operators to utilize enterprise versions of NocoDB. They can do this through * Adding their license key * Generating a JWT token for auth in NocoDB * Deploying the enterprise Docker image through the app config. Also updated README to reflect this change.
jjsfunhouse added 1 commit 2026-03-23 20:47:03 +00:00
Added enterprise functionality 128ab5eece
jjsfunhouse added 1 commit 2026-03-23 20:47:40 +00:00
Merge branch 'main' into enterprise-update 860037f7ed
jjsfunhouse merged commit e704d265dd into main 2026-03-25 20:34:14 +00:00
jjsfunhouse deleted branch enterprise-update 2026-03-25 20:34:19 +00:00
decentral1se reviewed 2026-03-26 11:54:42 +00:00
decentral1se left a comment
Owner
Copy Link

@jjsfunhouse flying by, maybe this is still useful!

In general, I look in the git log listing and then click "Request review" on the usernames on the pull request. This can be handy to get second opinions on changes. If a PR is left lingering, you can also ask on the Matrix channels.

https://git.coopcloud.tech/coop-cloud/nocodb/commits/branch/main

@jjsfunhouse flying by, maybe this is still useful! In general, I look in the git log listing and then click "Request review" on the usernames on the pull request. This can be handy to get second opinions on changes. If a PR is left lingering, you can also ask on the Matrix channels. > https://git.coopcloud.tech/coop-cloud/nocodb/commits/branch/main
.env.sample
@ -13,0 +21,4 @@
#JWT used for authentication in enterprise version
#SECRET_AUTH_JWT_VERSION=v1
#NC_AUTH_JWT_SECRET_FILE=/run/secrets/auth_jwt
decentral1se commented 2026-03-26 11:52:48 +00:00
Owner
Copy Link

This is unused?

This is unused?
jjsfunhouse commented 2026-03-27 16:39:05 +00:00
Author
Owner
Copy Link

In https://nocodb.com/docs/self-hosting/environment-variables, NocoDB specifies that the NC_AUTH_JWT_SECRET should be set for generating authentication tokens for user sessions. I thought it'd be better for the operator to know this value rather than it being set automatically.

In https://nocodb.com/docs/self-hosting/environment-variables, NocoDB specifies that the `NC_AUTH_JWT_SECRET` should be set for generating authentication tokens for user sessions. I thought it'd be better for the operator to know this value rather than it being set automatically.
👍 1
README.md
@ -28,0 +29,4 @@
* `abra app config <app-name>`. Uncomment the variables used for setting enterprise values. Make sure you have a valid license.
* `abra app undeploy <app-name>`
* `export JWT_SECRET=$(pwgen 50)`
decentral1se commented 2026-03-26 11:52:08 +00:00
Owner
Copy Link

You can achieve this using the password generator customisation feature:

https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-change-secret-generation-characters

auth_jwt is only included for generation when you do COMPOSE_FILE="$COMPOSE_FILE:compose.license.yml"

You can achieve this using the password generator customisation feature: > https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-change-secret-generation-characters `auth_jwt` is only included for generation when you do `COMPOSE_FILE="$COMPOSE_FILE:compose.license.yml"`
jjsfunhouse commented 2026-03-27 16:57:05 +00:00
Author
Owner
Copy Link

Changed the secret generation in #9 , I just had it like this to follow the trend set by the original recipe but maybe that wasn't ideal. Let me know what you think!

Changed the secret generation in #9 , I just had it like this to follow the trend set by the original recipe but maybe that wasn't ideal. Let me know what you think!
👍 1
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se devydave fauno flancian Frando iexos jade javielico jjsfunhouse jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moosemower moritz nicksellen notplants p4u1 pau pharaohgraphy renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val vaznasty virtualboys wolcen wykwit xynosis yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/nocodb#8
No description provided.
Delete Branch "jjsfunhouse/nocodb:enterprise-update"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?