Given how widespread PY310's usage has become, and how we're just a few months away from PY311 major release. This is a slightly late bumping but necessary to ensure smoother updates & maintenance for Frappe, ERPNext & other apps in the coming years. Almost all people who participated in the pool from the community as well as Frappe team voted (via active telegram groups) PY310 as their preferred minimum requirement for v14.
44 lines
1.4 KiB
YAML
44 lines
1.4 KiB
YAML
name: 'Frappe Assets'
|
|
|
|
on:
|
|
push:
|
|
branches: [ develop ]
|
|
|
|
jobs:
|
|
build-dev-and-publish:
|
|
name: 'Build and Publish Assets for Development'
|
|
runs-on: ubuntu-latest
|
|
|
|
steps:
|
|
- uses: actions/checkout@v3
|
|
with:
|
|
path: 'frappe'
|
|
- uses: actions/setup-node@v3
|
|
with:
|
|
node-version: 14
|
|
- uses: actions/setup-python@v4
|
|
with:
|
|
python-version: '3.10'
|
|
- name: Set up bench and build assets
|
|
run: |
|
|
npm install -g yarn
|
|
pip3 install -U frappe-bench
|
|
bench init frappe-bench --no-procfile --no-backups --skip-assets --skip-redis-config-generation --python $(which python) --frappe-path $GITHUB_WORKSPACE/frappe
|
|
cd frappe-bench && bench build
|
|
|
|
- name: Package assets
|
|
run: |
|
|
mkdir -p $GITHUB_WORKSPACE/build
|
|
tar -cvpzf $GITHUB_WORKSPACE/build/$GITHUB_SHA.tar.gz ./frappe-bench/sites/assets/frappe/dist
|
|
|
|
- name: Publish assets to S3
|
|
uses: jakejarvis/s3-sync-action@master
|
|
with:
|
|
args: --acl public-read
|
|
env:
|
|
AWS_S3_BUCKET: 'assets.frappeframework.com'
|
|
AWS_ACCESS_KEY_ID: ${{ secrets.S3_ASSETS_ACCESS_KEY_ID }}
|
|
AWS_SECRET_ACCESS_KEY: ${{ secrets.S3_ASSETS_SECRET_ACCESS_KEY }}
|
|
AWS_S3_ENDPOINT: 'http://s3.fr-par.scw.cloud'
|
|
AWS_REGION: 'fr-par'
|
|
SOURCE_DIR: '$GITHUB_WORKSPACE/build'
|