Newbie Questions

[craigbartholomew]

Hi,

I'm trying to put together a proof of concept bringing FormKiQ into an existing web application. On the surface, FormKiQ seems like exactly what we're looking for, but I'm struggling to make sense of a few things. I can't get access to the Slack Community without an invite, so I'll post my questions below in hope that someone can shed some light. For the avoidance of doubt, you can assume I'm operating exclusively in the local (docker/minio) environment, and I haven't yet deployed to AWS in this early stage.

• Should I expect to see a 'default' user group in Minio on a fresh installation?
• Does the local installation support multi-tenancy? I've created a new group and added a user, but the user can't authenticate with the console or API
• Can I get invited to the Slack Community?
• The local installation doesn't get much coverage in the docs, does this mean people aren't building/testing locally?

Many thanks

[reganwolfrom]

@craigbartholomew we'll get you some more answers ASAP, but here's a new invite link for the Slack community: https://join.slack.com/t/formkiqcommunity/shared_invite/zt-2ki1i21w1-9ZYagvhY7ex1pH5Cyg2O3g

Hopefully this one works; I think the other has expired so we need to refresh it.

[reganwolfrom]

@craigbartholomew Here are some responses from the team:

• The docker/minio environment comes with some limitation in comparision to the full AWS installation. The docker/minio only supports a single "admin" login as defined by the ADMIN_USERNAME / ADMIN_PASSWORD in the docker-compose file. Minio is only used to store documents and is not used for access control.

• The API supports multi-tenancy via the "siteId" parameter. The local environment does not, and only supports the admin user that user will have access to all sites. For multi-tenancy testing, you would unfortunately need to deploy into AWS.

• The local installation is a recent addition to allow the people to get up and running quickly and get an idea on how FormKiQ works. For testing out multi-tenancy or other features that aren't included in the local install, ,most users deploy one or more copies to their AWS account (because of the next to zero cost for a basic install) and then use the full features of the API rather than building/testing locally testing.

Hopefully this all makes sense. Please let us know if you have more questions or comments.

Thanks!