v1.2.6: заглушка №1 — дата-аналитика вместо хостинга; гейт по переводам строк выше проверки коммита

This commit is contained in:
2026-10-12 20:37:50 +03:00
parent 628130992d
commit ca5a57db55
4 changed files with 20 additions and 24 deletions
+16 -21
View File
@@ -468,7 +468,7 @@ EOF
KL_SITE_FILE=/var/www/kit/index.html
KL_SITE_TITLES=(
"Nordhost — VPS and cloud hosting"
"Radian Analytics — data platforms and BI"
"Circuit Nine — DevOps consulting"
"Cortex Monitor — server monitoring"
"Bluefin Software — custom development"
@@ -480,7 +480,7 @@ KL_SITE_TITLES=(
"Halyard Docs — project documentation"
)
KL_SITE_TOPICS=(
"VPS-хостинг: тарифы, регионы, платформа"
"дата-аналитика: хранилище, отчёты, дашборды"
"DevOps-консалтинг: CI/CD, Kubernetes, наблюдаемость"
"мониторинг серверов: метрики, алерты, статус-страница"
"разработка ПО на заказ: портфолио, стек, процесс"
@@ -545,30 +545,25 @@ HTML
kl_site_html() { # номер (с нуля) → страница на stdout
case $1 in
0) # хостинг
kl_site_open "Nordhost — VPS and cloud hosting" "Virtual servers on NVMe storage in three European regions. Hourly billing, snapshots, private networks and a full API." "Nordhost" '<a href="#plans">Plans</a><a href="#network">Network</a><a href="#docs">Docs</a>'
0) # дата-аналитика
kl_site_open "Radian Analytics — data platforms and BI" "We collect data from accounting, warehouses and websites into one place and build the few reports the business actually reads." "Radian Analytics" '<a href="#services">Services</a><a href="#approach">Approach</a><a href="#contact">Contact</a>'
cat <<'HTML'
<main>
<section class="hero"><div class="wrap">
<h1>Virtual servers that stay out of the way</h1>
<p>KVM instances in Frankfurt, Amsterdam and Zurich. Hourly billing, snapshots, private networking, and an API for everything the control panel can do.</p>
<a class="btn" href="#plans">See plans</a>
<h1>Reports that arrive before the meeting</h1>
<p>We pull data out of your accounting system, warehouse and website, load it into one warehouse, and build the handful of dashboards people actually open.</p>
<a class="btn" href="#services">What we build</a>
</div></section>
<section id="plans" class="wrap cards">
<div class="card"><h3>Starter — €4/mo</h3><p>1 vCPU, 2 GB RAM, 40 GB NVMe, 20 TB traffic.</p></div>
<div class="card"><h3>Standard — €9/mo</h3><p>2 vCPU, 4 GB RAM, 80 GB NVMe, 40 TB traffic.</p></div>
<div class="card"><h3>Compute — €18/mo</h3><p>4 vCPU, 8 GB RAM, 160 GB NVMe, 100 TB traffic.</p></div>
<section id="services" class="wrap cards">
<div class="card"><h3>Data pipelines</h3><p>Scheduled loads from databases, APIs and spreadsheets, with checks that catch a broken source early.</p></div>
<div class="card"><h3>Warehouse</h3><p>PostgreSQL or ClickHouse, modelled so that a new question does not need a new table every time.</p></div>
<div class="card"><h3>Dashboards</h3><p>The five numbers that matter on one page, with the detail one click behind each of them.</p></div>
</section>
<section id="network" class="wrap prose">
<h2>Network</h2>
<p>Every region is connected with redundant 10 GbE uplinks. Traffic inside a region is free, between regions it is billed at cost. IPv6 is included, IPv4 on request.</p>
<h2>Platform</h2>
<ul>
<li>Snapshots, weekly backups and one-click rebuilds</li>
<li>Private networks, floating IPs and firewalls</li>
<li>cloud-init, Terraform provider and REST API</li>
<li>Two-factor sign-in and audit log</li>
</ul>
<section id="approach" class="wrap prose">
<h2>How it usually goes</h2>
<p>Two weeks to collect the sources and agree on definitions — most arguments turn out to be about definitions, not about software. Then the pipeline runs nightly and the first reports go out a week later.</p>
<h2>One warning</h2>
<p>A dashboard nobody opens is expensive decoration. One report that somebody uses beats ten that nobody does.</p>
</section>
</main>
HTML
+1
View File
@@ -577,3 +577,4 @@ def main():
if __name__ == "__main__":
main()