Guides
Step-by-step WebShield guides for publishing websites and apps, protection, data storage and automation.
Choose your task: publish a Flask or Laravel app, deploy from a repository, connect a website or protect it against attacks.
A contact form without a backendHow to receive messages from a static site's form by email and in the control panel without a handler of your own.
A site without your own serverHow to host a landing page, business card site or documentation made of ready files with us and publish it on your domain — without a server of your own.
Attacks straight at the server IPIf protection is on and the server is still under load, requests may be bypassing us and hitting its address. How to find where the address leaked and close the server to everyone except WebShield.
Bots sign up and spam through formsHow to ask WebShield for a score of every sign-up or lead from your backend and filter out fake accounts, spam and SMS pumping.
Cloud backups — Windows, Mac, Linux, 1C and databasesSet up daily backups of a computer or server to WebShield S3 storage with restic — with shadow copies for open files, closing 1C before the copy and database dumps.
Home server disappears after a router rebootHow to keep a hostname on your home server's current address when the ISP assigns a dynamic IP, and hide that address behind the proxy.
How to publish a Python appCreate a small Flask app, publish it on your domain with WebShield, then check its logs, update it and roll back.
Publish a Laravel websiteBuild Laravel with Vite, connect Postgres and publish over HTTPS, with working forms, persistent sessions, updates and rollback.
The app updates itself after a push to a private repositoryDeploy a Node.js, Python, Go or Docker app from GitHub Actions, GitLab CI, Gitea or Forgejo — without opening repository access and without a server of your own.
The site updates itself after git pushWhen a Hugo, Astro or other generator site is built and uploaded by hand, the site may end up on the wrong version. How to publish it automatically from GitHub Actions, GitLab CI, Gitea or Forgejo.
WordPress is flooded with password guessingHow to cut off password guessing against wp-login.php and xmlrpc.php and plugin scans before they reach PHP, and close the server to direct access.