Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Directions for Plugin Development setup #783

Open
jrich523 opened this issue Jul 16, 2018 · 3 comments
Open

Directions for Plugin Development setup #783

jrich523 opened this issue Jul 16, 2018 · 3 comments

Comments

@jrich523
Copy link

Looking to do some plugin dev and it appears that this setup wasnt really specifically designed for that. Is that something that can be added?

@ekohl
Copy link
Member

ekohl commented Jul 26, 2018

You could have a look at luna-devel. which you can base yourself on.

@jrich523
Copy link
Author

@ekohl just out of curiosity, why?
I've been talking to the folks in the irc channel and have been making some (painful) progress.

At this point im using the centos7-devel, but its rather heavy for just plugin dev. how is the luna different?

@ekohl
Copy link
Member

ekohl commented Jul 26, 2018

At this point im using the centos7-devel, but its rather heavy for just plugin dev. how is the luna different?

I'd say luna is even heavier because there's additional plugins. I don't think we have a good playbook for a vanilla Foreman without Katello and its dependencies. I've never automated this because it's very few steps. See https://theforeman.org/contribute.html#Setupdevelopmentenvironment

It would be interesting to also set up a proxy in development mode and register it but that's one API call after you've started the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants