6888901468
* First cut * Temporarily disable composer.json for netlify build * POC * New recursive directory query, various refinements * Fix flexbox * new styled components plugin * Apply frontmatter delimiters * Mobile styles, animation * Search * Redesign, clean up * Nuke the cache, try again * fix file casing * Remove production env file * ID headers * Move app to new repo * Add frontmatter universally * Hide children changelogs * Add how to title * New callout tags * Revert inline code block change * Replace note callouts * Fix icons * Repalce images * Fix icon * Fix image links * Use proper SQL icon
2.2 KiB
| title | introduction | icon |
|---|---|---|
| Getting Started | SilverStripe is a web application. This means that you will need to have a webserver and database. We will take you through the setup of the server environment as well the application itself. | rocket |
Server Requirements
SilverStripe requires PHP 7.1 or newer. It runs on many webservers and databases, but is most commonly served using Apache and MySQL/MariaDB.
If you are setting up your own environment, you'll need to consider a few configuration settings such as URL rewriting and protecting access to certain files. Refer to our server requirements for details.
Quickstart Installation
If you're running Apache with MySQL/MariaDB already, and know your way around webservers, follow these steps to get started. SilverStripe is installed via Composer, a package management tool for PHP that lets you install and upgrade the framework and other modules. Assuming you've got this tool, run the following command to install SilverStripe:
composer create-project silverstripe/installer my-project
Within the newly created my-project folder, point your webserver at the public/ folder.
Rename .env.example to .env in your project, and configure your database connection there.
See environment variables for available configuration options,
e.g. to configure a default CMS login via SS_DEFAULT_ADMIN_USERNAME.
Now you should be able to build your database by running this command:
vendor/bin/sake dev/build
Your website should be available on your domain now (e.g. http://localhost).
The CMS login can be accessed at /admin.
Guided Installation
If you are unsure on how this all works, please jump on our lessons. Webserver setup is covered in Lesson 4: Setting up a local dev environment
Keep learning
[CHILDREN]
Troubleshooting
If you run into trouble, see common-problems or check our community help options.