<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hosting V3 on Webscale Product Documentation</title><link>https://docs.webscale.com/hosting-platforms/hosting-v3/</link><description>Recent content in Hosting V3 on Webscale Product Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.webscale.com/hosting-platforms/hosting-v3/index.xml" rel="self" type="application/rss+xml"/><item><title>Configuration</title><link>https://docs.webscale.com/hosting-platforms/hosting-v3/configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/hosting-platforms/hosting-v3/configuration/</guid><description>&lt;p&gt;Initial configuration and setup of a V3 servers of most types are handled
primarily through a program called &lt;code&gt;invoker&lt;/code&gt;. Permanent servers, such as
NFS servers, bastions, or other accessory servers, are maintained by request
to Webscale support following their initial creation. Cluster-based servers,
such as web servers, cron servers, consumer servers, or other servers based
on the &lt;code&gt;web-server&lt;/code&gt; image family are expected to only be configured and
maintained through their initial configuration. This is due to their transient
nature.&lt;/p&gt;</description></item></channel></rss>