GitHub user thomasf provided a workaround which I modified only slightly:
;; (source: https://github.com/bbatsov/projectile/issues/364#issuecomment-61296248)
(defun projectile-root-child-of (dir &optional list)
(projectile-locate-dominating-file
dir
(lambda (dir)
(--first
(if (and
(s-equals? (file-remote-p it) (file-remote-p dir))
(string-match-p (expand-file-name it) (expand-file-name dir)))
dir)
(or list project-root-regexps (list))))))
(defvar project-root-regexps ()
"List of regexps to match against when projectile is searching
for project root directories.")
(add-to-list 'project-root-regexps "/path/to/some/project/$")
(add-to-list 'project-root-regexps "/path/to/another/project/$")
(add-to-list 'project-root-regexps "/path/to/one/more/project/$")
(nconc projectile-project-root-files-functions '(projectile-root-child-of))
This lets me add projects to to the list project-root-regexps
, and as far as I can tell they behave just as if they had a .projectile
file at their root.