openstatushq / openstatus Goto Github PK

_{From SyncLinear.com | OPE-45}

This route will be publicly available and data is coming from our website.

_{From SyncLinear.com | ENG-32}

_{From SyncLinear.com | OPE-41}

Once in a while when I open farmako.openstatus.dev it throws a 500 error and then on refresh it starts working. It doesn't happen all the time. I wonder what it is, probably something related db?

_{From SyncLinear.com | OPE-52}

We should be able to edit a monitor

• Status → Pause/active
• Name
• Description

_{From SyncLinear.com | OPE-51}

Allow different locales

_{From SyncLinear.com | OPE-47}

https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap

_{From SyncLinear.com | OPE-35}

_{From SyncLinear.com | OPE-46}

_{From SyncLinear.com | OPE-46}

_{From SyncLinear.com | OPE-62}

Hey, I've noticed a minor spelling mistake in contact section of README.

I've opened a PR which fixes this issue.

create a shell page for settings

_{From SyncLinear.com | OPE-50}

• tsc
• lint
• …

_{From SyncLinear.com | OPE-22}

• check tremorlabs colors
• [ ]

_{From SyncLinear.com | OPE-44}

Whenever a ping is not 200-299, we should send a notification to the user.

Before starting, we should make sure to have a stable API around that.

For each integration, we should have a mapping function from our API to the service one.

_{From SyncLinear.com | OPE-38}

On the first request we should fetch the data and not rely on cache

There seems to be an issue with the z-index of the HoverCard on the landing page in Safari. The card is displayed behind the content below, if the card is rendered underneath.

The issue seems to discussed on the following page: https://ecomgraduates.com/blogs/news/fixing-z-index-issue-on-safari-browser

Demo

One solution would be to check if all relevant fields are present in the form before making the form submission. Alterly we can generate a random slug as we are already doing with workspaces.

When we resize window using button from top right between close and minimize, the background stays on the old position after switching to full screen again.

Pages: All pages

Use contentlayer for easy file management on github. Can be used for:

• changelog
• blog

Install reading-time for good read estimation.

Support mdx.

Some repos to get inspiration from:

• mxkaske/doxi
• mxkaske/mxkaske.dev
• shadcn/taxonomy
• steven-tey/dub

_{From SyncLinear.com | OPE-37}

Create a new app with nextra with the doc
How to contribute to the project
How to set up env !

when I click here it directs me to the path but relative with the subdomain,

there are two solutions to that

• putting the full URI
• redirect on subdomain level

it's optional, we should not ask if they want a preferred region to make the form simpler

_{From SyncLinear.com | OPE-60}

Some users did not select a frequency and they were able to create a monitor, it could lead to a bad ux

_{From SyncLinear.com | OPE-61}

my status page is empty and I have made a monitor to ping my site
and also there's no data recorded !!

I have been added it 8h ago

I noticed a small typo in the email I received after joining the waitlist. We are missing Y in the highlighted paragraph.

I know it's a small fix and I would have looked into repo, before creating this Issue, but I am on my phone and unable to do it properly.

Apologies, if I reported it in a wrong place 🙏.

We should improve DX for new development

A single command should launched a local dev

_{From SyncLinear.com | OPE-54}

_{From SyncLinear.com | OPE-49}

_{From SyncLinear.com | OPE-19}

We should save name and user in the user table to avoid extra calls to clerk

_{From SyncLinear.com | OPE-57}

How do you look at converting it to a public project with subdomain or path?

See example: https://github.com/fatih-yavuz/my-links

The sustainability of the project can also be ensured by adding certain limits that anyone can use by signing up with a dashboard.

https://twitter.com/hyrousek/status/1679150301281157123?s=20

_{From SyncLinear.com | OPE-48}

Let's release a public roadmap to provide a clearer view of the project.

First of all, the requests are working super well, awesome!

I've noticed most of the bugs like "data not showing" and related are due to how date is being handled.
When we access the monitor page it should pick the data from the current day, right now it is fetching from the previous day; if we set the date to today, it is possible to verify it. It also happens on the status page, only there we can't set the date to validate this issue.

_{From SyncLinear.com | OPE-58}

On status page tooltip don't work on mobile

_{From SyncLinear.com | OPE-53}

"OpenStatus is an open source alternative to your current monitoring service with beautiful status page.
should be
OpenStatus is an open source alternative to your current monitoring service with a beautiful status page.

Should fix the tsconfig.ts to run the migrate script

As a quick fix run the migration with

Bun arc/migrate.ts

Error Description:

When running the steps of the repository and using pnpm dev, I encounter the following error when trying to access localhost:3000:

web:dev: ❌ Invalid environment variables: { JITSU_HOST: [ 'Required' ], JITSU_WRITE_KEY: [ 'Required' ] }
web:dev: - wait compiling /_error (client and server)...
web:dev: - error ../node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@t3-oss/env-core/dist/index.mjs (1:501) @ y
web:dev: - error Error: Invalid environment variables
web:dev:     at y (webpack-internal:///(rsc)/../../node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@t3-oss/env-core/dist/index.mjs:11:91)
web:dev:     at h (webpack-internal:///(rsc)/../../node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@t3-oss/env-core/dist/index.mjs:15:31)
web:dev:     at eval (webpack-internal:///(rsc)/../../packages/analytics/env.ts:9:72)
web:dev:     at (rsc)/../../packages/analytics/env.ts (/home/user/Documentos/openstatus/apps/web/.next/server/app/page.js:5960:1)
web:dev:     at __webpack_require__ (/home/user/Documentos/openstatus/apps/web/.next/server/webpack-runtime.js:33:42)
web:dev:     at eval (webpack-internal:///(rsc)/./src/env.ts:8:83)
web:dev:     at (rsc)/./src/env.ts (/home/user/Documentos/openstatus/apps/web/.next/server/app/page.js:3774:1)
web:dev:     at __webpack_require__ (/home/user/Documentos/openstatus/apps/web/.next/server/webpack-runtime.js:33:42)
web:dev:     at eval (webpack-internal:///(rsc)/./src/lib/tb.ts:7:62)
web:dev:     at (rsc)/./src/lib/tb.ts (/home/user/Documentos/openstatus/apps/web/.next/server/app/page.js:3785:1) {
web:dev:   digest: undefined
web:dev: }
web:dev: null

Error Explanation:

The error message indicates that there are invalid environment variables, specifically JITSU_HOST and JITSU_WRITE_KEY. The error seems to be occurring in the file env-core/dist/index.mjs from the @t3-oss/env-core package version 0.6.0 with TypeScript version 5.1.6 and Zod version 3.21.4. The specific line where the error is triggered is line 1, column 501 (1:501).

The error traceback suggests that the issue is related to the file analytics/env.ts at line 9, column 72, and the file src/env.ts at line 8, column 83. Additionally, there is a reference to src/lib/tb.ts at line 7, column 62.

analytics/env.ts content:

import { createEnv } from "@t3-oss/env-core";
import { z } from "zod";

export const env = createEnv({
  server: {
    JITSU_HOST: z.string(),
    JITSU_WRITE_KEY: z.string(),
  },
  runtimeEnv: {
    JITSU_HOST: process.env.JITSU_HOST,
    JITSU_WRITE_KEY: process.env.JITSU_WRITE_KEY,
  },
});

Steps Taken:

1. Checked the .env file to ensure that JITSU_HOST and JITSU_WRITE_KEY are properly defined, but they seem to be correctly set.
2. Verified the env.ts file and ensured that the variables are being imported and accessed correctly.

Expected Behavior:

When executing pnpm dev and accessing localhost:3000, the application should run without any errors related to invalid environment variables.

Additional Information:

Operating System: Ubuntu 22.04.2 LTS (Jammy Jellyfish)

Node.js Version: 18.16.0

pnpm Version: 8.6.10

we should see some content bellow the title

_{From SyncLinear.com | OPE-59}

this way we lead to too much miss good analytics, as edge will use different ips each time even for the same region

so is there's a way to prevent that ?!

_{From SyncLinear.com | OPE-39}

Description

Since all blog routes /blog/* are public it's better to include them in the sitemap to make the blogs easily discoverable on the web🚀

I'll open a PR fixing this issue.

_{From SyncLinear.com | OPE-40}

The monitor datapage is blank

Will there be a GitHub sign up option any time soon?

i would like to be assigned to this

i'm trying to play with this project but i got this error

web:dev: - ready started server on 0.0.0.0:3000, url: http://localhost:3000
web:dev: ❌ Invalid environment variables: { DATABASE_URL: [ 'Required' ] }
web:dev: Error: Invalid environment variables
web:dev: at c (file:///C:/Users/Adam/openstatus-main/node_modules/.pnpm/@t3-oss[email protected][email protected][email protected]/node_modules/@t3-oss/env-core/dist/index.mjs:1:426)

i know it's related to env var but wich one i cant find tree of it or where's came from

aslo is there's any env file except this ?