Continuous integration and deployment works fine in the ohlwebsite.
Andre and I found an issue with regard to the domain name itself. I can recall the details but I think is in an older issue.
The current solution
Commit changes and automatically push to the current production website.
Setup this following these steps:
Go to .git\hooks folder in your local ohlwebsite repository. Make sure to unhide these folder if is hidden.
Go to post-commit file and replace its current code with the following code:
3. (Recommended but not compulsory for now) Test your change also locally running `npm start`.
4. Make your commits normally and the production repo will be updated automatically.
Continuous integration and deployment works fine in the ohlwebsite. Andre and I found an issue with regard to the domain name itself. I can recall the details but I think is in an older issue.
The current solution
Commit changes and automatically push to the current production website.
Setup this following these steps:
.git\hooks
folder in your local ohlwebsite repository. Make sure to unhide these folder if is hidden.post-commit
file and replace its current code with the following code:abort on errors
set -e
load .env
eval "$(cat .env <(echo) <(declare -x))"
build
npm run build
navigate into the build output directory
cd dist
if you are deploying to a custom domain
echo 'www.example.com' > CNAME
git init
echo "openhardware4.me" > CNAME
git add -A git commit -m 'deploy'
git push -f https://github.com/Open-Hardware-Leaders/open-hardware-leaders.github.io.git master
cd -
git push origin