tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-07-08 20:39:26 +02:00
Code Issues Projects Releases Wiki Activity
e344b66dbe
silverstripe-framework/docs/en/00_Getting_Started/index.md

76 lines
2.5 KiB
Markdown
Raw Normal View History

NEW: Update docs to be compliant with Gatsby site (#9314) * 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
2019-11-18 05:58:33 +01:00
---
Add introduction files to each of the sections
2014-09-21 02:07:58 +02:00
title: Getting Started
introduction: 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.
NEW: Update docs to be compliant with Gatsby site (#9314) * 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
2019-11-18 05:58:33 +01:00
icon: rocket
---
ENHANCEMENT Added sapphire/docs (migrated from https://github.com/chillu/silverstripe-doc-restructuring)
2011-02-07 07:48:44 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
## Server Requirements
ENHANCEMENT Added sapphire/docs (migrated from https://github.com/chillu/silverstripe-doc-restructuring)
2011-02-07 07:48:44 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
SilverStripe requires PHP 7.1 or newer.
It runs on many webservers and databases,
Update docs/en/00_Getting_Started/index.md Co-Authored-By: Garion Herman <garion@silverstripe.com>
2019-09-04 05:33:31 +02:00
but is most commonly served using Apache and MySQL/MariaDB.
ENHANCEMENT Added sapphire/docs (migrated from https://github.com/chillu/silverstripe-doc-restructuring)
2011-02-07 07:48:44 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
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](server_requirements) for details.
Added docs for composer
2012-11-03 06:00:58 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
## Quickstart Installation
Added docs for composer
2012-11-03 06:00:58 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
If you're running Apache with MySQL/MariaDB already,
and know your way around webservers, follow these steps to get started.
DOCS Remove archive download references (#9250) See https://github.com/silverstripe/silverstripe-framework/issues/9232. Also simplifies composer instructions a bit: - Removes composer update --no-dev references, that's a bit of an edge case that people can just discover on getcomposer.org if they need it - Changed example from the unused and oudated silverstripe/forum to silverstripe/blog - Updated example versions to 4.x - Remove "updating composer" section, it now tells you if its out of date - Remove ss-auto-git-ignore module reference. The module hasn't been updated in ages, and it's much less necessary now that all relevant modules are on composer - Add .env example config to getting started docs, I didn't realise it was stripped from the default --prefer-dist composer install
2019-11-18 08:02:00 +01:00
SilverStripe is installed via [Composer](https://getcomposer.org), a package management tool for PHP that
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
lets you install and upgrade the framework and other modules.
Assuming you've got this tool, run the following command to install SilverStripe:
Added docs for composer
2012-11-03 06:00:58 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
```
composer create-project silverstripe/installer my-project
```
Added docs for composer
2012-11-03 06:00:58 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
Within the newly created `my-project` folder, point your webserver at the `public/` folder.
DOCS Remove archive download references (#9250) See https://github.com/silverstripe/silverstripe-framework/issues/9232. Also simplifies composer instructions a bit: - Removes composer update --no-dev references, that's a bit of an edge case that people can just discover on getcomposer.org if they need it - Changed example from the unused and oudated silverstripe/forum to silverstripe/blog - Updated example versions to 4.x - Remove "updating composer" section, it now tells you if its out of date - Remove ss-auto-git-ignore module reference. The module hasn't been updated in ages, and it's much less necessary now that all relevant modules are on composer - Add .env example config to getting started docs, I didn't realise it was stripped from the default --prefer-dist composer install
2019-11-18 08:02:00 +01:00
Now create a `.env` file your project root (not the `public/` folder).
It sets up the minimum required [environment variables](environment_management).
Replace the placeholders as required:
```
SS_DATABASE_CLASS="MySQLDatabase"
SS_DATABASE_NAME="<database>"
SS_DATABASE_SERVER="localhost"
SS_DATABASE_USERNAME="<user>"
SS_DATABASE_PASSWORD="<password>"
SS_DEFAULT_ADMIN_USERNAME="admin"
SS_DEFAULT_ADMIN_PASSWORD="password"
Adding SS_ENVIRONMENT_TYPE to documentation Before running a dev/build the first time, you need to specify dev as your environment type. The variable wasn't mentioned as part of the list so I've added it. Let me know if it's not clear about the difference between the states, or it should be better documented here somehow.
2020-01-13 10:59:06 +01:00
SS_ENVIRONMENT_TYPE="<dev|test|live>"
DOCS Remove archive download references (#9250) See https://github.com/silverstripe/silverstripe-framework/issues/9232. Also simplifies composer instructions a bit: - Removes composer update --no-dev references, that's a bit of an edge case that people can just discover on getcomposer.org if they need it - Changed example from the unused and oudated silverstripe/forum to silverstripe/blog - Updated example versions to 4.x - Remove "updating composer" section, it now tells you if its out of date - Remove ss-auto-git-ignore module reference. The module hasn't been updated in ages, and it's much less necessary now that all relevant modules are on composer - Add .env example config to getting started docs, I didn't realise it was stripped from the default --prefer-dist composer install
2019-11-18 08:02:00 +01:00
```
Added docs for composer
2012-11-03 06:00:58 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
Now you should be able to build your database by running this command:
ENHANCEMENT Added sapphire/docs (migrated from https://github.com/chillu/silverstripe-doc-restructuring)
2011-02-07 07:48:44 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
```
vendor/bin/sake dev/build
```
ENHANCEMENT Added sapphire/docs (migrated from https://github.com/chillu/silverstripe-doc-restructuring)
2011-02-07 07:48:44 +01:00
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
Your website should be available on your domain now (e.g. `http://localhost`).
The CMS login can be accessed at `/admin`.
Added docs for composer
2012-11-03 06:00:58 +01:00
DOCS Remove archive download references (#9250) See https://github.com/silverstripe/silverstripe-framework/issues/9232. Also simplifies composer instructions a bit: - Removes composer update --no-dev references, that's a bit of an edge case that people can just discover on getcomposer.org if they need it - Changed example from the unused and oudated silverstripe/forum to silverstripe/blog - Updated example versions to 4.x - Remove "updating composer" section, it now tells you if its out of date - Remove ss-auto-git-ignore module reference. The module hasn't been updated in ages, and it's much less necessary now that all relevant modules are on composer - Add .env example config to getting started docs, I didn't realise it was stripped from the default --prefer-dist composer install
2019-11-18 08:02:00 +01:00
For more information on how to maintain your installation or install projects,
check out [Using SilverStripe with Composer](composer).
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
## Guided Installation
Added docs for composer
2012-11-03 06:00:58 +01:00
NEW: Remove web installer, move to separate package (#9231) * Remove installer * Remove exposed install files * Replace Dev/Install classes still in use * Update changelog * FIX make the grid field actions consistent to what they look like on pages Resolves https://github.com/silverstripe/silverstripe-admin/issues/904 * Docs changes
2019-09-11 03:10:25 +02:00
If you are unsure on how this all works, please jump on our [lessons](https://www.silverstripe.org/learn/lessons/v4/).
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
Webserver setup is covered in
DOCS Remove archive download references (#9250) See https://github.com/silverstripe/silverstripe-framework/issues/9232. Also simplifies composer instructions a bit: - Removes composer update --no-dev references, that's a bit of an edge case that people can just discover on getcomposer.org if they need it - Changed example from the unused and oudated silverstripe/forum to silverstripe/blog - Updated example versions to 4.x - Remove "updating composer" section, it now tells you if its out of date - Remove ss-auto-git-ignore module reference. The module hasn't been updated in ages, and it's much less necessary now that all relevant modules are on composer - Add .env example config to getting started docs, I didn't realise it was stripped from the default --prefer-dist composer install
2019-11-18 08:02:00 +01:00
[Lesson 4: Setting up a local dev environment](https://www.silverstripe.org/learn/lessons/v4/up-and-running-setting-up-a-local-silverstripe-dev-environment-1).
Added docs for composer
2012-11-03 06:00:58 +01:00
More install options (Vagrant and Bitnami)
2015-04-08 12:31:43 +02:00
NEW: Update docs to be compliant with Gatsby site (#9314) * 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
2019-11-18 05:58:33 +01:00
## Keep learning
[CHILDREN]
ENHANCEMENT Added sapphire/docs (migrated from https://github.com/chillu/silverstripe-doc-restructuring)
2011-02-07 07:48:44 +01:00
## Troubleshooting
DOCS Rewrite server requirements * Remove overly specific PHP RNG instructions (that's just built into PHP7 through random_bytes now, which will throw if no suitable RNG is available) * Remove PHP 5 RNG requirements, since we don't support that PHP release any mre * Remove verbose explanation of PHP 5.6 support * Remove conflicting instructions for PHP memory limits * Remove version numbers from supporetd databases other than MySQL, it's up to the community modules to define that * Remove Oracle support (code is nine years old!) * Make "community supported" status clearer on databases, people can draw their own conclusions as open source users on Github * Remove IIS version number, I think we should just stick to "needs web.config" and not give the impression that this is actively tested * Remove mention of OSes for web servers, that's kind of irrelevant in today's hosting world (containers, PaaS, etc) * Shorten install instructions in favour of a "quickstart" and point to lessons instead * Remove mention of archive download option, we really shouldn't promote this - composer is the de-facto standard * Add generic descriptions of the hosting environment considerations without going too much into specifics * Remove Apache version number, we don't test on different versions, and really mostly rely on mod_rewrite working properly. Laravel does the same (doesn't claim specific Apache version support)
2019-09-03 06:07:17 +02:00
If you run into trouble, see [common-problems](common_problems) or
Docs: Remove forum and IRC references
2017-12-18 23:45:16 +01:00
check our [community help options](https://www.silverstripe.org/community/).
ENHANCEMENT Added sapphire/docs (migrated from https://github.com/chillu/silverstripe-doc-restructuring)
2011-02-07 07:48:44 +01:00
Reference in New Issue Copy Permalink