Search Results for "users"

...Status checks and dry runs show the target directories, prompt source, and planned modifications before deployment. Layered uninstall removes only the newest deployment while preserving unrelated configuration changes. Users can restore hooks separately, deploy to multiple discovered directories, and supply their own instruction file.

...Your Buildbot installation has one or more masters and a collection of workers. The masters monitor source-code repositories for changes, coordinate the activities of the workers, and report results to users and developers. Workers run on a variety of operating systems. You configure Buildbot by providing a Python configuration script to the master. This script can be very simple, configuring built-in components, but the full expressive power of Python is available. This allows dynamic generation of configuration, customized components, and anything else you can devise. ...

...Config is driven by a simple INI per OS, so app IDs, entry points, requirements, and paths are declarative. PyAppExec also manages user-level caches/state, log rotation, and GUI suppression preferences letting you ship Python apps without asking end users to touch Python, virtualenvs, or package managers.

Piku is a minimalistic Platform as a Service (PaaS) that enables users to deploy applications to their own servers using simple Git push commands.

...You can make switches active for a certain percentage of visitors, all visitors to a particular host in a cluster, or if a particular string is present in the query string. Furthermore you can easily create your own conditions to do fancier things like geo-targeting, specific users, etc. In short, Switchboard turns you into a continuous deployment ninja.