AMIA-CIAT demo output website (version 2.0)
A Vue.js projectStatic build files from the latest vue project at branch vue-version.
Contains updated content with new AMIA Phase 2 information and documents.
The following requirements and dependencies were used for this project. Other system and software configurations are open for testing.
- Windows 10 Pro
- NodeJS
- npm version 10.16.3
- npm version 6.9.0
-
Clone the project.
git clone https://github.com/ciatph/ciatph.github.io.git
-
Checkout branch vue-version
git checkout vue-version
-
Install dependencies:
npm install
-
Serve with hot reload at localhost:8080
npm run dev
-
Build for production with minification.
npm run build
(static build files will be generated in the /dist directory) -
Build for production and view the bundle analyzer report
npm run build --report
For a detailed explanation on how things work, check out the guide and docs for vue-loader.
The website, accessible from https://ciatph.github.io serves static build files pushed into the master
branch.
This can be manually done by (a) pushing static build files from the /dist directly into the master
branch, or (b) automatically by pushing vue project code updates into the vue-version
branch. Please follow the instructions below to trigger the automatic Travis CI/CD.
Read on this reference for more information on setting up Travis CI for GitHub pages.
-
Create a branch from
vue-version
.
git checkout -b my-updates-branch
-
Edit and push updates to
my-updates-branch
. -
Create a new Pull Request (PR) from the
my-updates-branch
that you've created to branchvue-version
.- Go to
my-updates-branch
page in GitHub, i.e.:
https://github.com/ciatph/ciatph.github.io/tree/my-updates-branch - Press the [New pull request] button beside the branch navigator dropdown menu [Branch: my-updates-branch].
- Go to
-
Set the following in the resulting "Open a pull request" page:
- base:
vue-version
- compare:
my-updates-branch
- Press the [Create pull request] button.
- WAIT for the Travis CI checks to finish.
- base:
-
Press the [Merge pull request] button.
WARNING: It is important to WAIT for the Travis CI checks from #4 to finish first before pressing this button, else the Travis CI build will fail.
-
View the travis CI status from https://travis-ci.com/ciatph/ciatph.github.io.
New GitHub pages website updates can be viewed from https://ciatph.github.io if the build passed.
Please take note, the steps mentioned in Automatic CI/CD to GitHub Pages Using Travis is the recommended way for publishing updates to the GitHub pages website.
-
Follow the steps from the local Build Setup section. Keep the contents of the /dist directory.
-
Checkout a new branch from the
master
branch.
git checkout -b <NEW_BRANCH_NAME>
-
Copy the static contents of the local /dist directory (from
# 1
) into<NEW_BRANCH_NAME>
. -
Depending on the updated static files, you may need to delete some
.js
,.map
and.css
files from /static/css or /static/js. Make sure that only the contents of /dist will exist in<NEW_BRANCH_NAME>
. -
Push the new branch
<NEW_BRANCH_NAME>
and create a pull request. -
Approve the pull request if there are no conflicts.
For testing purposes, the static build files can be optionally uploaded to Firebase hosting prior to deploying on GitHub pages.
-
Login to the firebase cli as
ciat.ph06
. -
Run
firebase init
.- Are you ready to proceed? - choose Y
- Which Firebase CLI features do you want to set up for this folder? - choose Hosting.
- What do you want to use as your public directory? - type /dist
- Configure as a single-page app (rewrite all urls to /index.html)? - choose Y
- File dist/index.html already exists. Overwrite? - choose N
-
Run
firebase deploy
Updated: 20191113