Manage your Laravel infrastructure on Vapor and fall in love with the scalability and simplicity of serverless.
vendor/bin
directory of your project, which is where Composer installs executables. For example, to view all of the available Vapor CLI commands, you may use the list
command:
vapor
command to php vendor/bin/vapor
.help
command with the name of the command you wish to explore:
login
command:
laravel/vapor-core
package must be installed as a dependency of every Laravel application that is deployed using Vapor. This package contains various Vapor runtime files and a service provider to allow your application to run on Vapor. You may install the Vapor Core into your project using Composer:
team
CLI command. There is no additional charge for creating teams, and they serve as a great way to organize your projects by client or topic.
team:current
command:
team:switch
command:
team:add
CLI command. When you add a new collaborator to your team via the Vapor UI, you may select the permissions to assign to that person. For example, you can prevent a given team member from deleting databases or caches.
You may remove collaborators from your team using the Vapor UI or team:remove
CLI command.
AdministratorAccess
policy or create a custom policy with the specific permissions required by Vapor. After selecting a policy, click “Next.”AdministratorAccess
policy. If desired, you may create a separate AWS account to house this role and contain all of your Vapor resources.From the AWS console
From the AWS CLI
From a support case