overseas-working-visitors
v0.1.0
Published
Overseas Working Visitors Landing Page
Downloads
2
Readme
Overseas Working Visitors Landing Page
Related Links.
https://www.nib.com.au/overseas-working-visitors
https://www.nib.com.au/overseas-working-visitors/482-temporary-skills-shortage-health-insurance
https://www.nib.com.au/overseas-working-visitors/457-visa-health-insurance
https://www.nib.com.au/overseas-working-visitors/485-temporary-graduate-visa-health-insurance
Make sure that you have the Gatsby CLI program installed:
Last worked with node 14.19.1,
** note deleting package-lock.json file will cause build errors
npm install --global gatsby-cli
Then you can run it by:
npm install
npm run develop
And proceed to http://localhost:8000/
Production build
To see a preview of the production build, simply run:
npm run build
npm run serve
And proceed to http://localhost:9000/
Note: Due to the path-prefix, assets (client side JS, images, fonts) will likely not load locally. The same behaviour is experienced in kaos when accesses the static site directly from s3. To see a working site you must also configure the location in the nib-www-router. or you can try running
To run through the www router locally
Get the latest version of the www router (which points to http://localhost:9000) Run the docker box via vagrant or on your host machine
gatsby build --prefix-paths
gatsby serve -H 0.0.0.0
Testing in Kaos
slice-of-overseas-working-visitors
= BRANCH_NAME
Features
Steve for publishing
The starter has a familiar /deploy
directory with an apps.yml
and Gemfile
for steve pipeline management.
Prepush hook
There is a prepush
hook that formats your code with prettier and runs unit tests.
Styled Components for styling
Hot module reloading
Jest for unit testing
Prettier for code formatting
React-html for a common html layout and third party scripts
Our Theme component to provide styling information and css normalize
Commonly used nib design system components
Logs
Chat launcher local development
There's a environment variable flag that you can set for local development convenience when it comes to testing and debugging the @nib/chatbot-launcher
package (which is centralised in the <Layout/>
component. Note that this only affects behaviour in localhost.
#.env.development
# If you're running the `client` locally, in the `chatbot-client-monorepo`:
REACT_APP_LOCAL_CHAT_LAUNCHER_URL=http://localhost:8080
Note that this overrides the URL protocol, origin, AND path. As such you shouldn't expect the prop suffix path
to be added to this URL. If you want to test different path
suffixes, then you'll need to include that in your env var value.
Note, however, that any calculated query parameters (e.g. load external config) ARE appended to the local override URL as well.