VPS Hosting for CMS SilverStripe on SSD
SilverStripe (called Silverstripe CMS in its documentation) is a PHP system with a friendly editing panel and a flexible data model that developers like. VPS hosting for SilverStripe at HIP-HOSTING means a virtual machine that is yours alone: PHP, web server and database are picked by you. No SilverStripe image is listed at checkout; Composer assembles the site and the last installation steps happen in a browser. Pages, images and editors decide how big the server should be, and upgrading later needs no migration.
Get VPS from $3/mo- Standardfrom $3/mo
- Memoryfrom $10/mo
- Hi-CPUfrom $5/mo
VPS / VDS PLANS
Our VPS hosting plans for CMS SilverStripe
Choose a location and plan line. Prices shown per month.
FAQ
Frequently asked questions
IN DETAIL
Service description
Installing with Composer
Run composer create-project silverstripe/installer to create the site; a branch such as ^6.0 can be appended. With the web server and database running, load the site in a browser to let the installer finish. On a live server dependencies are installed with the flags --no-dev -o, and modules and themes that Composer manages are not committed to the project repository.
Document root
The web server must point at the public/ subfolder rather than the project root. Then source, vendor libraries and .env sit outside the address space of the site and cannot be reached by a link.
The .env file
Next to composer.json sits the .env file: it holds database access (SS_DATABASE_SERVER, SS_DATABASE_NAME, SS_DATABASE_USERNAME, SS_DATABASE_PASSWORD) and the environment type SS_ENVIRONMENT_TYPE with the values dev, test or live. The variables SS_DEFAULT_ADMIN_USERNAME and SS_DEFAULT_ADMIN_PASSWORD define a default administrator account whose password is not stored in the database.
Uploads and protected files
The web server has to write to public/assets/ and to the temporary folder TEMP_PATH. Uploaded files are protected by default and land in public/assets/.protected/. Requests to that folder must be denied, and moving it beyond the site root with SS_PROTECTED_ASSETS_PATH in .env is more reliable.
Database build and caches
After a code update and with new data models, run dev/build: it rebuilds the tables and the manifest. The flush parameter clears the caches but works in dev mode or for an administrator. By default caches are files in a temporary folder, nobody prunes them and they are not shared across several servers. Watch free space, and for a busy site add a memory cache.
Speed
Responsiveness comes from caching, lean images and a snappy database. Heavy projects gain from an NVMe VPS server with SilverStripe whenever caches and indexes are regenerated often; concurrency, however, is bounded by RAM.
Protection and mail
Use a long admin password, leave the database port unreachable from outside and log in over SSH with a key. Route outgoing mail through an external SMTP provider; on new servers the mail ports are not guaranteed to be open.
Backups and moving
Keep a set of three: the database, the public/assets folder (with .protected inside it, or its new location if you moved it with SS_PROTECTED_ASSETS_PATH), and .env. To move, deploy the copy to the new host, run dev/build, flush caches and repoint the domain at the very end.
PHP extensions
The documentation requires the extensions ctype, dom, fileinfo, hash, intl, mbstring, session, simplexml, tokenizer and xml, and gd or imagick for pictures. A database connector such as mysql is needed separately. Install everything before the first run so the wizard does not stop at the environment check.
Worker processes
One PHP process serves one request, so run several: that way simultaneous visitors and editors do not queue. Size the pool by memory and leave headroom for the DB engine and caching.
Who it suits
- agencies building client sites with SilverStripe;
- organisations whose editors prefer a comfortable panel;
- teams that deploy through Composer and keep staging apart from production;
- site owners who find shared hosting cramped.
Choosing a plan
Settle the branch, PHP and database first, size second. Someone about to buy SilverStripe VPS hosting may open with 2 vCPU and 2 GB. Teams that rent SilverStripe VDS hosting should settle upfront who owns patching and copies. A VPS/VDS for SilverStripe grows alongside the site, and cheap SilverStripe VPS hosting is one where the cache never stalls the editors.