[SAC] [OSGeo] #2684: new VM for demo.pygeoapi.io
OSGeo
trac_osgeo at osgeo.org
Thu Dec 23 11:59:20 PST 2021
#2684: new VM for demo.pygeoapi.io
---------------------------+----------------------------------------
Reporter: pvgenuchten | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2021-II
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+----------------------------------------
Comment (by robe):
@just yah sorry for the confusion earlier, I had a typo in domain earlier
with CNAME, so the plan is:
1. Test with demo.pygeoapi.osgeo.org -- which is already setup to proxy
thru to the demo-pygeoapi vm.
2. If all looks good we remove the demo.pygeoapi.osgeo.org and you setup
in your dns CNAME demo.pygeoapi.io -> web.osgeo3.osgeo.org
If you need to manage letsencrypt entirely via ansible, then let me know.
I think the easiest in that case would be to allocate a dedicated ip for
the osgeo3-demo-pygeoapi so I would need to get extra SAC approval for
that. I think we have a couple spare ips but something I'd like to avoid.
In that case I'd just point 80/443 ports directly to the vm dedicated ip.
3. Also let me know if it's easier for you to go thru a non-standard port
than having to do the proxy jump. That is easy enough to do. As
mentioned I'm not too concerned as long as you block off password access
(and only allow key access) in your vm. That means you need to put in your
ssh public key since the VMs are not set up to pull ldap stored public
keys.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2684#comment:11>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
More information about the Sac
mailing list