This website uses Cookies

Default deployment
and go-live offering

Which services are included and which are out of the default scope of work (this page was updated on 19 September 2022).

Intro

Intro

This document is created to present what's included in our standard deployment and go-live procedures. It aims to clearly define which services are included and which are out of the default scope of work.

We have several goals for the deployment and go-live procedure:

  • Ensure that end-users can access the system on a regular basis.
  • Ensure that the client has complete control of the source code and all the infrastructure we produced and configured.
  • Ensure stable system functioning in the live environment.

To make this happen, we outline all required services and deliverables expected to help achieve stated goals. Those deliverables are default ones and require close to zero input from the client.

We are happy to adjust those to the client's unique needs and guide them through technical difficulties. As those needs are mostly individual, we can estimate them precisely after several technical discovery sessions that need to happen in the first two weeks of our cooperation.

Services and Deliverables

System hosting setup

Our default hosting provider is DigitalOcean (DO). We prefer this provider because of price predictability, scalability, and swift support. We provide the following services and deliver the subsequent outcomes:

  • We set up a DigitalOcean standalone account, paid for one month.
  • We set up a DO Droplet with at least three containers running: one for the front-end, one for the back-end, and one for the database.
  • We set up a DO Managed Kubernetes service with the preferred hosting region (US East by default).
  • We customize a DO Space bucket to host assets like images, files, etc.
  • We configure a DO Load balancer to manage incoming traffic properly.
  • We set up a DO Container registry with pre-built images with working code.

The client gets:

  • Credentials for the DigitalOcean standalone account with the above-stated configurations.

The sole client is responsible for operating, managing, and controlling the DigitalOcean account after project handover.

Domain name setup

Our default domain name provider is Name.com. We provide the following services and deliver the subsequent outcomes:

  • We set up a Name.com standalone account and buy the preferred domain name (or set of names) on behalf of a client (the client gets full IP and management rights to the domain).
  • We set up all records to point correct mail servers and hosting servers.

The client gets:

  • Credentials for the Name.com standalone account with the above-stated configurations.
  • IP rights to the domain name.

To achieve the proper IP rights set up, we require the next information to be provided at least one month before the launch of the system.

Domain name owner information that is required includes: First Name, Last Name, Organization (if any), Phone Number, Email, Full Address

If not provided in time, BN Digital would be the owner of the domain name, and we would be glad to transfer the domain names set to the client as a service on hourly basis.

The sole client is responsible for operating, managing, and controlling the Name.com account after project handover.

Source code hosting setup

Our default code repository provider is Github.com. The repository contains all created source code and all the software's visual assets. We provide the following services and deliver the subsequent outcomes:

  • We set up a Github standalone account.
  • We set up a private repository and commit all source code with assets.
  • We set up Continuous Integration and Continuous Delivery Github Actions.
  • We set all secrets (passwords, tokens, etc.) in Github secrets area.

The client gets:

  • Credentials for the Github standalone account with the above-stated configurations.

The sole client is responsible for operating, managing, and controlling the Github account after project handover.

what's not included

  • bn's system hosting services

    • Alternate hosting providers setup (Amazon, Azure)

    • Alternate services setup (Cloudflare, Harbor)

    • DigitalOcean-related consultations

    • Any form of documentation, guides, instructions

  • bn's domain hosting services

    • Alternate domain name providers setup

    • Configuring already bought domain names

    • Name.com-related consultations

    • Any form of documentation, guides, instructions

  • bn's code storage services

    • Alternate repositories setup (Bitbucket, GitLab)

    • Github-related consultations

    • Any form of documentation, guides, instructions

process

Handover process

  • We create a temporary default email (e.g. %projectname%-bn@gmail.com)
  • We create DO standalone account with the default email and attach a temporary credit card.
  • We buy a domain name on name.com using the default email (check info), and we delegate it to DO with all relevant configurations for CNAME, MX records, etc.
  • We set stand-alone Github account registered on default email with the source code and actions set up for CI/CD.
  • We share credentials with the client. Credentials should not be changed until project handover.

Instructions to get control over the project

In a process of a handover, we expect a client to do the next steps to ensure the security:

  • change password for the default email.
  • change password for the DigitalOcean account.
  • change password for the Github account.

After following those steps, the client is encouraged to transfer, change ownership, and configure the setup per their needs.

Let’s work together.
We’d love to hear from you