Commit Graph

10 Commits (e571a698202fa2ed8a3565ec2eb147b2b98b2246)

Author SHA1 Message Date
absc e571a69820 Use crypto:rand_seed().
It's cryptographically strong and set a better state for the
pseudo-random number generator.
2024-07-27 13:16:05 +02:00
absc ab3ca1ec64 No need to use an additional variable just to compose the salted pass. 2024-07-27 12:38:30 +02:00
absc 80af46c6be Just use the classic POST form.
JSON doesn't make any sense in this case.
2024-07-27 12:36:14 +02:00
absc 895e0a5330 Enter the user handler API.
For now it handles PUTs, to create new users. It's still a
partial implementation and there is no documentation yet.

POST, PATCH and DELETE will arrive later to handle other users
operations.
2024-07-27 01:57:34 +02:00
absc 285f4ad402 Correct the callback matching for the ProvidedCallback function. 2024-07-25 01:18:00 +02:00
absc 8f7481d785 Use the REST handler instead of the default one.
This makes the code simpler and more manageable.
2024-07-24 23:32:16 +02:00
absc 03b76bddf2 No need for the bucket to be configurable.
While there, create the bucket for the users during initialization.
2024-07-23 23:42:31 +02:00
absc 3280596836 Skeleton for the storage bootstrap.
We want to automate this, for example, when deploying in a docker
container.

A bunch of static files will be loaded into the storage, in order
to be served to the clients.
2024-07-23 23:15:36 +02:00
absc 65d6e5fa05 File committed as error. 2024-07-23 22:59:39 +02:00
absc 1f243b16d3 Import the initial dudeswave code.
At this point it handles only GETs, giving back plain text
responses in case of errors.

The intention is to also produce some static pages for those,
where the CSS we will chose applies.

Other APIs will be managed through their respective handlers,
whose routes will be setup before this one.
2024-07-23 22:52:57 +02:00