Skip to content

should support local vagrant plugins #468

@hoatle

Description

@hoatle

local plugins should be within the plugins directory for prod usage. With dev mode, a plugin can be placed within the workspace directory, follow the convention of teracy-dev extensions for location lookup and path.

When a plugin is updated, make sure to re-install the plugin (gem) so that vagrant gets the latest code of the plugin.

I guess we could introduce: is_local and location option for plugin config so that we know it's a local plugin to handle properly.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions