andineck

auth with microservices

Authorization and Authentication are hard. when you only have to implement them once (as you do within a monolith) instead of over and over again, it makes the developer happy :-), and maybe leads to less implementation failures.

When you have a bunch of microservices, this is something that has to be considered.

Implement it once or in every microservice, or something in between?

alopresto

If anyone is interested in setting up their system to automatically (or manually) sign their git commits with their GPG key, here are the steps:

1. Generate and add your key to GitHub
2. $ git config --global commit.gpgsign true ([OPTIONAL] every commit will now be signed)
3. $ git config --global user.signingkey ABCDEF01 (where ABCDEF01 is the fingerprint of the key to use)
4. $ git config --global alias.logs "log --show-signature" (now available as $ git logs)
5. $ git config --global alias.cis "commit -S" (optional if global signing is false)
6. $ echo "Some content" >> example.txt
7. $ git add example.txt
8. $ git cis -m "This commit is signed by a GPG key." (regular commit will work if global signing is enabled)

bszwej

const http = require('http');
const server = http.createServer();

server.on('request', (request, response) => {
    let body = [];
    request.on('data', (chunk) => {
        body.push(chunk);
    }).on('end', () => {
        body = Buffer.concat(body).toString();

carlosedp

// Run with scala-cli httpserver.scala
// Save logback.xml file into ./resources dir
// Before generating native image binary, run first as above and make a real access to the URL
// so the native-image-agent can generate the metadata in ./resources dir.
// Then generate native image binary with: scala-cli package --native-image httpserver.scala
//> using scala "3.3.0"
//> using lib "dev.zio::zio:2.0.15"
//> using lib "dev.zio::zio-http:3.0.0-RC2"
//> using lib "dev.zio::zio-logging-slf4j2::2.1.13"
//> using lib "ch.qos.logback:logback-classic:1.4.8"