search

teracyhq / dev

The only truly universal productive development platform with Docker on macOS, Linux and Windows! http://blog.teracy.com/2016/12/20/teracy-dev-the-only-truly-universal-productive-development-platform-with-docker-on-macos-linux-and-windows/ http://slides.teracy.net/hoatle/productive-dev-workflow-with-teracy-dev/latest/
http://dev.teracy.org/docs
BSD 3-Clause "New" or "Revised" License
86 stars 31 forks source link

should support local vagrant plugins #468

Open hoatle opened 6 years ago

hoatle commented 6 years ago

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.

hoatle commented 6 years ago

I guess we don't need this yet for v0.6, so maybe we could make this into v0.7 or when we really need this feature

hoatle commented 6 years ago

related: #493

As I could see, plugin_manager also supports local plugin so we just need to add config support

hoatle commented 5 years ago

vagrant introduced local and global mode plugins, I need to specify more to avoid confusions.