search

purton-tech / barricade

Quickly add user registration and logon to any application
https://hub.docker.com/r/purtontech/barricade
MIT License
187 stars 7 forks source link

The .env file #99

Open afidegnum opened 1 year ago

afidegnum commented 1 year ago

Hi, Can you please share your.envfile ? I'm trying to replicate your examples but got stuck in the middle. I will be grateful if you can add some workflow about the functionality of each modules as well I can't find an attached docs.

9876691 commented 1 year ago

@afidegnum

I always work in a devcontainer. You can see the general approach I use here https://rust-on-nails.com/docs/ide-setup/dev-env-as-code/

Once the container is running I have access to some aliases see https://github.com/purton-tech/barricade/blob/master/.devcontainer/aliases.bash

So I either run cwe or cwb

I will be grateful if you can add some workflow about the functionality of each modules as well I can't find an attached docs.

Do you mean the crates in the crates folder?

afidegnum commented 1 year ago

@ianpurton

Do you mean the crates in the crates folder? yes, i.e. in Encryption

I'm a bit confused about kdf_and_wrap and why should a password be stretched aside an individual password input at stretch_password

I'm trying to build a standalone API server which will be processing requests/responses from a standalone webassembly client. That's why I needed a kind of steps to go through to be able to achieve similar results like your app.

9876691 commented 1 year ago

I'm trying to build a standalone API server which will be processing requests/responses from a standalone webassembly client.

Are you building an end to end encrypted application? kdf_and_wrap is used in that case. If you need more information on that then this is a useful guide https://bitwarden.com/images/resources/security-white-paper-download.pdf

If you're not, then kdf and wrap might not be relevant.