.graphifyrc is a small, committed file that tells Graphify Local the things it can’t work out on its own. Most repositories never need one. You add it when an extension means different languages in different projects, or when your graph is too big for the default HTML view.
Use
.graphifyrc when files land in the wrong language (a .inc parsed as Pascal instead of PHP, a .m as Objective-C instead of MATLAB), or when git hooks should write graph.html with a different node limit. For per-run settings, such as models and output paths, use environment variables.How it works
Graphify reads<root>/.graphifyrc once per scan, where <root> is the folder you pass to extract, update, or watch. The format is deliberately plain:
- One
key=valueper line. #starts a comment.- Blank lines are ignored.
Configure
string
Treat every file with extension
<ext> as the named language for classification, extractor choice, and cross-file resolution. Write <ext> with or without its leading dot. The value is either a language name or an extension Graphify already understands, such as .php or .ts.integer
Node limit baked into the git hooks that
graphify hook install writes. Graphs larger than this skip graph.html. An explicit GRAPHIFY_VIZ_NODE_LIMIT on the command line still wins.Language names you can use
Any extension Graphify supports works as a value too, for example
language.tpl=.ts. If a value isn’t valid, Graphify prints [graphify] warning: ignoring .graphifyrc: ... and skips the whole file, so a typo never half-applies.
See it in action
.graphifyrc
What changes
- Files with an overridden extension are parsed by that language’s extractor and resolved against the same language’s symbols.
- Hooks you install after adding
viz_node_limitexport it before each rebuild. Re-rungraphify hook installafter changing it. - Nothing else reads
.graphifyrc. Model, output, and logging settings live in environment variables.
Verify and troubleshoot
Should I commit .graphifyrc?
Should I commit .graphifyrc?
Yes. It describes the repository, not your machine, so everyone who builds the graph should get the same result.
Why isn't .h mapped to C++ automatically?
Why isn't .h mapped to C++ automatically?
.h is C in some projects and C++ in others, and .inc can be PHP, Pascal, SQL, or assembly. There’s no correct global default, so the repository declares it.Can I exclude files here?
Can I exclude files here?
No. Use
.graphifyignore.What’s next
Ignoring files and limits
Control what Graphify scans.
Environment variables
Every setting you can change per run.
Try it in Graphify
We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.