Create new incidents without having to rebuild/restart the server

[dudeisbrendan03]

Feature request

• [x] I confirm that this is a feature request rather than a question.

What problem does this feature solve?

Create new incidents without having to rebuild/restart the server.

What does the proposed API look like?

How should this be implemented in your opinion?

Are you willing to work on this yourself?**

[welcome[bot]]

Thanks for opening this issue, a maintainer will get back to you shortly! Be sure to follow the issue template! 🤓

[juliomrqz]

Hello, @dudeisbrendan03. Please, indicate how this is affecting you, and why it should be implemented. Thanks.

[dudeisbrendan03]

It's more from a convenience standpoint and it would also allow me to automatically generate incidents when issues occur with a simple script.

Having to restart the whole process isn't really that great and also is going to make my life a pain if I went to implement a way to automatically generate incident files.

[juliomrqz]

If you're using Statusfy in "Static Generated Mode", you need to regenerate the site every-time a change is made in order to hydrate the generated HTML files with latest changes.

If building time is an issue, you can use Statusfy in "Server Rendered Mode", you build once and deploy your incidents changes including the folder .statusfy.

We're planning to support other data sources as MySQL and PostgreSQL, so it will be not needed to redeploy the entire website when incidents changes are made.

[dudeisbrendan03]

Thanks, I'll take a look.

I've been putting incidents into content.

[juliomrqz]

Hi, @dudeisbrendan03. I invite you to leave your comment in the Statusfy Users issue when you start using Statusfy in your company or organization 🤓. Thanks!