Bulk site creation

Deployment and hosting for bulk site creation

Deployment and hosting put the generated sites online and keep them manageable as part of bulk site creation. Best Boost Partners writes scripts that register and configure domains, set DNS records, issue SSL certificates and distribute sites across hosting providers and IP addresses. The sites are kept under version control, and one command updates all of them. You receive the scripts, the register of domains and hosting, and all access details.

What exactly do we do in deployment and hosting setup?

  1. Domain registration and setup

    Scripts register domains or take the ones you have already bought and bring them to one state: name servers, contact data, renewal. We separate registrar accounts where the purpose of the network requires it.

  2. DNS

    The DNS records of each site are created from the data file. Before publication the script checks that the records have updated.

  3. SSL certificates

    Certificates are issued and renewed automatically for every domain. The script reports the domains where the issue failed, so that a site is not left with a browser warning.

  4. Distribution across hosting and IPs

    We distribute the sites across several hosting providers and IP addresses according to a plan. The plan states where each site is placed, and sites linked to each other do not end up on one server.

  5. Version control

    The generator, the templates and the data of every site are stored in a repository. Every change has an author and a date and can be rolled back.

  6. One-command update

    One command rebuilds the sites and publishes them to all servers. The same command works for a single site or for a chosen group.

What do you get from deployment and hosting?

  • Deployment scripts with a description of every command and its parameters.
  • A register of domains and hosting: registrar, renewal date, provider, IP address, name servers and SSL status for each site.
  • Access details for the registrar, DNS and hosting accounts, transferred in an agreed secure way.
  • A repository with the full history of the sites and the generator.
  • Instructions on how to add a site, move a site to another provider and update all sites.

When are deployment and hosting for bulk sites needed?

  • The sites are configured by hand, and every new domain requires the same steps all over again.
  • All sites of a network are placed on one hosting account or on one IP address.
  • A change in a template has to reach every site, and nobody knows for certain which sites have been updated.
  • Domains expire and certificates are not renewed because the dates are recorded in different places.

Frequently asked questions

Do you work on our hosting accounts or open new ones?

Both options are possible. If you already have accounts, we check how the sites would be distributed across them and say what is missing. New accounts are opened in your name or handed over with full access, and every account is entered in the register.

Why distribute sites across different hosting providers and IP addresses?

Sites of one network on one server share an IP address and often name servers, and for a link network this is a visible footprint. Distribution also limits the damage from an outage or a blocked account to part of the sites. Regional versions of one service usually do not need such separation, and we say so.

What happens if a hosting provider closes an account or stops working?

The sites from that account are rebuilt from the repository and published with another provider by the same command. The register shows which domains are affected, and a script changes the DNS records. The sites do not have to be restored from a server backup, because the source of every site is kept in the repository.

Tell us about the project

Fill in what you already know. Blank fields are fine: we will clarify the rest in conversation.

Prefer to talk first? Write to us on WhatsApp or by email.

Task

What do you need? Choose one or several.
Topic of the site

Project

An example helps us understand the style and scale you have in mind.
CMS or platform

Contact

How should we reply?