This repo is for hosting static files by GitHub Pages for now.
Currently, the web code files are in double-entry-generator/wasm, because the web page needs the wasm binary, which would be made by double-entry-generator project.
FYI, I have used the following several operations to create a deg-online GH Pages release:
$ cd ~/Code/double-entry-generator
$ make build-wasm
# wasm release files are created at `wasm-dist` directories, like wasm binary, html, wasm_exec.js in Go etc.
$ mv wasm-dist/* ~/Code/deg-online/
$ cd ~/Code/deg-online
$ git add .; git commit -s; git push
Indeed this is a bad way to deploy new web releases. I suggest the following workflow for the future:
Build and push WASM binary, wasm_exec.js from Go build environment (in GitHub Action, maybe) to deg-online's main branch when a release is created in double-entry-generator.
Build the web application (on every pushes to the main branch) in deg-online and push the web artifacts (dist directory for Vue) to deg-online's gh-pages branch, which the GitHub Action uses.
This repo is for hosting static files by GitHub Pages for now.
Currently, the web code files are in
double-entry-generator/wasm
, because the web page needs the wasm binary, which would be made bydouble-entry-generator
project.FYI, I have used the following several operations to create a
deg-online
GH Pages release:Indeed this is a bad way to deploy new web releases. I suggest the following workflow for the future:
wasm_exec.js
from Go build environment (in GitHub Action, maybe) todeg-online
'smain
branch when a release is created indouble-entry-generator
.main
branch) indeg-online
and push the web artifacts (dist
directory for Vue) todeg-online
'sgh-pages
branch, which the GitHub Action uses./cc @gaocegege
Originally posted by @Triple-Z in https://github.com/deb-sig/deg-online/issues/1#issuecomment-1364022457