Git Push Live content to Remote GIT

31 views
Skip to first unread message

Daniel E.

unread,
Mar 17, 2023, 4:26:45 AM3/17/23
to CrafterCMS
Hi,

I'm currently evaluating Crafter CMS (I am running the Docker Containers via Docker Compose) in very basic setup and I got stuck at the point were I want the content, that was published via the Studio Web-UI, to be pushed to a Remote Git-repo.
I have set up my own local GIT Server. I can also push and pull manually.

I created a deployer configuration file that looks as follows:

version: '2.4'
target:
  env: default
  siteName: cnd-31
  localRepoPath: /opt/crafter/data/repos/sites/cnd-31/published
  deployment:
    scheduling:
       enabled: false
    pipeline:
      - processorName: gitPushProcessor
        remoteRepo:
          url: http://XXXX/YYYY/craftercms.git
          branch: live
          username: XXXX
          password: XXXX
        force: true
        pushAll: true

The file is saved as /opt/crafter/data/deployer/targets/cnd-31-default.yaml and accessible inside the (authoring) deployer container.

All the output I get from the deployer Logs ist the following:

deployer_1  | 2023-03-17 08:23:00.000  INFO 21 --- [taskScheduler-3] aftercms.deployer.impl.TargetServiceImpl : Configuration files haven been updated for 'cnd-31-default'. The target will be reloaded.
deployer_1  | 2023-03-17 08:23:00.000  INFO 21 --- [taskScheduler-3] org.craftercms.deployer.impl.TargetImpl  : Closing target 'cnd-31-default'...
deployer_1  | 2023-03-17 08:23:00.001  INFO 21 --- [taskScheduler-3] org.craftercms.deployer.impl.TargetImpl  : Stopping current and pending deployments for target 'cnd-31-default'
deployer_1  | 2023-03-17 08:23:00.001  INFO 21 --- [taskScheduler-3] org.craftercms.deployer.impl.TargetImpl  : Releasing resources for target 'cnd-31-default'
deployer_1  | 2023-03-17 08:23:00.004  INFO 21 --- [taskScheduler-3] aftercms.deployer.impl.TargetServiceImpl : Loading target for configuration file /opt/crafter/data/deployer/targets/cnd-31-default.yaml


deployer_1  | 2023-03-17 08:23:00.253  INFO 21 --- [taskScheduler-3] oyer.impl.upgrade.DeployerUpgradeManager : Starting upgrade for target 'TargetImpl{env='default', siteName='cnd-31', configurationFile=/opt/crafter/data/deployer/targets/cnd-31-default.yaml}'
deployer_1  | 2023-03-17 08:23:00.256  INFO 21 --- [taskScheduler-3] org.craftercms.deployer.impl.TargetImpl  : Closing target 'cnd-31-default'...
deployer_1  | 2023-03-17 08:23:00.256  INFO 21 --- [taskScheduler-3] org.craftercms.deployer.impl.TargetImpl  : Stopping current and pending deployments for target 'cnd-31-default'
deployer_1  | 2023-03-17 08:23:00.256  INFO 21 --- [taskScheduler-3] org.craftercms.deployer.impl.TargetImpl  : Releasing resources for target 'cnd-31-default'

deployer_1  | 2023-03-17 08:23:00.493  INFO 21 --- [deployment-10] org.craftercms.deployer.impl.TargetImpl  : Executing init hooks for target 'cnd-31-default'
deployer_1  | 2023-03-17 08:23:00.493  INFO 21 --- [deployment-10] org.craftercms.deployer.impl.TargetImpl  : Creating deployment pipeline for target 'cnd-31-default'
deployer_1  | 2023-03-17 08:23:00.505  INFO 21 --- [deployment-10] org.craftercms.deployer.impl.TargetImpl  : Checking if deployments need to be scheduled for target 'cnd-31-default'

It just won't work. Even a simple "CommanLineProcessor" that would write a test-file won't work.
What step am I missing? 
Can somebody please help me out?

regards,
  Daniel

Daniel E.

unread,
Mar 17, 2023, 9:08:22 AM3/17/23
to CrafterCMS
Nevermind, I stumbled upon this post

I essentially did exactly the same... Copied the source code an suddenly it worked... mayber because I renamed the file to cnd-31-live.yaml and set env: live?

Best, 
  Daniel

Sumer Jabri

unread,
Mar 17, 2023, 9:44:42 AM3/17/23
to CrafterCMS
Glad it worked.
Reply all
Reply to author
Forward
0 new messages