AMS components
Custom reusable ams components for Expo/React Native apps
Pipedream Momentum AMS Components
Use _AMS CHECKOUT_ as an ES module.
AMS client library for node.js
Stylesheets for all components from the Amsterdam Design System and some general utilities. Use it to apply the visual design of the City of Amsterdam to your HTML elements or non-React components.
Generic styling for data.amsterdam.nl
NodesJS AMS development environment
Distance and similarity functions to compare vectors
All design tokens from the Amsterdam Design System. Use it to apply its visual design to your website or application.
Stylesheets for all components from the Amsterdam Design System and some general utilities. Use it to apply the visual design of the City of Amsterdam to your HTML elements or non-React components.
All design tokens from the Amsterdam Design System. Use it to apply its visual design to your website or application.
A shareable eslint config used in projects created by Story of AMS. The eslint config relies on several eslint plugins and implements prettier as a rule set.
Admin Materials System.
Use _AMS CHECKOUT_ as an ES module.
MCP server for Bambu Lab 3D printers with STL manipulation, slicing, and print management
A theme for Canvas AMS made by Instructure Inc.
Microsoft Omnichannel AMSClient
Fast, expressive styling for React.
All My Sons URL Shortner utility
TypeScript client for Redis Agent Memory Server (AMS) with automatic conversation summarization and context window management
Improve the debugging experience and add server-side rendering support to styled-components
Allmysons React UI Kit.
React component to render markdown
Repository for generic common code in Watermark Community Church applications
# Footman This gem is still growing. ## Installation Depends upon having reprepro tool installed (if debian based) or createrepo installed (if red hat based). Ruby 1.9.+ is required to use this gem. 'createrepo' (rpm) tool does not require any pre-setup to the repository or watched directory. - - - 'reprepro' (deb) tool requires pre-setup. The repository directory for deb files must contain: <pre><code> conf/ conf/distributions conf/options conf/override.precise </pre></code> options file is empty, but needed to make reprepro happy distributions file will contain: <pre><code>Origin: Tyler Label: Tyler's Personal Debs Codename: precise Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.precise DscOverride: override.precise Origin: Tyler Label: Tyler's Personal Debs Codename: lenny Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.lenny DscOverride: override.lenny </code></pre> Note that the code name is for each distribution repository you support. for each distribtuion repository you support there must be an override file. override file can be left empty, footman will fill it out when a new package is added. The watched directory must have sub directorys named after each of the distribution repositories you support. For example my watched directory at /path/ will have two subdirectories: <pre><code>/path/lenny/ /path/precise/</code></pre> Packages must be dropped into the subdirectory that corrosponds with the distribution they were built on. - - - Add this line to your application's Gemfile: gem 'footman' And then execute: $ bundle Or install it yourself as: $ gem install footman Or locally: $ gem build footman.gemspec $ gem install footman --local ## Usage footman path/to/watch path/to/repo ## Contributing 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request