The Block Editor Revolution: From Productivity Tools to Simple Website Publishing

Tech Stack

Infrastructure

Overview

The infrastructure for the MVP is designed to be reliable, privacy-compliant, and flexible enough to accommodate your core requirements while keeping maintenance minimal. By leveraging managed tools like Coolify and the robust resources of Hetzner Cloud, this infrastructure ensures a strong foundation for hosting your application, storage, and SSL management.

⁠

Components

1. Hosting Provider: Hetzner Cloud

The application will run on a dedicated Hetzner Cloud instance configured to support your needs during development and the beta phase.

Specifications:

CPUs: 4 cores.

RAM: 8 GB.

Storage: 120 GB SSD.

Operating System: Ubuntu (required for Coolify installation).

Why Hetzner?

Competitive pricing.

Fully compliant with GDPR and European data regulations.

Proven performance for small to medium-scale applications.

⁠

2. Deployment Management: Coolify

Coolify serves as the deployment manager, streamlining the process of deploying and managing your application components without direct interaction with the server.

Key Features:

Automates the deployment of your Next.js app, Supabase backend, and other services.

Manages the Traefik reverse proxy for domain routing and SSL certificates.

Offers a user-friendly interface to manage services, logs, and backups.

Provides built-in support for Docker, ensuring consistent and isolated environments.

⁠

3. Object Storage: Tebi.io

Static assets and user-uploaded content will be stored in Tebi.io, an S3-compatible storage service.

Why Tebi.io?

Fully compliant with GDPR and European hosting requirements.

Provides an efficient, scalable, and cost-effective alternative while Hetzner's S3 storage remains in beta.

Seamless integration with existing S3-compatible libraries.

⁠

4. DNS Management: Hetzner DNS

DNS services for the application will be handled by Hetzner.

Responsibilities:

Configure wildcard subdomains for development and production phases.

Handle DNS entries for user-connected custom domains using CNAME records.

DNS Configuration:

During development:

Primary domain: blokky.bombig.app.

Wildcard subdomains: *.blokky.bombig.app.

During beta launch:

Landing page: useblokky.com.

Application: app.useblokky.com.

User sites: *.blokky.site.

⁠

5. SSL Certificates

All SSL certificates will be managed using Traefik, with automation provided by Let's Encrypt.

Wildcard SSL: Covers wildcard domains like *.blokky.site.

Custom Domains: Automatically issues and renews certificates for user-connected domains.

DNS Challenges: Configured for Let's Encrypt to verify ownership of wildcard and custom domains.

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.