vault backup: 2025-02-26 10:10:32

README.md

@@ -133,7 +133,7 @@ The naming of functions is important. There are basically two styles:
 
 The task file function use the first style. The name of function starts with the action followed by the object. The object definition can be singular and/or plural.
 
-**Examples for actions**: <span id="actions">activate, install, dev, develop, init, build, start, update, remove, delete, enable, disable, template, convert, create, edit, change, get, set, patch, fetch, generate, push, pull, import, export, list, publish, release, test, setup, prepare, restart, stop, store, restore, translate, upgrade, zip, visualize, sync, switch, run, reset, load, dump, checkout, commit, drop, deploy, handle, trigger, render, lint, uninstall, split, parse, fix, refactor, chore, style, cat, ls, rm, serve, help, show, filter, limit, login, logout, encrypt, decrypt</span>
+**Examples for actions**: <span id="actions">activate, install, dev, develop, init, build, start, update, remove, delete, enable, disable, template, convert, create, edit, change, get, set, patch, fetch, generate, push, pull, import, export, list, publish, release, test, setup, prepare, restart, stop, store, restore, translate, upgrade, zip, visualize, sync, switch, run, reset, load, dump, checkout, commit, drop, deploy, handle, trigger, render, lint, uninstall, split, parse, fix, refactor, chore, style, cat, ls, rm, serve, help, show, filter, limit, login, logout, encrypt, decrypt, upload, download</span>
 
 **Examples for objects**: <span id="objects">env, venv,  submodule, container, database, snippet, model, module, repo, mail, doc, dependency, view, user, vault, file, host, node, log, password, hash, script, requirement, part, component, system, workspace, image, process, state, platform, dir, folder, readme, overview, lang, level, request, response, result, worker, server, proxy, workflow, volume, network, package, field, value, secret</span>