name: "Install and Start WordPressify"

env:
  WPFY_GH_REPO: ${{ github.repository }}
  WPFY_GH_REF: ${{ github.ref }}

on:
  push:
  workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - run: npm ci --no-audit
      - run: ./installer/index.js -y

name: "Install and Start WordPressify"

env:
  WPFY_GH_REPO: ${{ github.repository }}
  WPFY_GH_REF: ${{ github.ref }}

on:
  push:
  workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - run: npm ci --no-audit
      - run: |
          mkdir wpfy_global;
          cd wpfy_global;
          npm init -y;
          npm install ../;
          mkdir test;
          cd test;
          ../node_modules/.bin/wordpressify -y;
          for container in $( docker-compose ps -q ); do
          docker exec $container echo "Hi!";
          done;

Improve GitHub Actions to better emulate real usage
Improve GitHub Actions to better emulate real usage

Before this commit, GitHub Actions checked out the WordPressify
repository and ran the installer from there.  There are two problems
with this:

- No checks that containers were built successfuly
- All files get downloaded by the checkout process, rather than
  by the wordpressify command alone.

Now we match real usage more closely. And there are also checks in
place which make sure that the containers are running after
WordPressify installation is completed.
