We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We do have a table that manages the status of the application.
And we have an endpoint that checks whether the service is available:
But we don't have an endpoint that changes the status. So we would need a post request that sends/receives the following:
{ "status": "maintenance" }
or
{ "status": "running" }
Using a Fake API we could implement this in the dashboard. Maybe we can have a checkbox for this somewhere on the left side:
Ideally, when changing the checkbox, we send a message that forces the user to confirm it. Similar to what we do for the user deleting.
Check client implementation using a Fake-API. Later the backend implementation will follow.
Dev
The text was updated successfully, but these errors were encountered:
GET /api/status -> "running" or "maintenance" PUT /api/status -> {status: "running" or "maintenance"}
"running" or "maintenance"
{status: "running" or "maintenance"}
Sorry, something went wrong.
Thank you! @metemaddar could you implement the PUT endpoint in the API? Important is that the PUT endpoint is for superusers only.
cinaaaa
No branches or pull requests
Goal of this issue
We do have a table that manages the status of the application.
And we have an endpoint that checks whether the service is available:
But we don't have an endpoint that changes the status. So we would need a post request that sends/receives the following:
or
Using a Fake API we could implement this in the dashboard. Maybe we can have a checkbox for this somewhere on the left side:
Ideally, when changing the checkbox, we send a message that forces the user to confirm it. Similar to what we do for the user deleting.
Resources
Check client implementation using a Fake-API. Later the backend implementation will follow.
Deliverables
Branch to derive
Dev
The text was updated successfully, but these errors were encountered: