Nms-api-start-services: Difference between revisions

From I Will Fear No Evil
Jump to navigation Jump to search
(Created page with "Currently there is no systemd, so all daemons are actually running via the PHP server command directly. <pre> cd /opt/nmsApi/ php -S 0.0.0.0:8002 -t public & </pre> Nothing...")
 
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
=== API control ===
Currently there is no systemd, so all daemons are actually running via the PHP server command directly.
Currently there is no systemd, so all daemons are actually running via the PHP server command directly.


Line 7: Line 8:


Nothing has been done as far as headers or CORS at this time.  This simply starts the API system
Nothing has been done as far as headers or CORS at this time.  This simply starts the API system
=== Todo ===
# Build systemd for daemons.
## Use require Apache or Nginx to be active so they can pull via API calls
# Build Apache2 configuration for API
# Build Nginx configuration for API
* Avoid using Apache or Nginx auth tools, as we want a fix for issues to be within the code, not the webserver
[[Category:NMS]]

Latest revision as of 08:10, 7 June 2023

API control

Currently there is no systemd, so all daemons are actually running via the PHP server command directly.

cd /opt/nmsApi/
php -S 0.0.0.0:8002 -t public &

Nothing has been done as far as headers or CORS at this time. This simply starts the API system

Todo

  1. Build systemd for daemons.
    1. Use require Apache or Nginx to be active so they can pull via API calls
  2. Build Apache2 configuration for API
  3. Build Nginx configuration for API
  • Avoid using Apache or Nginx auth tools, as we want a fix for issues to be within the code, not the webserver