hyve-web

Project setup

npm install

Copy .env.example to .env (or, if it shouldn't be in version control, to .env.local) and adapt the values to your needs. You can also use .env.development, .env.production or .env.test for the respective mode in which you want the configuration to be active.

Note that dotenv loads multiple env files if available. For example, if both .env and .env.your-build-mode are present and your build mode is indeed your-build-mode, both will be loaded, with values in .env.your-build-mode overriding the ones in .env, but if there are values in .env that are not in .env.your-build-mode, they will still be there. The developers advise against such a setup since config options for different environments should not be shared.

Compiles and hot-reloads for development

npm run serve

Compiles and minifies for production

npm run build

Lints and fixes files

npm run lint

Customize configuration

See Configuration Reference.

Environment variables

• VUE_APP_TITLE: Title of the app
• VUE_APP_BACKEND_API_URL: Root URL of the backend API
• VUE_APP_MEDIA_URL: Root URL for media files
• VUE_APP_I18N_LOCALE: Locale to use by default (string, e.g., "en")
• VUE_APP_I18N_FALLBACK_LOCALE: Locale(s) to use for messages not available in the chosen locale. If the value is parsable as JSON, it can be used as an array or decision map according to the Vue i18n documentation. Otherwise the value will be used directly.