FPSMS-frontend
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
 
 
 
CANCERYS\kw093 16f7cf37f0 Merge branch 'master' of https://git.2fi-solutions.com/derek/FPSMS-frontend pirms 1 nedēļas
public initial commit pirms 6 mēnešiem
src Merge branch 'master' of https://git.2fi-solutions.com/derek/FPSMS-frontend pirms 1 nedēļas
types eslint suggested spacing pirms 1 mēnesi
.env.development [feature] update axios pirms 4 mēnešiem
.env.production update pirms 1 mēnesi
.eslintrc.json [config] update IDE typescript config pirms 3 mēnešiem
.gitignore tsms to fpsms pirms 6 mēnešiem
.npmrc initial commit pirms 6 mēnešiem
.nvmrc initial commit pirms 6 mēnešiem
README.md update po pirms 3 mēnešiem
next.config.js Please check the follow files, i comment the warning part for deployment, pirms 1 mēnesi
package-lock.json i18n pirms 2 mēnešiem
package.json update pirms 2 nedēļām
postcss.config.js eslint suggested spacing pirms 1 mēnesi
tailwind.config.js eslint suggested spacing pirms 1 mēnesi
tsconfig.json eslint suggested spacing pirms 1 mēnesi
zip_project.ps1 tsms to fpsms pirms 6 mēnešiem

README.md

This is a Next.js project bootstrapped with create-next-app.

Setting Up the Environment

It is recommended to use the same node and npm versions for development. An easy way to do so would be to use nvm (Linux/MacOS, Windows).

Version

nvm: 1.1.12

After installing nvm, run:

nvm use
npm install

This will automatically use the node version defined in .nvmrc and then proceed with installing the necessary dependencies for development.

Getting Started

First, run the development server:

npm run dev

Open http://localhost:3000 with your browser to see the result.

References

This project uses the following libraries:

Qrcode Testing

https://stackoverflow.com/questions/16835421/how-to-allow-chrome-to-access-my-camera-on-localhost Local Qrcode testing require setting tweak Steps:

  1. Navigate to chrome://flags/#unsafely-treat-insecure-origin-as-secure in Chrome.
  2. Find and enable the Insecure origins treated as secure section (see below).
  3. Add any addresses you want to ignore the secure origin policy for. Remember to include the port number too (if required).