Platform or Platform.sh is the infrastructure which is running all your projects.
A project is the site that you're working on. Each project can contain multiple applications and be deployed in their own environments.
An environment is a standalone copy of your site, complete with code, data, and running services. The master branch is the production environment, while any other branch can be setup as an otherwise identical testing environment.
If you want to delete your project and cancel your subscription, simply go to your user profile and click on "Edit plan" on the project you want to delete. Then you can click on the link: "delete your Platform.sh plan".
This will delete your project and stop invoicing for this project. If you have multiple projects, your subscription will continue until you don't have any projects left.
Platform.sh uses MariaDB to manage and store your databases. It's a fork of MySQL which is more stable and has more interesting features.
Yes! Branching an environment creates an exact copy (snapshot) of the parent environment, containing the files, the database, the services...
Yes! Unlike other PaaS providers Platform.sh supports non-ephemeral storage. When you configure your application you can tell us what directories you want to be read/write (these are called mounts). These will be mounted on a distributed file system (which is transparent for you). When you back-up your environment they will be backed up as well. When you create a new staging environment... these will be cloned with the rest of your data.
If you push a local branch that you created with Git, you create what we call an
inactive environment, ie. an environment that is not deployed.
This means there won't be any services attached to this branch.
You are able to convert an
inactive environment into an
active environment and vice versa back from the environment configuration page or using the CLI.
Master gets all the resources that are divided into each service (PHP 40%, MySQL 30%, Redis 10%, Solr 20%…). Each Development environment gets the Development plan resources.
You're logged in to the PHP service. It's a read-only file system.
No ! Since the PHP service you access via SSH is a read-only file system, you'll have to push your fix to be able to test it.
We try to make the log as self-explanatory as possible, so you should see the Git output and also output from the drush make...
You can also find it back by clicking on the status of the activity in the
Platform.sh is built on Debian.
The Development plan provides all the tools to build your website. You can create as many development profiles as you wish for yourself and for your team.
Once your project is built and ready for production, you can choose another plan to go live. These plans are listed on the pricing page.
Please validate the syntax of your YAML file. Don't use tabs. And if all fails, contact support.
Platform leverages the power of public cloud infrastructures like AWS, Microsoft Azure, or Huawei/Orange. We can deploy your site in a region that is very close to your target audience.
'sh' is the short version of shell.
According to Wikipedia™, in computing, a shell ) is a user interface for access to an operating system's services. Generally, operating system shells use either a command-line interface (CLI) or graphical user interface (GUI). This is exactly what Platform.sh is about: Giving developers tools to build, test, deploy, and run great websites!
".sh" is also the TLD for Saint Helena that looks like a lovely island, and whose motto is: "Loyal and Unshakeable" which we also strive to be.
In order for MAMP to work well with the symlinks created by the Platform.sh CLI, add the following to the section under Hosts > Advanced called “Customized virtual host general settings.” For more details visit MAMP Pro documentation page.
<Directory> Options FollowSymLinks AllowOverride All </Directory>
When you specify your document root, MAMP will follow the symlink and substitute the actual build folder path. This means that when you rebuild your project locally, you will need to repoint the docroot to the symlink again so it will refresh the build path.
Yes we do, and it is easy to enable. To do so please go to your Account Settings on our Account site. Then click on the left tab called Security which will propose you to enable TFA Application.