best practice

release should be easy ....

Whenever you push to a designated branch, it releases on a server (test / production).
Dist files are build on the server (where possible)
We are able to roll back (db + code)

Here are three options on how to achieve this:

option 1 - use bitbucket book with this module.

use this module:

first

set:

SS_RELEASE_TOKEN=" ___ HELLO ___ OR SOMETHING LIKE THAT __"
SS_RELEASE_SCRIPT="run.sh"

in your .env file.

create a release script in the root of your silverstripe project (e.g. run.sh)

finally

add a hook to bitbucket https://mysite.co.nz/_resources/vendor/sunnysideup/release/client/ReleaseProjectFromBitbucketHook.php?ts=29083w490809suiaiofd78897

option 2 - use BEAM

https://github.com/heyday/beam/

option 3 - use bitbucket pipepline

create ssh key on bitbucket.com (settings > pipelines > ssh keys)
add ssh key to server (see if you can just add it to ~/.ssh/authorized_keys) / may have to added to control panel
add bitbucket user to server
turn on pipelines in bitbucket.com
write file below as bitbucket-pipelines.yml

pipelines:
  branches:

    development:
      - step:
          script:
            - ssh -o StrictHostKeyChecking=no [email protected] 'cd ./container/application; bash release.sh'

    master:
      - step:
          script:
            - echo "hello"

add to your repo release.sh

#!/bin/bash
cd "$(dirname "$0")"

echo "=========================" >> release.log
echo "Time: $(date). START UPDATE: " >> release.log
git describe --all --long > release.log
git fetch --all
git pull
composer install --no-dev
vendor/bin/sake dev/build flush=all
bash npm-build-script.sh
git describe --all --long > release.log

OR (with backup)

#!/bin/bash
cd "$(dirname "$0")"

echo "=========================" >> release.log
echo "Time: $(date). START UPDATE: " >> release.log

wget https://silverstripe.github.io/sspak/sspak.phar
chmod +x sspak.phar

rm backup.sspak
php sspak.phar save --db . backup.sspak

git describe --all --long > release.log
git fetch --all
git status
git pull

composer install --no-dev
vendor/bin/sake dev/build flush=all

npm-build-script.sh

git describe --all --long > release.log

add to your repo npm-build-script.sh

bonus idea

Once you have a release file on the server, you can then also run this locally:

ssh myserver 'cd container/application/; bash release.sh'

19/100

Module rating system helping users find modules that are well supported. For more on how the rating system works visit Module standards

Score not correct? Let us know there is a problem

Readme

FOSS License

Structured correctly

Contributing file

Git attributes file

Editor config file

Good code coverage (>40%)

Great code coverage (>75%)

Documentation

CI builds passing

Scrutinizer >6.5

PSR-2 standards

sunnysideup / release

Readme

best practice

option 1 - use bitbucket book with this module.

first

next

finally

option 2 - use BEAM

option 3 - use bitbucket pipepline

bonus idea

Module rating breakdown

Versions

Requires

Requires