Please welcome a new gem in town: foreman_devel

First version is available here: https://github.com/ShimShtein/foreman_devel

The end goal of this plugin would be a one stop shop for foreman core and
plugins developers that will supply a set of tools that will aide the
development process.
I have started it by adding generator that would automatically add a
migration to a plugin, with naming convention that will enable easier
uninstallation of plugins. The discussion of this feature is in the rfc
<https://github.com/theforeman/rfcs/pull/15>.

In my vision, it would be a repository for generators, rake tasks e.t.c to
aid plugin developers to write foreman plugins.

Things that I think should be in the plugin:
generator for the whole template - create a plugin in one step
generator for plugin declaration
generator for assets handling
generator for gettext
generator for seeds

Feel free to criticize it, suggest different names, suggest different
solutions, add things to my todo list. Basically any input will be welcome.

Thanks!
Shim

> Feel free to criticize it, suggest different names, suggest different
> solutions, add things to my todo list. Basically any input will be
> welcome.

The name implies it's a Foreman plugin. Other than that, thanks!

··· -- Later, Lukas "lzap" Zapletal

> First version is available here: GitHub - ShimShtein/foreman_devel
>
> The end goal of this plugin would be a one stop shop for foreman core and
> plugins developers that will supply a set of tools that will aide the
> development process.
> I have started it by adding generator that would automatically add a
> migration to a plugin, with naming convention that will enable easier
> uninstallation of plugins. The discussion of this feature is in the rfc
> <https://github.com/theforeman/rfcs/pull/15&gt;.
>
> In my vision, it would be a repository for generators, rake tasks e.t.c to
> aid plugin developers to write foreman plugins.
>
> Things that I think should be in the plugin:
> generator for the whole template - create a plugin in one step
> generator for plugin declaration
> generator for assets handling
> generator for gettext
> generator for seeds
>
> Feel free to criticize it, suggest different names, suggest different
> solutions, add things to my todo list. Basically any input will be welcome.
>

+1, thanks Shimon, I think this is something I would use if we can get
it to mature I hope it can become something like Forklift.

If this is meant for core too as you say - I think adding gems like
'better_errors', 'brakeman' or 'pry-byebug' to the Gemfile.local would be
useful.

Other things I'm thinking is changing the test db to run in memory as
Lukas showed in a thread here a while ago, and making sure your plugin
PRs run on Jenkins (that could be a bit tricky)

··· On 10/09, sshtein@redhat.com wrote:

Thanks!
Shim


You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Daniel Lobato Garcia

@dLobatog

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: elobato (Daniel Lobato Garcia) | Keybase