/Ecomuseu-do-Corvo---Kioske

Primary LanguageTypeScript

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

yarn react-start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn react-test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn react-build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

yarn react-build:staging

Same as react-build, but uses the .env.staging file in order to get the staging configuration.

yarn react-eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Available Configurations

If you are using a global configuration file .env or a staging file .env.staging, you must specify the following:

NODE_PATH=src/
REACT_APP_API_URL=<API_URL> // Place here your API URL

Packaging

Check this out: https://medium.com/@johndyer24/creating-and-deploying-an-auto-updating-electron-app-for-mac-and-windows-using-electron-builder-6a3982c0cee6

In order to package a new release, you must run the following commands in the given order:

  1. yarn react-build // Will build with production variables
  2. yarn electron-dist // Will copy electron files inside build folder
  3. yarn package // Will package the files to an exe
    • yarn deploy // Same as package, but will deploy to github

Configuration

Keep in mind that you must create a electron-builder.yml file with the given paramenters:

appId: [APP NAME]
publish:
  provider: github
  token: [YOUR GITHUB ACCESS TOKEN]

files:
  - "./build/**/*",
  - "node_modules/**/*"

win":
  target: "NSIS",
  icon: [LOGO PATH]