Counterpoint Scheduler

There's no built-in scheduler with Counterpoint so this was built on top of it. This project was built using node.js express.js, MS SQL for back-end. Front-end use React.js.

Installation

Install the following

node.js at least version 14.17.5. -- I now use 16.13.0.
Any code editor like Visual Studio Code. But me I use Sublime 3. It won't matter.
$ npm install pm2@latest -g.
After npm installation, copy the pspdfkit/dist/pspdfkit-lib/ to PUBLIC/static/js folder. If the dir do not exists, create them.

Optional Installtion

Depends on what you use to run your front-end. You can use IIS. If you use IIS, use the web.config in order to run the react.js. Tested on IIS. Refer to the internet on how to install IIS 10 for Windows 10 or 11. Then install the Windows URL Rewriter for IIS.

Use npm as installer for node.js. From the back-end folder, run npm install. Do the same in front-end folder.

Reference

https://dev.to/sumitkharche/how-to-deploy-react-application-on-iis-server-1ied https://serverok.in/how-to-serve-static-site-using-pm2 https://pm2.keymetrics.io/docs/usage/quick-start/

Running dev.

From back-end folder run

clear && npm run buildDev && npm start

From front-end folder run

$ clear && npm start

Running production.

From back-end folder run

$ npm run buildProd

it will create compiled files to dist/ folder. Then using pm2 as process management, run if not yet installed. Note: we do not use pm2 anymore. node-windows is better bc it creates windows service. Also, the back-end/node_modules folder is needed to run the windows service. Otherwise, it'll stops immediately. Just put the node_modules along side with /dist folder. Front-end don't needs the node_modules.

$ npm install pm2@latest -g

If installed already.

Jhun@POS-HI-DEMO-0 MINGW64 /c/Scheduler/back-end (main)
$ pm2 start dist/server.js --name scheduler-back-end-8080 -- --port 8080

To run in production mode using pm2. To utilize pm2 according to good practice, run $ pm2 start dist/server.js --name Scheduler-BE-8080 -- --port 8080 Then run $ pm2 serve build/ --spa --name Scheduler-FE-3000 --port 3000

To run in production using node-windows instead of pm2. node-windows is better by the way.

npm i node-windows -g. Close the terminal and run as Administrator.
Run npm link node-windows.
Go to the root directory and copy the service.js to the dist/ directory.
From dist dir, run node service.js.
It should show the new service CompuTant Scheduler to the windows service.
It will create new directory daemon in your current dir.
The common error is it cannot connect to sql server. To fix, copy the .env to the dist dir.
Restart the new windows service. You're good to go.

NOTE: To delete pm2 documentation. We've been using node-windows for months already.

From front-end folder run

clear && npm run build && npm start

Running from browser

To run, from browser pull up http://localhost:3000/createsession?userid=BILLY. BILLY is the Counterpoint user so you can replace it any valid user of Counterpoint.

To Test back-end is running

http://localhost:8080/createsession?userid=BILLY&expiryinminutes=10 will result to like {"status":"OK","data":{"sessionId":"EFD18534-E36A-4AE1-9797-ED8E86D01175"}}

Running ngrok

ngrok-v3-stable-windows-amd64 $ ngrok.exe http 80

Contributing

Jhun Morcilla - software engineer

Thanks to Vincent Pascua for being very supportive.

Scripts

Pull up from browser: http://localhost:3000/createsession?userid=BILLY
Back-end: http://localhost:8080/createsession?userid=BILLY&expiryinminutes=10
http://localhost:3000/admin/invoice/40FD37AB-4AE1-4D2E-A7AF-2E51AF2CC8D4

Common Issues

If Windows service is getting stopped after updating the files like in production, probably you have added a new module while
developing the system. You may update the node_modules as well if that's the case.

License

MIT

Upgrades

The latest node.js version it can use is 16.13.0.
In the development you can install node version manager aka nvm. Now I'm using , version 16.13.0. It's the last version that webpack can build. But the last one I used for long time was v14.9.1. if you want to use version higher than the aforementioned, try solving by applying from here: https://stackoverflow.com/questions/69692842/error-message-error0308010cdigital-envelope-routinesunsupported.

Debugging Android Chrome with PC

Remote Debugging on Android with Chrome

The way your web content behaves on mobile can be dramatically different from the desktop experience. Remote debugging with Chrome DevTools lets you debug live content on your Android device from your development machine.

Debugging Chrome for Android using the Chrome Developer Tools

Remote debugging on Android supports:

Debugging websites in browser tabs.
Debugging WebViews in native Android apps.
Screencasting live to your development machine from your Android device.
Accessing your development server on Android using port forwarding and virtual host mapping.

Requirements

We are going to talk about debugging a website in a Chrome browser tab in this document. To begin remote debugging, you need:

Chrome 32 or later installed on your development machine.
A USB cable to connect your Android device.
For browser debugging: Android 4.0+ and Chrome for Android.

Note: Remote debugging requires your version of desktop Chrome to be newer than the version of Chrome for Android on your device. For best results, use Chrome Canary (Mac/Windows) or the Chrome Dev channel release (Linux) on desktop and Chrome Stable on Android. This ensures the version of desktop Chrome is newer than the version of Chrome for Android.

Setting up your Android device

Follow these instructions to set up your Android device for remote debugging.

Enable USB debugging

On your Android device, select Settings > Developer options.

Note: On Android 4.2 and later, the developer options are hidden by default. To enable the developer options, select Settings > About phone and tap Build number seven times.

In Developer options, select the USB debugging checkbox:
If an alert prompts you to allow USB debugging. Tap OK.

Connect your device

Connect the Android device to your development machine using a USB cable.

Note: If you are developing on Windows, install the appropriate USB driver for your device. See OEM USB Drivers on the Android Developers' site.

Discovering devices in Chrome

After setting up remote debugging on Android, discover your device in Chrome.
On your desktop Chrome browser, navigate to chrome://inspect. Confirm that Discover USB devices is checked.
On your device, an alert prompts you to allow USB debugging from your computer. Tap OK.
The message USB debugging connected displays in the device's notification drawer.

Note: During remote debugging, Chrome prevents your device’s screen from going to sleep. This feature is useful for debugging, but is also less secure. So be sure to keep an eye on your device!

On your computer, the chrome://inspect page displays every connected device, along with its open tabs and debug-enabled WebViews.

Debugging remote browser tabs

From the chrome://inspect page, you can launch DevTools and debug your remote browser tabs.
To start debugging, click inspect below the browser tab you want to debug.
A new instance of Chrome DevTools launches on your computer. From this instance, you can interact with the selected browser tab on your device in real time.

For example, you can use DevTools to inspect web page elements on your device:

When you mouse over an element in the Elements panel, DevTools highlights the element on your device.
You can also click the Inspect Element inspect element icon icon in DevTools and tap your device screen. DevTools highlights the tapped element in the Elements panel.

Debugging tips

Here are a few tips to help get you started with remote debugging:

Use F5 (or Cmd+r on Mac) to reload a remote page from the DevTools window.
Keep the device on a cellular network. Use the Network panel to view the network waterfall under actual mobile conditions.
Use the Timeline panel to analyze rendering and CPU usage. Hardware on mobile devices often runs much slower than on your development machine.
If you’re running a local web server, use port forwarding or virtual host mapping to access the site on your device.

Live screencasting

Shifting your attention between screens isn’t always convenient. Screencast displays your device's screen right alongside DevTools on your development machine. You can interact with the content on your device from the screencast too.

As of KitKat 4.4.3, screencast is available for both browser tabs and Android WebViews.

To start screencasting, click the Screencast screencast icon icon in the upper right corner of your remote debugging DevTools window.
The Screencast panel opens on the left and displays a live view of your device's screen.

Screencast only displays page content. Transparent portions of the screencast are covered by the omnibox, device keyboard, and other device interfaces.

Note: Because screencast continuously captures frames, it has some performance overhead. If your tests are sensitive to frame rate, disable screencast.

When you interact with the screencast, clicks are translated into taps, firing proper touch events on the device. Keystrokes from your computer are sent to the device, so you can avoid typing with your thumbs.

Other DevTools work with the screencast too. For example, to inspect an element, click the Inspect Element inspect element icon icon and then click inside the screencast.

Tips: To simulate a pinch gesture, hold Shift while dragging. To scroll, use your trackpad or mouse wheel or fling with your pointer.

Port forwarding

Port forwarding on Chrome for Android makes it easy to test your development site on mobile. It works by creating a listening TCP port on your mobile device that maps to a particular TCP port on your development machine. Traffic between these ports travels through USB, so the connection doesn't depend on your network configuration.

To enable port forwarding:

Open chrome://inspect on your development machine.
Click Port Forwarding. The port forwarding settings display.
In the Device port field, enter the port number you want your Android device to listen on. (The default port is 8080.)
In the Host field, enter the IP address (or hostname) and port number where your web application is running.
This address can be any local location accessible from your development machine. Currently, port numbers must be between 1024 and 32767 (inclusive).
Check Enable port forwarding.
Click Done.
The port status indicators on chrome://inspect are green when port forwarding is successful.

Now you can open a new Chrome for Android tab and view the content of your local server on your device.

Adapted from Chrome DevTools Docs

jhunexjun / CP_Scheduler