bakku / easyalert Goto Github PK

Users should be able to delete their account using their token in the Authorization header.
Request:

DELETE /api/users/me
Authorization: Bearer 12345

Response:

HTTP 204

For development/testing we need some kind of mailcatcher.

When an alert is successfully sent the status and sent_at should be updated, on failure only the status should be updated.

This ticket also includes some kind of background job/worker logic so the API can enqueue mailing jobs.

Request:

POST /api/alerts
Authorization: Bearer 12345

{
    "subject": "Hello!",
    "message": "This is a test message"
}

Response:

HTTP 201 Created

Users should be able to update their email and password using their token in the Authorization header. It should also be possible to only update the email or only update the password.

Request:

PUT /api/users/me
Authorization: Bearer 12345

{
    “email”: “[email protected]”,
    “password”: “12345”    
}

Response:

HTTP OK

{
    "token": "12345"
}

The users table is missing indices for email and token.

Also the schema.sql has to be updated.

In case a token or the password is comprimised, users should be able to refresh their token.

Request:

PUT /api/auth/refresh
Authorization: Token 12345

Response:

HTTP OK

{
    “token”: “67890”
}

There are a few things that should be changed. Easyalert should be terminal-first and we probably have to save subject instead of having a name...

The http server currently sets up the postgres repositories, this should only be done in main.go.

• Build it
• Deploy it
• Test it
• Publish it on reddit

The admin flag is not needed. Admins can just use a database client.

Request:

GET /api/alerts
Authorization: Bearer 12345

Response:

[
    {
        “subject”: “Hello!”,
        “status”: “sent”,
        “sent_at”: “2018-01-01T01:00:00Z”,
        “created_at”: “2018-01-01T00:00:00Z”
    },
    …
]

• Setup database
• Setup server environment using systemd
• Setup deployment

If no accept header is sent, easyalert will assume that the request came from a terminal.
It will then return text instead of JSON and will provide helpful curl commands for further usage
of the API.

Try to refactor the API as far as possible.

Furthermore add a ?silent parameter so the terminal version does not produce too much output

What is needed:

• Server
• Domain + Email

Maximum budget: 10 $/€ per month, better would be 5 $/€

When creating a user that already exists the API just returns:

{
  "error": "User could not be created. Verify that you sent valid data."
}

A more specific error however should be returned. E.g.:

{
  "error": "Email is already taken."
}

It is also possible to send a user without an email or a password. Both should be validated as well.

Alerts are the entity that contain all the information of the alert which should be sent.

Table structure:

id BIGSERIAL PRIMARY KEY
subject TEXT NOT NULL
status smallint NOT NULL
sent_at TIMESTAMP DEFAULT NULL
user_id BIGINT NOT NULL REFERENCES users(id) ON DELETE CASCADE
created_at TIMESTAMP NOT NULL
updated_at TIMESTAMP NOT NULL

Implement the following endpoint:

POST /api/users/auth
{
    "email": "[email protected]",
    "password": "test1234"
}

Response 200
{
    "token": "123456789"
}

The endpoint should check the credentials of the user and return the token of the user.

Currently the API does not return for any API endpoint Content-Type: application/json.