Daat is an experimental library meant to provide parameterized modules to #elixir.
Imagine that you have a module named UserService, that exposes a function named
By using parameterized, or higher-order modules, we can instead define a module that specifies an interface, and acts as a generator for modules of that interface. By then passing our dependencies to this generator, we are able to dynamically create new modules that implement our desired behaviour.
https://github.com/QuinnWilton/daat
  
  
  
  
  
  Imagine that you have a module named UserService, that exposes a function named
follow/2. When called, the system sends an email to the user being followed. It would be nice if we could extract actually sending the email from this module, so that we aren't coupling ourselves to a specific email client, and so that we can inject mocks into the service for testing purposes.By using parameterized, or higher-order modules, we can instead define a module that specifies an interface, and acts as a generator for modules of that interface. By then passing our dependencies to this generator, we are able to dynamically create new modules that implement our desired behaviour.
https://github.com/QuinnWilton/daat
SHML is a #shell framework for faster and easier script development. HTML has CSS, terminals have "ANSI/VT100 Control Sequences". SHML makes is easy to apply some style to your shell scripts without trying to remember that Yellow = 
https://github.com/odb/shml
  
  
  
  
  
  \033[33m instead Yellow is $(color yellow).https://github.com/odb/shml
Enforceable standards for your package.json scripts – like eslint for 
package.json scripts are an integral part of the Node dev experience: we use them to start our projects, run our dev environments and for all kinds of formatting, linting and tooling in general. They are just as important as our code. Yet we don't treat them with the same meticulous attention to detail. Scripts need ❤️ too!
One of the main goals for scriptlint was to enable people to use memorable and consistent script names across their projects. Tools like nps are great when you have to organize scripts with a certain level of complexity, but they don't help you with the structure and naming of your scripts.
This is where the scriptlint CLI shines: it makes best practices outlined in this documentation enforceable throughout your project(s). Think of it as eslint for your "scripts" section.
https://github.com/peerigon/scriptlint
#ts #js
  
  
  
  
  
  npm run!package.json scripts are an integral part of the Node dev experience: we use them to start our projects, run our dev environments and for all kinds of formatting, linting and tooling in general. They are just as important as our code. Yet we don't treat them with the same meticulous attention to detail. Scripts need ❤️ too!
One of the main goals for scriptlint was to enable people to use memorable and consistent script names across their projects. Tools like nps are great when you have to organize scripts with a certain level of complexity, but they don't help you with the structure and naming of your scripts.
This is where the scriptlint CLI shines: it makes best practices outlined in this documentation enforceable throughout your project(s). Think of it as eslint for your "scripts" section.
https://github.com/peerigon/scriptlint
#ts #js
Bringing full-stack to the JAMstack
Do you love the JAMstack philosophy but need a database-backed web app? Want great developer experience and easy scaling? Redwood is here! Built on #react, GraphQL, and Prisma, Redwood works with the components and development workflow you love, but with simple conventions and helpers to make your experience even better.
https://redwoodjs.com/
It also includes React Single File components: https://www.swyx.io/writing/react-sfcs-here/
#ts #js
  
  
  
  
  
  Do you love the JAMstack philosophy but need a database-backed web app? Want great developer experience and easy scaling? Redwood is here! Built on #react, GraphQL, and Prisma, Redwood works with the components and development workflow you love, but with simple conventions and helpers to make your experience even better.
https://redwoodjs.com/
It also includes React Single File components: https://www.swyx.io/writing/react-sfcs-here/
#ts #js
⚡Breaking news!
#npm is joining #github!
npm is a critical part of the #js world. The work of the npm team over the last 10 years, and the contributions of hundreds of thousands of open source developers and maintainers, have made npm home to over 1.3 million packages with 75 billion downloads a month. Together, they’ve helped JavaScript become the largest developer ecosystem in the world. We at GitHub are honored to be part of the next chapter of npm’s story and to help npm continue to scale to meet the needs of the fast-growing JavaScript community.
Looking further ahead, we’ll integrate GitHub and npm to improve the security of the open source software supply chain, and enable you to trace a change from a GitHub pull request to the npm package version that fixed it. Open source security is an important global issue, and with the recent launch of the GitHub Security Lab and GitHub’s built-in security advisories, we are well-positioned to make a difference. In addition, GitHub Sponsors has already paid out millions of dollars to open source contributors, and we’re excited to explore tasteful ways to extend it to the npm ecosystem.
https://github.blog/2020-03-16-npm-is-joining-github/
  
  
  
  
  
  #npm is joining #github!
npm is a critical part of the #js world. The work of the npm team over the last 10 years, and the contributions of hundreds of thousands of open source developers and maintainers, have made npm home to over 1.3 million packages with 75 billion downloads a month. Together, they’ve helped JavaScript become the largest developer ecosystem in the world. We at GitHub are honored to be part of the next chapter of npm’s story and to help npm continue to scale to meet the needs of the fast-growing JavaScript community.
Looking further ahead, we’ll integrate GitHub and npm to improve the security of the open source software supply chain, and enable you to trace a change from a GitHub pull request to the npm package version that fixed it. Open source security is an important global issue, and with the recent launch of the GitHub Security Lab and GitHub’s built-in security advisories, we are well-positioned to make a difference. In addition, GitHub Sponsors has already paid out millions of dollars to open source contributors, and we’re excited to explore tasteful ways to extend it to the npm ecosystem.
https://github.blog/2020-03-16-npm-is-joining-github/
#python
django-schema-graph makes a colourful diagram out of your Django models. The diagram is interactive, and makes it easy to toggle models and apps on/off at will.
https://github.com/meshy/django-schema-graph
It looks like this:
  
  
  
  
  
  django-schema-graph makes a colourful diagram out of your Django models. The diagram is interactive, and makes it easy to toggle models and apps on/off at will.
https://github.com/meshy/django-schema-graph
It looks like this:
Health checks for your documentation links.
Features:
- Concurrent and recursive checks
- Respect robots.txt restrictions (content only)
- External links checks
- Checking links within base url path
- Retries in the case of 502, 503 and 504 http errors
https://github.com/butuzov/deadlinks
#python
  
  
  Features:
- Concurrent and recursive checks
- Respect robots.txt restrictions (content only)
- External links checks
- Checking links within base url path
- Retries in the case of 502, 503 and 504 http errors
https://github.com/butuzov/deadlinks
#python
Introducing wax: a #wasm package runner!
wax is a tool intended to ease the use of command-line WebAssembly applications on your system. Similarly to wapm, that allows the installation and usage of packages and commands, wax enables use of CLI tools without installing them globally or changing your PATH.
https://wasmer.io/
  
  
  wax is a tool intended to ease the use of command-line WebAssembly applications on your system. Similarly to wapm, that allows the installation and usage of packages and commands, wax enables use of CLI tools without installing them globally or changing your PATH.
https://wasmer.io/
Lightweight Kubernetes. Easy to install, half the memory, all in a binary less than 40mb.
Great for:
- Edge
- IoT
- CI
- ARM
- Situations where a PhD in #k8s clusterology is infeasible
https://github.com/rancher/k3s
#go #devops
  
  Great for:
- Edge
- IoT
- CI
- ARM
- Situations where a PhD in #k8s clusterology is infeasible
https://github.com/rancher/k3s
#go #devops
GitHub
  
  GitHub - k3s-io/k3s: Lightweight Kubernetes
  Lightweight Kubernetes. Contribute to k3s-io/k3s development by creating an account on GitHub.
  Lens - The free, smart desktop application for managing Kubernetes clusters.
What makes Lens special?
- Amazing usability and end user experience
- Real-time cluster state visualization
- Resource utilization charts and trends with history powered by built-in Prometheus
- Terminal access to nodes and containers
- Fully featured role based access control management
- Dashboard access and functionality limited by RBAC
https://github.com/lensapp/lens
#k8s #ts
  
  What makes Lens special?
- Amazing usability and end user experience
- Real-time cluster state visualization
- Resource utilization charts and trends with history powered by built-in Prometheus
- Terminal access to nodes and containers
- Fully featured role based access control management
- Dashboard access and functionality limited by RBAC
https://github.com/lensapp/lens
#k8s #ts
YouTube
  
  Kontena Lens - The Smart Dashboard for Kubernetes
  Kontena Lens provides the most sophisticated user interface for managing Kubernetes clusters. It is the only management system you’ll ever need to take control of your clusters. Once you have tried it, there's no going back.
  papermill is a tool for parameterizing, executing, and analyzing Jupyter Notebooks.
Papermill lets you:
- parameterize notebooks
- execute notebooks
This opens up new opportunities for how notebooks can be used. For example:
- Perhaps you have a financial report that you wish to run with different values on the first or last day of a month or at the beginning or end of the year, using parameters makes this task easier.
- Do you want to run a notebook and depending on its results, choose a particular notebook to run next? You can now programmatically execute a workflow without having to copy and paste from notebook to notebook manually.
https://github.com/nteract/papermill
#python
That's how you execute notebooks:
And that's how you parametrize them:
  
  
  Papermill lets you:
- parameterize notebooks
- execute notebooks
This opens up new opportunities for how notebooks can be used. For example:
- Perhaps you have a financial report that you wish to run with different values on the first or last day of a month or at the beginning or end of the year, using parameters makes this task easier.
- Do you want to run a notebook and depending on its results, choose a particular notebook to run next? You can now programmatically execute a workflow without having to copy and paste from notebook to notebook manually.
https://github.com/nteract/papermill
#python
That's how you execute notebooks:
papermill local/input.ipynb s3://bkt/output.ipynb -p alpha 0.6 -p l1_ratio 0.1And that's how you parametrize them:
Introducing you misspell-fixer-action. It is a #github action that will fix your typos and grammar errors in both source code and documentation. 
And then send you a pull request with the fixes it made! It is an auto-formatter, but for natural languages.
https://github.com/sobolevn/misspell-fixer-action
Here's an example:
  
  
  
  
  
  And then send you a pull request with the fixes it made! It is an auto-formatter, but for natural languages.
https://github.com/sobolevn/misspell-fixer-action
Here's an example:
MeiliSearch is a powerful, fast, open-source, easy to use, and deploy search engine. The search and indexation are fully customizable and handles features like typo-tolerance, filters, and synonyms. 
https://github.com/meilisearch/MeiliSearch
#rust
  
  https://github.com/meilisearch/MeiliSearch
#rust
GitHub
  
  GitHub - meilisearch/meilisearch: A lightning-fast search engine API bringing AI-powered hybrid search to your sites and applications.
  A lightning-fast search engine API bringing AI-powered hybrid search to your sites and applications. - meilisearch/meilisearch
  K9s provides a terminal UI to interact with your Kubernetes clusters. The aim of this project is to make it easier to navigate, observe and manage your applications in the wild. K9s continually watches Kubernetes for changes and offers subsequent commands to interact with your observed resources.
https://github.com/derailed/k9s
#go #k8s #devops
  
  
  
  
  
  https://github.com/derailed/k9s
#go #k8s #devops
This plugin adds 
https://github.com/killercup/cargo-edit
#rust
  
  cargo add, cargo rm, and cargo update commands to #rust projects. Something I personally really miss.https://github.com/killercup/cargo-edit
#rust
GitHub
  
  GitHub - killercup/cargo-edit: A utility for managing cargo dependencies from the command line.
  A utility for managing cargo dependencies from the command line. - killercup/cargo-edit
  An operating system designed for hosting containers written in #rust
Bottlerocket focuses on security and maintainability, providing a reliable, consistent, and safe platform for container-based workloads. The base operating system has just what you need to run containers reliably, and is built with standard open-source components. Bottlerocket-specific additions focus on reliable updates and on the API. Instead of making configuration changes manually, you can change settings with an API call, and these changes are automatically migrated through updates.
Some notable features include:
- API access for configuring your system, with secure out-of-band access methods when you need them.
- Updates based on partition flips, for fast and reliable system updates.
- Modeled configuration that's automatically migrated through updates.
- Security as a top priority.
https://github.com/bottlerocket-os/bottlerocket
#devops
  
  Bottlerocket focuses on security and maintainability, providing a reliable, consistent, and safe platform for container-based workloads. The base operating system has just what you need to run containers reliably, and is built with standard open-source components. Bottlerocket-specific additions focus on reliable updates and on the API. Instead of making configuration changes manually, you can change settings with an API call, and these changes are automatically migrated through updates.
Some notable features include:
- API access for configuring your system, with secure out-of-band access methods when you need them.
- Updates based on partition flips, for fast and reliable system updates.
- Modeled configuration that's automatically migrated through updates.
- Security as a top priority.
https://github.com/bottlerocket-os/bottlerocket
#devops
GitHub
  
  GitHub - bottlerocket-os/bottlerocket: An operating system designed for hosting containers
  An operating system designed for hosting containers - bottlerocket-os/bottlerocket
  > I remember how careful I was the first time I opened a GitHub pull request. I read, re-read and triple-checked every one my comments before posting. It felt scary publishing my thoughts online because I was afraid people would judge me or misinterpret me.
> I enjoy working on open source just as much today as when I started. In this post I want to share some principles I try to follow to avoid unproductive discussions and invest my focus on what matters the most. Some of these dos and don'ts might be useful for maintainers, some for contributors. Whatever your role in open source, I hope you find some useful tips.
Dos and don'ts in open source: https://geirsson.com/open-source.html
  
  > I enjoy working on open source just as much today as when I started. In this post I want to share some principles I try to follow to avoid unproductive discussions and invest my focus on what matters the most. Some of these dos and don'ts might be useful for maintainers, some for contributors. Whatever your role in open source, I hope you find some useful tips.
Dos and don'ts in open source: https://geirsson.com/open-source.html
Geirsson
  
  Dos and don'ts in open source
  I remember how careful I was the first time I opened a GitHub pull request. I read, re-read and triple-checked every one my comments before posting. It felt scary publishing my thoughts online because I was afraid people would judge me or misinterpret me.