Tinystatus: A tiny status page generated by a Python script • Hacker News Board

Yea, you can create a website on S3 and set up a Lambda trigger every minute. To schedule this, you can use a CloudWatch rule with a 'Schedule' expression to trigger the Lambda function.

Alternatively, you could use GitHub Actions and schedule the workflow to run every minute.

However, I prefer the Lambda approach.

Re: Tinystatus: A tiny status page generated by a Python script

#29

Post by remram » Thu, Sep 05, 2024, 1:43 PM UTC

8n4vidtmkvmk wrote: post #7

remram wrote: post #5

Earlier quoted context omitted.

> clean, responsive web page Consider adding a screenshot.

Why he need screenshot when there's a perfectly good demo?

The demo link is not in the README either. If it was, yes, I agree with you.

Re: Tinystatus: A tiny status page generated by a Python script

#30

Post by remram » Thu, Sep 05, 2024, 1:46 PM UTC

selcuka wrote: post #6

remram wrote: post #4

Why not put these .env variables inside the checks.yaml config file? What is the advantage of two config files with two separate syntaxes?

The idea is the values in .env files can be configured via environment variables, while checks.yaml is for things that can be hard coded. In this case it's a bit moot because the yaml file works like a database, but when you deploy this using, say, Docker or k8s, you can use a different method to configure environment variables and skip .env files.

Why can't I change the port of my database server via an environment variable? This would be required for e.g. Nomad support.

If this is a goal, why is it a goal for only half the configuration?