-
Notifications
You must be signed in to change notification settings - Fork 65
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
Why do I have this listing in my server root ? #228
Comments
That doesn't sound right. Can you tell us how you deploy the module? I suspect that this module is mostly tested on the same server as Katello and you deploy it standalone. This is something I really want to improve and is on my short term agenda. Any insight on common use cases would be greatly appreciated. |
Pulp module is 4.3.0, over CentOS 7 Here's my profiles::pulp
Here's the roles::test calling pulp
Common's just about installing vim, ntp, starting firewalld... no real impact for pulp / apache And I'm having this hiera, no real impact here
That's it for our usage of pulp, as standalone mirroring server |
I am also experiencing this problem. My setup is simple: class profile::pulp {
include ::profile::apache
include ::profile::apache::ssl
include ::apache::mod::wsgi
# Set up Pulp repo for installation
yumrepo { 'pulp-2-stable':
descr => 'Pulp 2 Production Releases',
baseurl => 'https://repos.fedorapeople.org/repos/pulp/pulp/stable/2/$releasever/$basearch/',
enabled => 1,
skip_if_unavailable => 1,
gpgcheck => 1,
gpgkey => 'https://repos.fedorapeople.org/repos/pulp/pulp/GPG-RPM-KEY-pulp-2',
}
# Install Pulp server with katello/pulp
class { '::pulp':
enable_rpm => true,
enable_puppet => true,
require => Yumrepo['pulp-2-stable'],
}
# Install Pulp admin utility
class { '::pulp::admin':
enable_puppet => true,
enable_nodes => true,
enable_rpm => true,
}
} |
So the reason is https://github.com/puppetlabs/puppetlabs-apache/blob/7301123aa51afe696f129988482889f61aa4f0d0/manifests/vhost.pp#L44. The easiest patch would be to change the pulp-http vhost and add |
It can't really make it any worse 😄 At the moment, I can't use Pulp at all because of this |
Don't you think all the repos rely on index view ? |
That's what I suspect, but I'm still getting to know the module better and need better testing of individual parts. |
I don't think it's as simple as disabling |
Well, you have the index but all the actual hosting happens through aliases. Those are not visible in the index but when you go to |
Browsing to |
Then I'm wondering what
Then you should be able to use Note I'm doing this without access to an actual pulp server (yay traveling without a dev box) so I might be slightly off in some details. |
I created
and the
|
Then I think it should be working. Note that as far as I know pulp has no UI. You can use Katello but that may not be what you're looking for. |
I also have these WSGI scripts listed on my standalone deployment. I think it may be as simple as disabling Indexes because a quick test on my setup seemed to indicate everything works well without it. Also, the HTTPS vhost works fine without this "Options" line. Regarding WSGI scripts, 1 improvement would also be to run them as a distinct, specifically created user (instead of running them as apache). I'll try to write a patch and submit a PR for this. |
When #252 lands there will be some acceptance tests. After those are in I'll feel a lot safer when making changes. Of course I can already use that to test submitted PRs |
Hi
The question is in the title, I dunno why I end up with this calling http://fqdn/ ?
Best regards,
The text was updated successfully, but these errors were encountered: