Deploy-Package - GitLite

KO | EN

gitlite — search

#artificial-intelligence #anthropic #rag #codex #kubernetes #cpp #sql #css #database #mcp

Deploy-Package

(★ 17)

The TYPO3.Deploy FLOW3 package

파일 탐색기

ZIP 다운로드

- - FLOW3.php
  - FLOW3Distribution.php
  - TYPO3.php
- - DeployCommandController.php
  - EncryptCommandController.php
- - EncryptionServiceInterface.php
  - InvalidKeyException.php
  - InvalidPassphraseException.php
  - KeyPair.php
  - OpenSslEncryptionService.php
- - CleanupReleasesTask.php
  - CreateArchiveTask.php
  - CreateDirectoriesTask.php
  - GitCheckoutTask.php
  - ShellTask.php
  - SourceforgeUploadTask.php
  - SymlinkReleaseTask.php
  - VarnishPurgeTask.php
- Package.php
- Package.xml
.gitignore
README.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

명령어 용어집

이 문서에서 사용된 명령어를 모아봤습니다. 낯선 명령어가 있다면 펼쳐서 확인해보세요.

🔍

`php`

설명 보기 ▼

PHP 명령줄 인터페이스.
더 많은 정보: <https://www.php.net/manual/en/features.commandline.options.php>.

php {{path/to/file}}

PHP 스크립트를 구문 분석하고 실행:

php {{[-l|--syntax-check]}} {{path/to/file}}

PHP 스크립트의 문법 검사(즉, 린트):

php {{[-a|--interactive]}}

PHP를 대화형으로 실행:

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

TYPO3.Deploy - FLOW3 deployment
====================================

## DESCRIPTION

The deploy package is a complete automatic deployment tool powered by FLOW3. It's best used bot not limited to deploy FLOW3 applications. It might be included in your FLOW3 application but can be run standalone. It's inspired by some features of Capistrano (thanks) concerning the Git workflow.

Some of the features of the deploy package:

* Remote checkout of Git repositories with submodules (sorry, no SVN yet)
* Flexible, declarative configuration of deployments
* Multi-node, multi-application, multi-deployment deployments
* Hook in any deployment stage
* Create custom tasks with a few lines
* Simulate deployments with a dry run

Note that the final name of the package and options / API are very likely to change.

## INSTALLATION

Install the deploy package by cloning this Github repository to `FLOW3_ROOT/Packages/Application/TYPO3.Deploy` of a FLOW3 installation.

## GUIDE

Eeach deployment is a distinct configuration (e.g for development, staging, live environments). Eeach deployment configuration specifies a workflow for the deployment (for now it's just _SimpleWorkflow_, but feel free to create your own), at least one application and assigns nodes to the application(s).

We start by creating a simple deployment configuration in `FLOW3_ROOT/Build/Deploy/MyDeployment.php` for a deployment with name _MyDeployment_:

```php
<?php
  $workflow = new \TYPO3\Deploy\Domain\Model\SimpleWorkflow();
  $deployment->setWorkflow($workflow);

$node = new \TYPO3\Deploy\Domain\Model\Node('example');
  $node->setHostname('example.com');
  $node->setOption('username', 'myuser');
  $deployment->addNode($node);

$application = new \TYPO3\Deploy\Application\FLOW3();
  $application->setDeploymentPath('/home/my-flow3-app/app');
  $application->setOption('repositoryUrl', 'git@github.com:myuser/my-flow3-app.git');
  $application->addNode($node);
  $deployment->addApplication($application);
?>
```

That's a very basic deployment based on the FLOW3 application template `TYPO3\Deploy\Application\FLOW3`. The deployment object is available to the script as the variable `$deployment`. A node is basically a deployment target representing a host. The Node is assigned to the application for the deployment. Finally the application is added to the deployment.

You can get a description of the deployment by running:

$ ./flow3 deploy:describe MyDeployment

Simulate the deployment by running:

$ ./flow3 deploy:simulate MyDeployment

If everything looks right, you can run it:

$ ./flow3 deploy:deploy MyDeployment

## CUSTOMIZATION

Since a deployment descriptor is just a plain PHP file with access to any FLOW3 class it's easy to extend it or program a more complex behavior. But it's even easier to remove tasks or add some simple shell tasks to an existing application template:

```php
<?php
  ...

$workflow->defineTask('mycompany.mypackage:initialize',
  	'typo3.deploy:shell',
  	array('command' => 'cd {releasePath} && ./flow3 mycompany.mypackage:setup:initialize')
  );
?>
```

This adds a new task based on the `typo3.deploy:shell` task with a custom shell command which would run a FLOW3 command. After defining the new task we have to tell the deployment configuration when to execute it:

```php
<?php
  ...

$workflow->defineTask('mycompany.mypackage:initialize',
  	'typo3.deploy:shell',
  	array('command' => 'cd {releasePath} && ./flow3 mycompany.mypackage:setup:initialize')
  );

$deployment->onInitialize(function() use ($workflow, $application) {
  	$workflow->forApplication($application, 'migrate', 'mycompany.mypackage:initialize');
  	$workflow->removeTask('typo3.deploy:flow3:setfilepermissions');
  });

?>
```

This will execute the new task in the _migrate_ stage only for the application referenced by `$application`. As you can see, it's also possible to remove a task from a workflow. Most of the methods are available for global or application specific task configuration.

Besides specifying the execution point via a stage, you can also give an existing task as an anchor and specify the task execution with `afterTask` or `beforeTask`.

## COPYRIGHT

The deployment package is licensed under GNU General Public License, version 3 or later (http://www.gnu.org/licenses/gpl.html). Initial development was sponsored by [networkteam - FLOW3 Agentur](http://www.networkteam.com/flow3-agentur.html).