ambition-legacy/backend/README.md

# Backend Usage

In order for this to work, you need to have [sqlite3](https://sqlite.org)
installed on your system. Once you do, make a databse called `users.db`
and initialize it with the `sql/init.sql` script:

```sh
$ cat sql/init.sql | sqlite3 users.db
```

You also need to create a `.env` file with the following variables:

- `JWT_SECRET`: Required. A cryptographically secure string used to encode
tokens.
- `PORT`: Optional. Overrides the default port of `7741`
feat(backend): Create Users and Get JWT Introducing a unified signup and login API. You can post to the /user route with credentials (so far just name and password), and if the user doesn't exist, we create the user and return a token. If the user does exist, if the password inputted matches the database password, we return a token for that user, else we return an error. i've never wanted to kms more during a programming session 2023-07-26 21:16:25 +01:00			`# Backend Usage`

			`In order for this to work, you need to have [sqlite3](https://sqlite.org)`
			installed on your system. Once you do, make a databse called `users.db`
			and initialize it with the `sql/init.sql` script:

			```sh
			`$ cat sql/init.sql \| sqlite3 users.db`
			```

feat(backend): update and delete users The title says most of it. For authentication, the token gotten from the POST method can be put as a 'Token' header. It's then validated before being used. Other changes caused by this update are: - Fixed a bug where the creation token was unusable due to lacking the user password hash - Changed the signing method to HMAC, requiring a string for encryption This is mentioned in the README.md 2023-07-28 18:17:01 +01:00			You also need to create a `.env` file with the following variables:

			- `JWT_SECRET`: Required. A cryptographically secure string used to encode
			`tokens.`
			- `PORT`: Optional. Overrides the default port of `7741`