Community Profiles

Community profiles are GitHub repositories made by users. They can save time, but you must inspect them first.

What is a community profile?

A community profile is a repository with a profile.yaml file at the root. DPM reads this file to find tools and optional dotfiles.

DPM uses profile.yaml and dotfiles listed inside it. For example, in AskDatDude/MD, DPM uses profile.yaml and dotfiles/.tmux.conf. Other files like LICENSE or extra notes are not used as install instructions.

Finding community profiles

Search the community profile index from the CLI:

The community index is local data shipped with DPM releases. Search reads this local index, then dpm inspect fetches real file content from GitHub.

Applying a community profile

Start with inspect. In the current CLI build, remote community apply is limited, so treat inspect as the required first step:

Sharing your own profile

Create a public GitHub repository. Put profile.yaml in the root. Put dotfiles in a dotfiles/ folder. Then reference those filenames in the dotfiles list.

When ready, submit your repository URL to the DPM community index in the DPM repository. After merge, users can find it with dpm search --community.

Community index and sync

The community index is a snapshot of known repositories. It ships with DPM and is refreshed in later releases. Search does not query GitHub live.

Actual profile content is fetched when you run dpm inspect.