GitLab

dist/ is the output of 'yarn build' which is not part of the development
process, so if it gets run, don't pollute the repo with it.

All in App.vue but not working have tried various other locations...

sign out is not working - not sure where to put the correct log out sections / getter and action

made pouch connect to CouchDB and build a dist for checking CORS restrictions are working.

basic account registration happens into an accounts PouchDB

installed dependancy

not adding instance select screen yet as authentication method is a place holder approach and so changes are not worth it right now

just for fun, bit of a nicer look for now

But cant get it elsewhere, least library is working not needs to be global or something ?

imported correctly may also help with understanding others.

tweaks to some of the components and some basic styling, still working on importing libraries.

I think i merged master again with SVG_again at the wrong point, so merged back to master for now

Whenever you push to remote now, the CI server will:
1. install repo dependencies
2. do tests (currently just linting)
3. do a build

Whenever a merge to master occurs, apparently there is a way to manually
trigger the 'deploy' stage, which we will make.

That stage will do a recursive copy / rsync to another location,
wherever nn.adamprocter.co.uk is being hosted, possibly the same machine
even. After copying, it'll run 'yarn serve' and our prod site will
receive the fresh copy of master and be fully updated.

Eventually, I'd like to have that part run in duplicate / haproxy, so we
can take one half down and update it, while the other half is still up.
No downtime during deploys.

not secure as you can still hack URLs but better
Not added instance select will do , but needs more logic