If you are wondering where the data of this site comes from, please visit GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Peter Etelej peteretelej @Microsoft Nairobi, Kenya I enjoy building things and solving problems. Work on Azure at Microsoft. Fan of @golang @flutter @reactjs @vuejs docker

AzureAD/SCIMReferenceCode 52

Reference code to build a SCIM endpoint to automate provisioning

peteretelej/nasa 12

Go Library for accessing the NASA API, nasa CLI and apps

peteretelej/comet 10

Boostrap Desktop Apps with Go (wraps Electron in a neat cli)

peteretelej/jekyll-container 9

Jekyll Docker container for Github Pages

peteretelej/dserve 7

dserve - Directory Serve: Serve a static directory via HTTP / static website (with basic-auth authentication support)

peteretelej/jsonbox 5

Go wrapper / Client SDK for

peteretelej/gws 3

gws: go web server

peteretelej/kenyadecides 3

Kenya Election Results Live on Twitter

peteretelej/dockerfiles 2

Dockerfiles for useful container images


started time in 15 hours

fork waynemunro/computer-science

:mortar_board: Path to a free self-taught education in Computer Science!

fork in 16 hours


started time in 16 hours


release vercel/next.js


released time in a day


started time in a day

release grafana/grafana


released time in 2 days

release strapi/strapi


released time in 2 days

release vercel/next.js


released time in 2 days

release vercel/next.js


released time in 2 days


started time in 2 days

release vercel/next.js


released time in 2 days

issue commentAzureAD/SCIMReferenceCode

Missing documentation/comments about AAD long-lived bearer token

Yes, been struggling with trying to understand how to turn this into a multi-tenant enabled solution. Creating a fixed token per AD tenant doesnt make sense.

Would not checking the issued Azure AD token be better than a long lived secret?


comment created time in 3 days

release vercel/next.js


released time in 4 days


started time in 5 days


started time in 5 days

release vercel/next.js


released time in 6 days

release grafana/grafana


released time in 7 days

release vercel/next.js


released time in 7 days

release vercel/next.js


released time in 7 days

issue openedAzureAD/SCIMReferenceCode

Test suite assumes junk data is accepted by server

The junk data test suite the server ignores any junk data sent on a request and creates the resource regardless. Sending a 400 request and not creating the resource is an equally viable option.

created time in 7 days

issue openedAzureAD/SCIMReferenceCode

Resource Array is not required when no results are returned

The last two tests in the postman collection (Get all users and Get all groups). Assert that an empty resource array is returned on the body. Whilst scim specifies that this array is not a requirement when no results are returned see

created time in 7 days

issue commentAzureAD/SCIMReferenceCode

Postman GET /ResourceTypes expectation is sensitive to ordering

Not only that but the test checks. pm.expect(jsonData[0].endpoint).to.eql("/Users"); Which will never pass if the scim list response schema is followed (as it should be).


comment created time in 7 days

release vercel/next.js


released time in 8 days

issue openedAzureAD/SCIMReferenceCode

Request: More examples in WebHostSample - Users


Could there be more examples in the WebHostSample project please?

At least one for Users which has the best practice of extending the main library, with static data. And then it can be adapted to be used in other applications.


created time in 9 days

release grafana/grafana


released time in 9 days

fork pmutua/anastasia-a-zhivaeva

Full Stack JavaScript Developer | Architect

fork in 9 days