These are the steps you'll need to go through to get Cobrowse running:
1. Database setup
The first thing you'll need is access to a MongoDB database. Cobrowse will need a connection string containing the address and authentication information for your cluster.
A MongoDB cluster is required for running Cobrowse. We do not provide this as part of the terraform environment.
You will need to create a cluster and provide the connection URL as a part of the Cobrowse configuration. You can either run your own MongoDB cluster and manage the deployment and backups yourself. Alternatively, we recommend using a hosted service such as MongoDB Atlas. They have a range of certifications required by many enterprises with compliance requirements.
2. Create initial Azure resources
There are some resources that are not created by our Terraform. You will need to manually create:
We have provided a small command line utility to help you get started. This utility will gather the required config for your deployment. Run the following command from your terminal:
> npx cobrowse-enterprise create azure ./example
You can replace "./example" with the directory where you wish to save the configuration data. The directory will be created if it does not exist yet.
4. Deploy the Terraform
Warning: This will store all Terraform state locally. We strongly recommend adding a backend configuration for almost all deployment scenarios.
Once you have successfully generated a configuration directory via our command line utility you are then ready to deploy the terraform to Azure. Navigate to the configuration directory you created and run the following commands:
> terraform init
This will instruct terraform to prepare the resources it needs to deploy. Run the following command to start the deployment of resources to Azure:
> terraform apply
This will list the modifications that terraform will make to your Azure account. If that looks good, type 'yes' to continue the deployment.
5. Configure your DNS provider
Configure your DNS provider with an A record to point to the IP address provisioned by the terraform. We recommend doing this as soon as the IP is provisioned in the Azure portal to prevent DNS propagation delays, although this is not essential.
Once the terraform is deployed and the DNS configured you may have to wait for the certificate to be provisioned. Depending on DNS propagation delays this can take some time (usually between 5 minutes and an hour).
6. Check your deployment
Your Cobrowse instance should now be deployed. Head to /registeron your domain to create an account.