On Wed, Jun 19, 2019 at 05:22:56PM +0200, Martin Kletzander wrote:
This is a response to all the discussions (mainly) other people had
about all
the JS code we're currently using, bundling, etc.
I would love some feedback on whether we can work on any of the solutions for
getting rid of that external proxy. We would have to:
- either have our own proxy,
Ideally we'd not use any proxy imho
- send a 'Access-Control-Allow-Origin' header from the
libvirt.org server to
allow fetching the atom.xml or
Can you elaborate on this ? This is something we'd need to set on the
libvirt.org httpd config, to allow it to access atom.xml from the
planet.virt-toos.org server ?
I can change
libvirtd.org httpd as needed in general.
- be providing JSONP access to the RSS feed on virt-planet.
Again any more details on what this would imply ? The planet web
server is just running centos7 httpd container in openshift:
https://libvirt.org/git/?p=virttools-planet.git;a=blob;f=openshift/templa...
Regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|