FPSMS-frontend
25'ten fazla konu seçemezsiniz Konular bir harf veya rakamla başlamalı, kısa çizgiler ('-') içerebilir ve en fazla 35 karakter uzunluğunda olabilir.
 
 
CANCERYS\kw093 57d537f930 Merge branch 'master' of http://svn.2fi-solutions.com:8300/derek/FPSMS-frontend 16 saat önce
public logo update 2 ay önce
src Merge branch 'master' of http://svn.2fi-solutions.com:8300/derek/FPSMS-frontend 16 saat önce
types eslint suggested spacing 5 ay önce
.env.development [feature] update axios 7 ay önce
.env.production update 5 ay önce
.eslintrc.json [config] update IDE typescript config 7 ay önce
.gitignore tsms to fpsms 9 ay önce
.npmrc initial commit 9 ay önce
.nvmrc initial commit 9 ay önce
README.md update po 6 ay önce
check-translations.js update 1 ay önce
next.config.js Please check the follow files, i comment the warning part for deployment, 5 ay önce
package-lock.json i18n 5 ay önce
package.json update 4 ay önce
postcss.config.js eslint suggested spacing 5 ay önce
tailwind.config.js eslint suggested spacing 5 ay önce
tsconfig.json eslint suggested spacing 5 ay önce
zip_project.ps1 the zip file ignore the .env.development to make logout go to 10.100.0.81:3000 temperately 2 hafta önce

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).