I hereby claim:
- I am rkzel on github.
- I am rkzel (https://keybase.io/rkzel) on keybase.
- I have a public key ASCftgx0VgNuEqTnKzJCP8F15tuQdAt5HGgwtEnmLbnEPQo
To claim this, I am signing this object:
This post links my 3Box profile to my Github account! Web3 social profiles by 3Box. | |
✅ did:muport:QmbiGG2Qn4tNVb4XtdoY54EV4d2nN3rt57A1uiqj6F5ZWT ✅ | |
Create your profile today to start building social connection and trust online at https://3Box.io/ |
1. How would you add an authentication microservice to haproxy? | |
There are two sides to this: one is interface to haproxy (or nginx or any other proxying solution in front of IPFS), the other is interface to blockchain and all the logic: authentication, caching data, etc. The former seems simple, the later seems complex. | |
Two possibilities are: | |
a) write a custom auth module encompassing all logic and work, | |
b) write a custom simple auth module that communicates with a separate microservice (most likely in form of simple HTTP(S) server). | |
After considering pros and cons the second option seems better, because: | |
- it will keep proxy side of thing simple and clean, |
#!/bin/bash | |
if [ "$#" -ne 1 ]; then | |
echo "Please provide path to applications" | |
exit 1 | |
fi | |
ARAGON=/usr/local/bin/aragon | |
APPS="address-book allocations dot-voting projects rewards" |
did:muport:QmZKYi8U6zG7MnPPA5WfozYuVsN6wxSivNHxeA4B8NpFWo | |
I hereby claim:
To claim this, I am signing this object: