wagtail/.squash.yml

deployments:
  default:
    dockerimage: python:3.7.4-stretch
    build_steps:
      - apt-get update && apt-get install -y libssl-dev libpq-dev git build-essential libfontconfig1 libfontconfig1-dev curl
      - RUN bash -c "curl -sL https://deb.nodesource.com/setup_10.x | bash -"
      - apt install -y nodejs
      - pip install setuptools pip --upgrade --force-reinstall
      - cd /code
    post_build_steps:
      - npm install --no-save --no-audit --progress=false
      - npm run dist
      - pip install /code
      - mkdir /myproject
      - cd /myproject
      - wagtail start mysite
      - cd /myproject/mysite
      - python manage.py migrate
      - echo "<br><h1>Wagtail test instance</h1><p>Log into <a href='/admin/'>/admin/</a> with 'admin' / 'changeme'.</p>" > home/templates/home/welcome_page.html
      - echo "from django.contrib.auth import get_user_model; User = get_user_model(); User.objects.create_superuser('admin', 'admin@example.com', 'changeme')" | python manage.py shell
    launch_steps:
      - cd /myproject/mysite
      - python manage.py runserver 0.0.0.0:80
    port_forwarding: 80:80
    run_options: -v ~/code:/code
Adding a .squash.yml file 2019-03-05 02:01:47 +01:00			`deployments:`
			`default:`
Pin Squash docker image to a specific version (#5441) Recent builds have been breaking due to the following error: `/post_build.sh: line 2: npm: command not found`. I’m not entirely sure this is the fix, but it looks like this `latest` tag is now resolving to `3.7.4-buster` (https://hub.docker.com/_/python). Debian Buster got released 2 weeks ago. It feels safer to have a pinned dependency, and Stretch is probably what it was resolving to before. 2019-07-19 19:50:25 +02:00			`dockerimage: python:3.7.4-stretch`
Adding a .squash.yml file 2019-03-05 02:01:47 +01:00			`build_steps:`
update squash.yml file to run pip install for the current branch 2019-03-20 18:26:01 +01:00			`- apt-get update && apt-get install -y libssl-dev libpq-dev git build-essential libfontconfig1 libfontconfig1-dev curl`
Upgrade to Gulp v4 & Node 10 * Syntax changes to get Gulp working * Require Node 10, use node 10 in CircleCI and squash.yml * Update docs * resolves #5653 2020-04-28 22:23:15 +02:00			`- RUN bash -c "curl -sL https://deb.nodesource.com/setup_10.x \| bash -"`
update squash.yml file to run pip install for the current branch 2019-03-20 18:26:01 +01:00			`- apt install -y nodejs`
updated .squash.yml config 2019-03-21 23:24:04 +01:00			`- pip install setuptools pip --upgrade --force-reinstall`
update squash.yml file to run pip install for the current branch 2019-03-20 18:26:01 +01:00			`- cd /code`
Explicitly use port 80 for squash.io (#7523) Hopefully prevents scenarios where Squash prompts for a port number and a wrong port number is entered. This leads to the Squash deployment never finishing and eventually timing out. 2021-09-17 18:22:44 +02:00			`post_build_steps:`
Optimise npm install in squash for speed & logs visibility (#6158) * Optimise npm install in squash for speed & logs - `--no-optional` prevents installing dependencies that shouldn’t be needed for a one-off build - `--no-audit` prevents running the `npm audit` - `--progress=false` * Add additional --no-fund flag to npm install * Add "CI=true" environment variable to Squash builds for Node tooling * Move CI=true to commands that need it * Remove options that did not work 2020-06-25 17:03:42 +02:00			`- npm install --no-save --no-audit --progress=false`
update squash.yml file to run pip install for the current branch 2019-03-20 18:26:01 +01:00			`- npm run dist`
			`- pip install /code`
Adding a .squash.yml file 2019-03-05 02:01:47 +01:00			`- mkdir /myproject`
			`- cd /myproject`
			`- wagtail start mysite`
			`- cd /myproject/mysite`
			`- python manage.py migrate`
Replace welcome page for Squash instances 2020-01-24 16:23:58 +01:00			`- echo "<br><h1>Wagtail test instance</h1><p>Log into <a href='/admin/'>/admin/</a> with 'admin' / 'changeme'.</p>" > home/templates/home/welcome_page.html`
Explicitly use port 80 for squash.io (#7523) Hopefully prevents scenarios where Squash prompts for a port number and a wrong port number is entered. This leads to the Squash deployment never finishing and eventually timing out. 2021-09-17 18:22:44 +02:00			`- echo "from django.contrib.auth import get_user_model; User = get_user_model(); User.objects.create_superuser('admin', 'admin@example.com', 'changeme')" \| python manage.py shell`
Adding a .squash.yml file 2019-03-05 02:01:47 +01:00			`launch_steps:`
updated .squash.yml config 2019-03-21 23:24:04 +01:00			`- cd /myproject/mysite`
			`- python manage.py runserver 0.0.0.0:80`
Explicitly use port 80 for squash.io (#7523) Hopefully prevents scenarios where Squash prompts for a port number and a wrong port number is entered. This leads to the Squash deployment never finishing and eventually timing out. 2021-09-17 18:22:44 +02:00			`port_forwarding: 80:80`
updated .squash.yml config 2019-03-21 23:24:04 +01:00			`run_options: -v ~/code:/code`