vue
Description
Project will be deployed to server and processed with npm and gulp.
npm is also used for dependency management and local testing.
Project structure
Default project structure is the following:
.
├── dist
| ├── css
| | └── style.all.min.css
| ├── img
| ├── js
| | └── script.all.min.js
| ├── index.html
| ├── *.html
| └── *
| └── *.html
├── src
| ├── css
| | └── *.css
| ├── img
| ├── js
| | ├── store
| | | └── *.store.js
| | ├── app.js
| | ├── app.router.js
| | ├── app.store.js
| | ├── functions.js
| | └── index.js
| ├── less
| | ├── global.less
| | ├── index.less
| | ├── media.less
| | └── style.less
| ├── pug
| | ├── includes
| | | └── mixins.pug
| | ├── index.pug
| | ├── *.pug
| | └── *
| | └── *.pug
| ├── vue
| | ├── components
| | | ├── *
| | | | └── *.vue
| | | └── *.vue
| | ├── pages
| | | ├── *
| | | | └── *.vue
| | | └── *.vue
| | └── index.vue
| ├── index.html
| ├── *.html
| └── *
| └── *.html
├── .gitignore
├── .gitlab-ci.yml
├── bs-config.json
├── gulpfile.js
└── package.json
-
dist/css/style.all.min.cssis CSS styles file. All styles will be compiled to it -
dist/imgis a folder for images. It will be moved as is -
dist/js/script.all.min.jsis JS script file. All scripts will be compiled to it -
dist/index.htmlis main HTML file -
dist/**/*.htmlare other HTML files. Their paths relative tosrcorsrc/pugparent folder will be preserved indistfolder -
src/cssfolder is supposed to be only used as CSS libraries folder -
src/imgfolder is used for images. It will be moved as is -
src/jsfolder is used for JS scripts-
src/js/store/*.store.jsare Vuex module files. -
src/js/app.jsis main Vue app file. All other app files should be imported to it. -
src/js/app.router.jsis vue-router config file. -
src/js/app.store.jsis main Vuex file. -
src/js/index.jsis main file for scripts. All other JS files should be imported to it -
src/js/functions.jsis auxiliary file and supposed to be used for JS functions. All functions necessary in other files should be exported
-
-
src/lessfolder is used for LESS styles-
src/less/global.lessis auxiliary LESS file and supposed to be used for global styles -
src/less/index.lessis main file. All other styles should be imported to it -
src/less/media.lessis auxiliary LESS file and supposed to be used for styles for different media types/devices -
src/less/style.lessis primary LESS file for styles
-
-
src/pugfolder is used for Pug files-
src/pug/includesare auxiliary Pug files and supposed to be used for including, mixins, templates etc. These files will not be compiled by Pug compiler-
src/pug/includes/mixins.pugis auxiliary Pug file and supposed to be used for mixins
-
-
src/pug/index.pugis main Pug file that will become main HTML file -
src/pug/**/*.pugare other Pug files. Their paths relative tosrc/pugfolder will be preserved indistfolder
-
-
src/vuefolder is used for Vue single-file components-
src/vue/componentsfolder is used for Vue app components -
src/vue/pagesfolder is used for Vue app pages -
src/vue/index.vueis main Vue app component/page that containsrouter-view
-
-
src/index.htmlis main HTML file -
src/**/*.htmlare other HTML files. Their paths relative tosrcfolder will be preserved indistfolder -
.gitignoreis used to ignore files.distfolder is ignored -
.gitlab-ci.ymlis a CI config. Should not be edited in most of cases -
bs-config.jsonis a Browsersync settings -
gulpfile.jsis a gulp config. Inpaths.filesvariable inside it can be specified files and folders that will be moved todistfolder as is -
package.jsonis main file for npm. Project dependencies can be specified inside it
Note: All markup files will be processed in parallel and therefore their relative paths should not be duplicated. Be aware: in the above project structure files src/index.html and src/pug/index.pug do have the same relative paths!
How to get
-
Download it manually or get it using project-template-loader:
project-template-loader web/vue
2. Open `package.json` and change `name` and `version` to the name and version of your project
## How to use
1. Open terminal
2. Go to your project folder
3. Run
``` bash
npm start
to start local server that will track changes in project files and update browser page (supposed to be used during development)
*or*
``` bash
npm run build-testing
to get files in `dist` folder ready to deploy to `testing` environment
*or*
``` bash
npm run build-staging
to get files in `dist` folder ready to deploy to `staging` environment
*or*
``` bash
npm run build
to get files in `dist` folder ready to deploy to production
### Useful tools
#### weinre
weinre is a debugger for web pages, like FireBug (for FireFox) and Web Inspector (for WebKit-based browsers), except it's designed to work remotely, and in particular, to allow debugging of web pages on mobile devices such as a phones.
To enable weinre support (which is enabled in markup index files by default), the following comment should be added to markup:
* in HTML:
```html
<!-- weinre -->
-
in Pug:
//- weinre
After that, weinre will be accessible at [http://weinre.dev.gvia.group](http://weinre.dev.gvia.group).
## Workflow
### Local
During developing under local environment all scripts and styles are not minified and source maps are available for them.
By default, project is accessible at [http://localhost:3000](http://localhost:3000) and Browsersync control panel at [http://localhost:3001](http://localhost:3001).
In addition to that, weinre is accessible at [http://weinre.dev.gvia.group](http://weinre.dev.gvia.group).
### Review
All branches except `dev` and `master` are used to review changes live.
These branches will be built and each one will be available under its own environment with unique address.
For each of them weinre is accessible at [http://weinre.dev.gvia.group](http://weinre.dev.gvia.group).
### Testing
Branch `dev` is used to merge all changes and review them. All developers are responsible to merge their changes to `dev` by themselves.
This branch will be built and available under `testing` environment.
Weinre is accessible at [http://weinre.dev.gvia.group](http://weinre.dev.gvia.group).
### Staging
Branch `master` is used to review changes before deploying to production. It should only contain stable versions that are supposed to be released.
This branch will be built and available under `staging` environment.
Weinre is accessible at [http://weinre.dev.gvia.group](http://weinre.dev.gvia.group) with debug id `staging`.
### Production
To deploy to production:
1. Create the following [secret variables](https://git.gvia.group/help/ci/variables/README.md#secret-variables):
* `HOSTING_PROJECT` - project name on hosting server
* `HOSTING_PROJECT_URL` - project site URL
2. Ask GitLab administrator to assign the project to specific runner that will deploy the project