Repository navigation
Conversation
manage.py, or a dependency on Django in uv.lock, pyproject.toml or requirements.txt, is Django; any of those files is otherwise Python. Asked after go.mod and before package.json, because a Django site builds its front end with npm and is not a Node project. The starter pins the version from .python-version, or the floor requires-python sets, and builds with what the repository locks with: uv held to uv.lock, pip into .venv for requirements.txt, uv resolving afresh for a pyproject.toml alone, which is said. Django's adds collectstatic to the build, migrate as a deploy step and Gunicorn on the WSGI module manage.py names, and says when the settings have no STATIC_ROOT for the build step to use. A plain Python project is asked for its start: line rather than given a guess, unless gunicorn.conf.py already names the application. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… it; --wait follows the task A project recorded with `vallic link` is one answer for the whole machine, and the resolver read it before the git remote. Linked once, it answered in every checkout, including those whose remote names a different project, and a command run there acted on the linked one. - The git remote now answers first; the linked project only where it names no project (a fork, a mirror, no git). A flag and VALLIC_PROJECT still beat both. `link`'s help and messages say so. - A protected environment's question names the project as well as the environment: "Deploy to acme-production (Acme), which is protected?" Every project has a "production". - `--wait` follows the task the control plane names for the deployment (`task`, new there). It followed the deployment's own id as a task's; the two are numbered apart, so it found no such task, or another task whose ending it reported as the deploy's. Without a task named, the wait says where to look instead of guessing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
init: Python and Django
manage.py, or a Django dependency inuv.lock,pyproject.tomlorrequirements.txt, is detected as Django; any of those files otherwise means Python. Checked aftergo.modand beforepackage.json, since a Django site builds its front end with npm..python-versionor therequires-pythonfloor, and builds with what the repository locks with: uv held touv.lock, pip into.venvforrequirements.txt, uv resolving afresh for a barepyproject.toml(and says so).collectstaticin the build,migrateas a deploy step and Gunicorn on the WSGI modulemanage.pynames, with a warning when settings have noSTATIC_ROOT. Plain Python asks for itsstart:line unlessgunicorn.conf.pyalready names the app.resolve: a checkout's own project before the linked one
vallic link; the linked project is used only where the remote names none (a fork, a mirror, no git). A flag andVALLIC_PROJECTstill win over both.link's help and messages say so.--waitfollows the task the control plane names for the deployment (newtaskfield) instead of treating the deployment's id as a task id. Without a task named, it says where to look rather than guessing.api: environment servers
EnvironmentDetailexposesservers(machine ID and role), limited to what the caller may see. Nil only against a control plane that predates it.🤖 Generated with Claude Code