As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
Is anyone aware of a procedure to validate and test a community (or any) install? I'm basically just stuck with finding Youtube vids and checking whether the install does the same thing, which isn't great.
There is no a simple method to validate an installation. It depends on what you've installed.
I created this presentation some time ago: https://www.slideshare.net/angelborroy/bee-con2016-presentation20160125004installing
Hope that helps.
Thanks, Angel. I didn't know about some of the stuff in the Use Case 'adaptation' list, and I don't have a couple of the endpoints listed (the monitoring and CMIS/atom ones), so that will need some thinking about. It seems like any attempt at validation would be useless without a lot of real data and a well-defined use case.
Slideshare is a paid service; I found the presentation on github here.
On the RAM requirement - my test VMs are running 4GB / 2 vCPUs for a small amount of data and one user (Apache with mod_jk gateway, Google docs, AOS, MariaDB, no email/SMB/LDAP). I think 2GB might be Ok with this configuration (2GB is the price inflection point for a low-end VPS) - I'll try when I get some time.
