<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello, FreeIPA list.<div><br></div><div>We're looking to start using FreeIPA to replace our standard 389 LDAP server on our public web server.</div><div><br></div><div>That public web server also houses a public wiki, which currently authenticates against 389. We're running FreeIPA on site in our hackerspace, but are working toward a goal of a federated login system between all of our public and internal systems.</div><div><br></div><div>My plan, as it stands, is to set up a VPN link between our public web server and our space, and set up a master-master replication between a FreeIPA server running onsite, and another on our public web server.</div><div><br></div><div>The limitation I'm currently considering is that our public web server is limited on resources - it's a VM with 1GB of RAM, on which we're already running Apache, Mediawiki, and an IRC bot. The VM is currently donated by a member. We're a little crunched on resources as it is, and I fear that spinning up a full FreeIPA replica on that system may push us over the edge of resource constraints.</div><div><br></div><div>Is it possible to tune FreeIPA to run with fewer resources, or replicate only the portions of it that we really need running remotely (just the LDAP server)? </div><div><br></div><div>Thanks!</div><div><br><div> Christopher Swingler<br><i>CTO</i><br>South Side Hackerspace Chicago<br>2233 South Throop St | Unit 214 | Chicago, IL 60608 </div> <br></div></body></html>