blsmedia/sign
2
0
Fork 0
Code Issues Packages Releases Activity
Files
dd162205faa6990fbbb228ea0d1e2acf89b7e599
sign/turbo.json

139 lines
4.2 KiB
JSON
Raw Normal View History

Add turborepo to monorepo.
2023-05-29 10:38:24 -05:00
{
"$schema": "https://turbo.build/schema.json",
"pipeline": {
"build": {
feat: allow oidc only signup and trust mail addresses (#1208) This change will allow for user registration when users are federated through oidc provider even if the general signup is disabled additionally the users email address can now be automatically set as trusted. This will force corporate users to signin using SSO instead of creating manual accounts.
2024-07-31 07:38:12 +02:00
"dependsOn": ["prebuild", "^build"],
"outputs": [".next/**", "!.next/cache/**"]
Add turborepo to monorepo.
2023-05-29 10:38:24 -05:00
},
chore: add prebuild to handle prisma build cache
2024-06-21 12:55:17 +10:00
"prebuild": {
chore: add more field types (#1141) Adds a number of new field types and capabilities to existing fields. A massive change with far too many moving pieces to document in a single commit.
2024-07-18 16:45:44 +03:00
"cache": false,
feat: allow oidc only signup and trust mail addresses (#1208) This change will allow for user registration when users are federated through oidc provider even if the general signup is disabled additionally the users email address can now be automatically set as trusted. This will force corporate users to signin using SSO instead of creating manual accounts.
2024-07-31 07:38:12 +02:00
"dependsOn": ["^prebuild"]
chore: add prebuild to handle prisma build cache
2024-06-21 12:55:17 +10:00
},
chore: add some eslint rules (#344)
2023-11-14 14:31:45 +05:30
"lint": {
"cache": false
},
"lint:fix": {
"cache": false
},
fix: support optimise imports
2023-09-21 21:34:24 +10:00
"clean": {
"cache": false
},
Add turborepo to monorepo.
2023-05-29 10:38:24 -05:00
"dev": {
"cache": false,
"persistent": true
feat: add playwright
2023-10-03 09:53:47 +01:00
},
chore: upgrade to next 14.0.0
2023-10-27 15:14:04 +11:00
"start": {
feat: allow oidc only signup and trust mail addresses (#1208) This change will allow for user registration when users are federated through oidc provider even if the general signup is disabled additionally the users email address can now be automatically set as trusted. This will force corporate users to signin using SSO instead of creating manual accounts.
2024-07-31 07:38:12 +02:00
"dependsOn": ["^build"],
chore: upgrade to next 14.0.0
2023-10-27 15:14:04 +11:00
"cache": false,
"persistent": true
},
feat: add playwright
2023-10-03 09:53:47 +01:00
"dev:test": {
"cache": false
},
"test:e2e": {
feat: allow oidc only signup and trust mail addresses (#1208) This change will allow for user registration when users are federated through oidc provider even if the general signup is disabled additionally the users email address can now be automatically set as trusted. This will force corporate users to signin using SSO instead of creating manual accounts.
2024-07-31 07:38:12 +02:00
"dependsOn": ["^build"],
fix: command
2024-01-04 23:40:35 +05:30
"cache": false
feat: initial i18n marketing implementation (#1223) ## Description This PR introduces an initial i18n implementation using [Lingui](https://lingui.dev). We plan to combine it with Crowdin which will provide AI translations when PRs are merged into main. We plan to rollout i18n to only marketing for now, and will review how everything goes before continuing to introduce it into the main application. ## Reasoning Why not use i18n-next or other alternatives? To hopefully provide the best DX we chose Lingui because it allows us to simply wrap text that we want to translate in tags, instead of forcing users to do things such as: - Update the text to `t('some-text')` - Extract it to the file - The text becomes a bit unreadable unless done correctly Yes, plugins such as i18n-ally and Sherlock exist to simplify these chores, but these require the user to be correctly setup in vscode, and it also does not seem to provide the required configurations for our multi app and multi UI package setup. ## Super simple demo ```html // Before <p>Text to update</p> // After <p> <Trans>Text to update</Trans> </p> ``` ## Related Issue Relates to #885 but is only for marketing for now. Another branch is slowly being prepared for the changes required for the web application while we wait to see how this goes for marketing. ## Changes Made Our configuration does not follow the general standard since we have translations that cross: - Web app - Marketing app - Constants package - UI package This means we want to separate translations into: 1. Marketing - Only translations extracted from `apps/marketing` 2. Web - Only translations extracted from `apps/web` 3. Common - Translations from `packages/constants` and `packages/ui` Then we bundle, compile and minify the translations for production as follows: 1. Marketing = Marketing + Common 2. Web = Web + Common This allows us to only load the required translations when running each application. Overall general changes: - Add i18n to marketing - Add core i18n setup to web - Add pre-commit hook and GH action to extract any new <Trans> tags into the translation files <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added Romanian localization for marketing messages to improve accessibility for Romanian-speaking users. - Introduced German and English translation modules and PO files to enhance the application's internationalization capabilities. - Integrated internationalization support in the RootLayout component for dynamic language settings based on server-side configurations. - Enhanced the Enterprise component with translation support to adapt to user language preferences. - Added a `<meta>` tag to prevent Google from translating the page content, supporting internationalization efforts. - **Bug Fixes** - Resolved minor issues related to the structure and accessibility of translation files. - **Chores** - Updated project dependencies to support the new localization features and ensure stability. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Lucas Smith <me@lucasjamessmith.me> Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: github-actions <github-actions@documenso.com>
2024-07-26 14:56:42 +10:00
},
"translate:compile": {
"cache": false
Add turborepo to monorepo.
2023-05-29 10:38:24 -05:00
}
wip: refresh design
2023-06-09 18:21:18 +10:00
},
feat: allow oidc only signup and trust mail addresses (#1208) This change will allow for user registration when users are federated through oidc provider even if the general signup is disabled additionally the users email address can now be automatically set as trusted. This will force corporate users to signin using SSO instead of creating manual accounts.
2024-07-31 07:38:12 +02:00
"globalDependencies": ["**/.env.*local"],
wip: refresh design
2023-06-09 18:21:18 +10:00
"globalEnv": [
chore: implemented feedback
2023-09-11 13:43:17 +03:00
"APP_VERSION",
feat: add two factor auth (#643) Add two factor authentication for users who wish to enhance the security of their accounts.
2023-12-01 05:52:16 +05:30
"NEXT_PRIVATE_ENCRYPTION_KEY",
feat: add server crypto (#863) ## Description Currently we are required to ensure PII data is not passed around in search parameters and in the open for GDPR reasons. Allowing us to encrypt and decrypt values with expiry dates will allow us to ensure this doesn't happen. ## Changes Made - Added TPRC router for encryption method ## Testing Performed - Tested encrypting and decrypting data with and without `expiredAt` - Tested via directly accessing API and also via trpc in react components - Tested parsing en email search param in a page and decrypting it successfully ## Checklist - [X] I have tested these changes locally and they work as expected. - [X] I have followed the project's coding style guidelines.
2024-01-25 16:07:57 +11:00
"NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY",
wip: refresh design
2023-06-09 18:21:18 +10:00
"NEXTAUTH_URL",
"NEXTAUTH_SECRET",
feat: add single player mode
2023-09-20 13:48:30 +10:00
"NEXT_PUBLIC_PROJECT",
feat: add vercel build script
2023-09-14 15:00:14 +10:00
"NEXT_PUBLIC_WEBAPP_URL",
"NEXT_PUBLIC_MARKETING_URL",
feat: add and use NEXT_PRIVATE_INTERNAL_WEBAPP_URL (#1298) Introduces `NEXT_PRIVATE_INTERNAL_WEBAPP_URL` used for requesting the app by itself (backend) [e.g. for background jobs]
2024-09-06 12:37:10 +02:00
"NEXT_PRIVATE_INTERNAL_WEBAPP_URL",
feat: feature flags
2023-08-18 20:05:14 +10:00
"NEXT_PUBLIC_POSTHOG_KEY",
"NEXT_PUBLIC_FEATURE_BILLING_ENABLED",
fix: fix eslint warnings
2023-08-31 13:33:13 +10:00
"NEXT_PUBLIC_STRIPE_COMMUNITY_PLAN_MONTHLY_PRICE_ID",
feat: add document auth (#1029)
2024-03-28 13:13:29 +08:00
"NEXT_PUBLIC_STRIPE_ENTERPRISE_PLAN_MONTHLY_PRICE_ID",
fix: build error
2023-12-09 12:05:36 +05:30
"NEXT_PUBLIC_DISABLE_SIGNUP",
perf: mentioned type and size of the doc to be uploaded (#867) explicitly mentioned "PDF" to upload, and added a toast if pdf size is greater than 50mb fixes: #621
2024-02-05 07:20:35 +05:30
"NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT",
wip: refresh design
2023-06-09 18:21:18 +10:00
"NEXT_PRIVATE_DATABASE_URL",
feat: add vercel build script
2023-09-14 15:00:14 +10:00
"NEXT_PRIVATE_DIRECT_DATABASE_URL",
chore: use rust based cms signing
2024-03-15 22:26:09 +11:00
"NEXT_PRIVATE_SIGNING_TRANSPORT",
"NEXT_PRIVATE_SIGNING_PASSPHRASE",
"NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH",
"NEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS",
"NEXT_PRIVATE_SIGNING_GCLOUD_HSM_KEY_PATH",
"NEXT_PRIVATE_SIGNING_GCLOUD_HSM_PUBLIC_CRT_FILE_PATH",
"NEXT_PRIVATE_SIGNING_GCLOUD_HSM_PUBLIC_CRT_FILE_CONTENTS",
"NEXT_PRIVATE_SIGNING_GCLOUD_APPLICATION_CREDENTIALS_CONTENTS",
feat: feature flags
2023-08-18 20:05:14 +10:00
"NEXT_PRIVATE_GOOGLE_CLIENT_ID",
"NEXT_PRIVATE_GOOGLE_CLIENT_SECRET",
feat: add oidc support
2024-04-13 20:46:08 -04:00
"NEXT_PRIVATE_OIDC_WELL_KNOWN",
"NEXT_PRIVATE_OIDC_CLIENT_ID",
"NEXT_PRIVATE_OIDC_CLIENT_SECRET",
feat: make oidc sign in button text configurable (#1209) Adds a configurable label for the OIDC connection's button.
2024-07-31 14:22:52 +02:00
"NEXT_PRIVATE_OIDC_PROVIDER_LABEL",
feat: allow oidc only signup and trust mail addresses (#1208) This change will allow for user registration when users are federated through oidc provider even if the general signup is disabled additionally the users email address can now be automatically set as trusted. This will force corporate users to signin using SSO instead of creating manual accounts.
2024-07-31 07:38:12 +02:00
"NEXT_PRIVATE_OIDC_ALLOW_SIGNUP",
"NEXT_PRIVATE_OIDC_SKIP_VERIFY",
feat: universal upload Implementation of a universal upload allowing for multiple storage backends starting with `database` and `s3`. Allows clients to put and retrieve files from either client or server using a blend of client and server actions.
2023-09-14 12:46:36 +10:00
"NEXT_PUBLIC_UPLOAD_TRANSPORT",
"NEXT_PRIVATE_UPLOAD_ENDPOINT",
S3Client: Add forcePathStyle
2024-03-22 15:46:22 +01:00
"NEXT_PRIVATE_UPLOAD_FORCE_PATH_STYLE",
feat: universal upload Implementation of a universal upload allowing for multiple storage backends starting with `database` and `s3`. Allows clients to put and retrieve files from either client or server using a blend of client and server actions.
2023-09-14 12:46:36 +10:00
"NEXT_PRIVATE_UPLOAD_REGION",
"NEXT_PRIVATE_UPLOAD_BUCKET",
"NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID",
"NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY",
feat: support cloudfront presign
2023-10-31 12:19:16 +11:00
"NEXT_PRIVATE_UPLOAD_DISTRIBUTION_DOMAIN",
"NEXT_PRIVATE_UPLOAD_DISTRIBUTION_KEY_ID",
"NEXT_PRIVATE_UPLOAD_DISTRIBUTION_KEY_CONTENTS",
chore: sign document
2023-09-25 15:57:10 +10:00
"NEXT_PRIVATE_SIGNING_TRANSPORT",
"NEXT_PRIVATE_SIGNING_PASSPHRASE",
"NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH",
"NEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS",
"NEXT_PRIVATE_SIGNING_LOCAL_FILE_ENCODING",
feat: use server-actions for authoring flow This change actually makes the authoring flow work for the most part by tying in emailing and more. We have also done a number of quality of life updates to simplify the codebase overall making it easier to continue work on the refresh.
2023-07-26 18:52:53 +10:00
"NEXT_PRIVATE_SMTP_TRANSPORT",
feat: add resend mail transport
2023-09-28 12:27:04 +10:00
"NEXT_PRIVATE_RESEND_API_KEY",
feat: use server-actions for authoring flow This change actually makes the authoring flow work for the most part by tying in emailing and more. We have also done a number of quality of life updates to simplify the codebase overall making it easier to continue work on the refresh.
2023-07-26 18:52:53 +10:00
"NEXT_PRIVATE_MAILCHANNELS_API_KEY",
"NEXT_PRIVATE_MAILCHANNELS_ENDPOINT",
"NEXT_PRIVATE_MAILCHANNELS_DKIM_DOMAIN",
"NEXT_PRIVATE_MAILCHANNELS_DKIM_SELECTOR",
"NEXT_PRIVATE_MAILCHANNELS_DKIM_PRIVATE_KEY",
"NEXT_PRIVATE_SMTP_HOST",
"NEXT_PRIVATE_SMTP_PORT",
"NEXT_PRIVATE_SMTP_USERNAME",
"NEXT_PRIVATE_SMTP_PASSWORD",
"NEXT_PRIVATE_SMTP_APIKEY_USER",
"NEXT_PRIVATE_SMTP_APIKEY",
"NEXT_PRIVATE_SMTP_SECURE",
feat: allow anonymous smtp authentication (#1204) Introduces the ability to use anonymous SMTP authentication where no username or password is provided. Also introduces a new flag to disable TLS avoiding cases also where STARTTLS is used despite `secure` being set to `false`
2024-07-09 02:39:59 +02:00
"NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS",
feat: use server-actions for authoring flow This change actually makes the authoring flow work for the most part by tying in emailing and more. We have also done a number of quality of life updates to simplify the codebase overall making it easier to continue work on the refresh.
2023-07-26 18:52:53 +10:00
"NEXT_PRIVATE_SMTP_FROM_NAME",
fix: fix eslint warnings
2023-08-31 13:33:13 +10:00
"NEXT_PRIVATE_SMTP_FROM_ADDRESS",
feat(email): support configurable SMTP service (#1447)
2024-11-06 11:00:59 +01:00
"NEXT_PRIVATE_SMTP_SERVICE",
feat: add vercel build script
2023-09-14 15:00:14 +10:00
"NEXT_PRIVATE_STRIPE_API_KEY",
feat: plan limits
2023-10-15 20:26:32 +11:00
"NEXT_PRIVATE_STRIPE_WEBHOOK_SECRET",
feat: show monthly new users
2023-11-05 12:48:05 +11:00
"NEXT_PRIVATE_GITHUB_TOKEN",
feat: add certificate and audit log pdfs
2024-04-10 15:13:18 +07:00
"NEXT_PRIVATE_BROWSERLESS_URL",
wip: background tasks
2024-05-15 18:55:05 +10:00
"NEXT_PRIVATE_JOBS_PROVIDER",
"NEXT_PRIVATE_TRIGGER_API_KEY",
"NEXT_PRIVATE_TRIGGER_API_URL",
fix: support custom inngest app ids
2024-08-14 16:26:58 +10:00
"NEXT_PRIVATE_INNGEST_APP_ID",
feat: add initial api logging (#1494) Improve API logging and error handling between client and server side.
2024-11-28 16:05:37 +07:00
"NEXT_PRIVATE_LOGGER_HONEY_BADGER_API_KEY",
fix: support inngest vercel integration
2024-08-14 13:49:47 +10:00
"INNGEST_EVENT_KEY",
feat: inngest provider
2024-06-14 13:53:48 +10:00
"NEXT_PRIVATE_INNGEST_EVENT_KEY",
feat: add document auth (#1029)
2024-03-28 13:13:29 +08:00
"CI",
feat: add vercel build script
2023-09-14 15:00:14 +10:00
"VERCEL",
"VERCEL_ENV",
"VERCEL_URL",
feat: add document auth (#1029)
2024-03-28 13:13:29 +08:00
"NODE_ENV",
feat: add vercel build script
2023-09-14 15:00:14 +10:00
"DEPLOYMENT_TARGET",
fix: unable to load font for signing
2023-11-24 16:17:54 +11:00
"FONT_CAVEAT_URI",
fix: use noto sans for text insertion on pdfs Use Noto Sans to gracefully handle inserting custom text on PDF's. Previously we were using Helvetica which is a standard PDF font but that would fail for any character that couldn't be encoded in WinANSI. Noto Sans was chosen as it has support for a large number of languages and glyphs with challenges now being adding support for CJK glyphs.
2024-05-23 13:07:37 +10:00
"FONT_NOTO_SANS_URI",
feat: add vercel build script
2023-09-14 15:00:14 +10:00
"POSTGRES_URL",
"DATABASE_URL",
fix: remove duplicate neon pooler (#990) ## Description Fixes the issue with Vercel preview deployments failing. It appears that the old `PGHOST` environment variable injected by neon was: `ep-snowy-snowflake-a2vc5pa2.eu-central-1.aws.neon.tech` It is now: `ep-snowy-snowflake-a2vc5pa2.eu-central-1-pooler.aws.neon.tech` Notice the `-pooler` being attached automatically to the `PGHOST`. ## References > The following changes were made to the [Neon Vercel Integration](https://vercel.com/integrations/neon): > >To ensure that users accessing a Neon database from a serverless environment have enough connections, the DATABASE_URL and PGHOST environment variables added to a Vercel project by the Neon integration are now set to a pooled Neon connection string by default. Pooled connections support up to 10,000 simultaneous connections. Previously, these variables were set to an unpooled connection string supporting fewer concurrent connections. https://neon.tech/docs/changelog https://neon.tech/docs/guides/vercel#manage-vercel-environment-variables
2024-03-07 18:17:28 +08:00
"DATABASE_URL_UNPOOLED",
feat: add vercel build script
2023-09-14 15:00:14 +10:00
"POSTGRES_PRISMA_URL",
chore: use env vars for tests
2023-10-05 09:12:56 +03:00
"POSTGRES_URL_NON_POOLING",
chore: use rust based cms signing
2024-03-15 22:26:09 +11:00
"GOOGLE_APPLICATION_CREDENTIALS",
chore: use env vars for tests
2023-10-05 09:12:56 +03:00
"E2E_TEST_AUTHENTICATE_USERNAME",
"E2E_TEST_AUTHENTICATE_USER_EMAIL",
"E2E_TEST_AUTHENTICATE_USER_PASSWORD"
wip: refresh design
2023-06-09 18:21:18 +10:00
]
fix: improve lingui configuration (#1388) ## Description Currently merge conflicts arise due to the compiled JS and PO translation files. This PR is a rework on how we handle extracting and compiling translations to streamline PRs and merging branches. ## Changes Made - Remove compiled translation files from being committed - Extract and compile translations only on build - Extract will still occur when commits land on main to sync and pull new translations with Crowdin
2024-10-09 14:13:52 +11:00
}
Reference in New Issue Copy Permalink