Setting up your custom Buzzy app

Using your own domain, publishing to the app stores and more

Setting up your server

Configuration options for your own Buzzy server:

App name

This just needs to be something unique in the realm of Buzzy deployment names. We recommend something like the name of your organization or project.

Region

You need to choose the region you'd like to deploy in, at the moment, these options are available:

• NA1 - North America (in the USA)

• EU1 - Europe - (in Germany)

• AP1 - Asia Pacific - (in Australia)

Based on the chose region, this is where you app's data will reside and be served from.

Domain name

You have two options to configure the domain name setup:

1. Use Buzzy's domain with your own custom sub-domain

Use your custom sub-domain with a Buzzy domain - as an example: somethingcustom.buzzy.buzz The sub-domain here is somethingcustom. Constraints it needs to be unique and not anything offensive, aligned with Buzzy's terms and conditions.

2. Your own domain

Setup your own sub-domain to point to the Buzzy deployment, for example "app.<yourdomain>.com " where "app" is the sub-domain.

You will need to go to your DNS provider, like Godaddy, and setup a CNAME record to the details below. As an example, of how to setup on Godaddy please see here.

If you need help, please reach out to your DNS provider to get help on how to do this.

The CNAME record will need to be setup to point to one of the following servers depending on the region your Buzzy server will be in:

1. NA1 point to communication-k8s.buzzycompany.com

2. EU1 point to eu1-cluster.buzzy.buzz

3. AP1 point to communication-sydney-cluster.buzzycompany.com

Once setup you should be able to validate it's been done correctly a nslookup web site like CNAME lookup. You can also do a nslookup or dig on your computer via the Terminal/Command prompt.

If you want to have your own domain but need more time to set it up, we can set up your server with the Buzzy domain to start with and switch to your custom domain once it is ready.

Mail Settings

To send mail from you own servers we'll need return users eg [e-mail] SMTP url in the format of smtps://USERNAME:PASSWORD@HOST:PORT you will need to get this from your mail provider

Google Maps API Key

To enable Google Maps functionality in your Buzzy app, you'll need to set up a Google Maps API key and provide it to us. Follow these steps:

1. Sign in to Google Cloud Console

• Go to https://console.cloud.google.com/

• Sign in with your Google account (or create one if you don't have one).

2. Create a new project

• In the top-left, click the project dropdown, then New Project.

• Give it a name like "My Maps Demo", choose your organisation (if prompted), and click Create.

• Wait a few seconds for it to finish.

3. Enable billing

• Google Maps APIs require a billing account, though you get a free monthly credit.

• In the left menu, go to Billing.

• Follow prompts to add a credit card.

• Once set up, billing will be linked to your project.

4. Enable the required Maps APIs

• In the left menu, go to APIs & Services » Library.

• Search for and Enable each of these APIs:

  • Maps JavaScript API

  • Geocoding API

  • Directions API

  • Places API

5. Create your API key

• Still under APIs & Services, click Credentials.

• Click + CREATE CREDENTIALS and choose API key.

• Google generates a long string—that's your key.

6. Secure your key (strongly recommended)

• Unrestricted keys can be abused if someone finds them. Let's lock it down:

• On the Credentials page, click your new key's name.

• Under Application restrictions, choose HTTP referrers (web sites).

• Add your site's URL(s), e.g.

  • https://your-domain.com/*

  • http://localhost:3000/*

• Under API restrictions, select Restrict key, then select only the four APIs you enabled:

  • Maps JavaScript API

  • Geocoding API

  • Directions API

  • Places API

You'll need to provide this API key to us when setting up your Buzzy deployment. This allows your app to use Google Maps features while maintaining security and usage control.