Status: alpha.
initx python myapp
initx node myappThis creates:
myapp/myapp/venv/myapp/main.pymyapp/requirements.txtmyapp/.gitignoremyapp/README.md
For Node.js this creates:
myapp/myapp/package.jsonmyapp/index.jsmyapp/.gitignoremyapp/README.md
initx python <name> [--path <directory>] [--no-venv]
initx node <name> [--path <directory>]python: selects the Python project templatenode: selects the Node.js project template<name>: the directory name for the generated project--path: sets the parent directory where the project will be created--no-venv: skipspython -m venv venv
initx python ...requirespythonorpython3initx node ...requires bothnodeandnpm
For Python projects, Init prefers python3 when both python3 and python exist, and falls back to python only when python3 is unavailable.
Using . instead of a project name tells Init to use the current target directory directly.
Examples:
initx python .
initx node .
initx python . --path ~/empty-folderRules:
- the target directory must already exist or be resolvable by
--path - the target directory must be empty
- Init will refuse to write into a non-empty directory
initx python myapp
initx python myapp --path ~/code
initx python myapp --no-venv
initx python .
initx node myapp
initx node myapp --path ~/code
initx node .initx <platform> . initializes the current directory, but only if it is empty.