Search Results for "remote" - Page 3

fx is a tool to help you do Function as a Service on your own server, fx can make your stateless function a service in seconds, with both Docker host and Kubernetes cluster supported. The most exciting thing is that you can write your functions with most programming languages.

...By "distributed", we mean that code reviews are stored inside of the repository as git objects. Every developer on your team has their own copy of the review history that they can push or pull. When pulling, updates from the remote repo are automatically merged by the tool. This design removes the need for any sort of server-side setup. As a result, this tool can work with any git hosting provider, and the only setup required is installing the client on your workstation. he git command-line tool is configured with the credentials it needs to push to and pull from the remote repos. ...

...Ideal for development where you can push your WIP branch to the cluster to test. Reference implementation for writing git-based automation on your server. Fork this repo and create your own CRD + controller + git remote hook that can do things on the Kubernetes cluster. No dependencies except native tooling (git, kubectl). Plug and play installation. Simple public key-based authentication. RBAC ready - Control access to git remotes using RBAC. Support for namespace-based multi-tenancy - Remotes can only deploy to their own namespace. No assumptions about the repository structure.

hub is an extension to command-line git that helps you do everyday GitHub tasks without ever leaving the terminal. Hub is a tool that wraps git in order to extend it with extra functionality that makes it better when working with GitHub. Available commands are split into two groups: those that are already present in git but that are extended through hub, and custom ones that hub provides. Most hub commands are supposed to be run in a context of an existing local git repository. Hub will...

CRFS is a user-space filesystem that mounts container images directly from remote registries, exposing them as ordinary directories without a full “pull” step. Instead of downloading entire layers upfront, it fetches file ranges on demand and maintains a content-addressed cache, yielding fast startup and lower bandwidth for large images. The system speaks registry protocols and understands layered image formats, resolving whiteouts and overlays so the mounted view matches what a container runtime would see. ...

...If your repository has local changes the containers will only be tagged as latest, otherwise the containers will be tagged as latest, COMMIT_ID & BRANCH_NAME. Now your Git commit tree is reproduced in your local docker repository. Use captain test to run your tests. Use captain push to send selected images to the remote repository. From the other side, you can now pull the feature branch you want to test, or create distribution channels (such as 'alpha', 'beta', 'stable') using git tags that are propagated to container tags. Captain will automatically configure itself with sane values without the need for any pre-configuration.

...It defaults to origin for the remote repository. Time data can be retrieved from the remote repository by fetching.