diff --git a/.changeset/spotty-walls-flow.md b/.changeset/spotty-walls-flow.md new file mode 100644 index 00000000000..5122f128c68 --- /dev/null +++ b/.changeset/spotty-walls-flow.md @@ -0,0 +1,5 @@ +--- +"@trigger.dev/sdk": patch +--- + +Automatically pickup on the TRIGGER_WSS_URL for the wss endpoint diff --git a/README.md b/README.md index 22482562908..e75024b20f7 100644 --- a/README.md +++ b/README.md @@ -172,7 +172,7 @@ new Trigger({ One of the most powerful features of Trigger.dev is the [runs page](https://docs.trigger.dev/viewing-runs). All of the steps in a workflow, including the initial event, can be viewed in detail. See the status / output of each step, the logs, rich previews, errors and much more. - + diff --git a/apps/webapp/Dockerfile b/apps/webapp/Dockerfile index c93fc6f5f31..fbad25cd232 100644 --- a/apps/webapp/Dockerfile +++ b/apps/webapp/Dockerfile @@ -42,6 +42,7 @@ ENV NODE_ENV production RUN pnpm run generate RUN pnpm run build --filter=webapp... RUN pnpx prisma migrate deploy --schema apps/webapp/prisma/schema.prisma +RUN pnpm run db:seed --filter=webapp # Runner FROM node:16-bullseye AS runner diff --git a/apps/webapp/app/components/LoginPromoPanel.tsx b/apps/webapp/app/components/LoginPromoPanel.tsx index 6363c26b538..d0acf36801a 100644 --- a/apps/webapp/app/components/LoginPromoPanel.tsx +++ b/apps/webapp/app/components/LoginPromoPanel.tsx @@ -4,67 +4,99 @@ import { CloudArrowUpIcon, WrenchScrewdriverIcon, } from "@heroicons/react/24/outline"; +import { TemplateListItem } from "~/presenters/templateListPresenter.server"; +import { Panel } from "./layout/Panel"; +import { Body } from "./primitives/text/Body"; +import { Header2, Header3 } from "./primitives/text/Headers"; -export function LoginPromoPanel() { +export function LoginPromoPanel({ template }: { template?: TemplateListItem }) { return (
- Write workflows by creating triggers directly in your code. These - can be 3rd-party integrations, custom events or on a schedule. -
-+ Write workflows by creating triggers directly in your code. + These can be 3rd-party integrations, custom events or on a + schedule. +
+- When your server runs, your workflow will be registered and you - can authenticate with any APIs you’re using. -
-- Test your workflow by triggering them manually in your dashboard. - Follow it as it runs step-by-step. -
-+ When your server runs, your workflow will be registered and you + can authenticate with any APIs you’re using. +
++ Test your workflow by triggering them manually in your + dashboard. Follow it as it runs step-by-step. +
+- Deploy your new workflow as you would any other code commit and - inspect each workflow run in real time. -
-+ Deploy your new workflow as you would any other code commit and + inspect each workflow run in real time. +
+