Start project¶
Usage: start-project [-r] [--skip-new-version-check] [-b BLUEPRINT] [-l] PROJECT_NAME [DIRECTORY] [-h] [--completion COMPLETION]
Initialize a new django project the falco way.
Options
[-r, --root] Consider the specified directory as the root directory.
[--skip-new-version-check] Do not check for new version.
[-b, --blueprint BLUEPRINT] The blueprint to use to generate the project.
[-l, --local] Use a local copy of the blueprint if it exists.
Arguments
PROJECT_NAME Name of the project to create.
[DIRECTORY] Directory to create project in.
Help
[-h, --help] Show this message and exit.
[--completion COMPLETION] Use `--completion generate` to print shell-specific completion source. Valid options: generate, complete.
Initialize a new django project the falco way. This project-starter makes several assumptions; we’ll go through the most important choices I made in the next couples of sections. I’ll list some alternatives below in case you don’t agree with my choices. But even if you choose to use an alternative, most commands can still be useful to you, and the guides are not particularly tied to the generated project. So, even with another project-starter, Falco can still bring you value.
$ falco start-project myproject
Note
The authors key of the [tool.project] section in the pyproject.toml is set using your git global user
configuration. If you haven’t set it yet, see this page.
The subsequent sections will delve deeper into the folder structure, package choices, and provide guidance on deploying your project.
Alternative starters¶
Here are some alternative project starters that you can consider if the falco starter is not to your liking: