HTTPS on xampp or LAN?? Read my story. Need Help

[EuchGrimoire]

mga pro.. may idea po ba kayu kung paano maging https xampp sa LAN?
for example https://computername.. possible po ba yan? nagsertz po ako ng way. ansabe kelangan gumawa ng cert at
iimport lahat sa browser for each pc. (Local lang po kasi tong site ko). eeh mejo hassle po kasi kung ganun.
the story behind this is the desktop push notification, eto po yung mga possible way na naiisip ko para dun:

1. gagamit akong custom na desktop push notification gamit long polling ajax, eeh ang pagkakaalam ko po is hindi xa magnonotif kapag
nakaclose yung site di ba. so mejo no sakin..

2. gagamit akong 3rd party kagaya ng onesignal, pero hindi ko lang alam if possible yun na magnotif sa specific na user.

3. para maachieve na magnotif sa specifc na user, gagamit akong custom na notif yung long polling ajax, which is.. hindi naman kaya magnotif kapag naka close yung site.

4. gagawa akong cert, iinstall pa perbrowser ng client. (ayoko lang kasi mahassle mga client). at gagamit ng long polling with push notif na may service worker ( para maachieve yung kahit nakaclose yung browser di ba?)

please help me decide or baka may teknik kayu pang desktop push notification while nakaclose yung site and specific na tao.
Thanks!

 

[calbee]

If you plan to use an https over the internet, you can create your own free certificate here: https://letsencrypt.org/getting-started/. However, if the server is on a LAN, you can create your own self-sign certificate (more info: https://benohead.com/generating-new-certificate-xampp-windows/)

The drawback for having a self-signed certificate is you have to install it on each client. Usually, the browser will show a prompt the first time they visit the website to install the cert.


Also, all the options you outlined need a push server to be up and running-- that's how the service is supposed to be designed, using client-server architecture. The website you are referring to is just another layer for the client to interact with if they need to using a web browser. However, it is not necessary. Pwede ka gumawa ng push server as a separate entity using websocket. For example, socket.io or pusherapp.

 

[EuchGrimoire]

If you plan to use an https over the internet, you can create your own free certificate here: https://letsencrypt.org/getting-started/. However, if the server is on a LAN, you can create your own self-sign certificate (more info: https://benohead.com/generating-new-certificate-xampp-windows/)

The drawback for having a self-signed certificate is you have to install it on each client. Usually, the browser will show a prompt the first time they visit the website to install the cert.


Also, all the options you outlined need a push server to be up and running-- that's how the service is supposed to be designed, using client-server architecture. The website you are referring to is just another layer for the client to interact with if they need to using a web browser. However, it is not necessary. Pwede ka gumawa ng push server as a separate entity using websocket. For example, socket.io or pusherapp.

huwow grabe ang galing, since gusto ko gumawa ng hindi gawa sa 3rd party like onesignal..
sige sir nkakaexcite naman yan.. so sige po so ang naiisip kong option ngayun is:

1. gumawa ng cert.. (Thanks po sa link)

2. pag aralan ang socket.io or pusherapp.. dahil dito, eto po ngayun napasok sa isip ko:

2.1 since halos gawa na yung site ko (Tracker po kasi yun, na pwede magAssign ng gagawin, magnonotify if may inassign sayu). (gawa po yun sa php oop with ajax.). pwede kaya yun singitan ng socket.io? di ko pa po kasi maimagine. admin and client po kasi yun, c admin magAassign, then magnonotify kay specific client. so kunwari ako si admin, ang ttype ko sa browser ko is http://computername:3000, gagana po ba mga php neto?.. then sa mga user lang is http://computername/sitename..

yun lang po.. pacheck nga po if tama yung mga speculations ko po.. Thanks!

 

[kizzbonez]

So ang gusto mo ay i assign sa ibang port ung admin page?pwed naman basta i listen mo ung port 3000 sa httpd.conf .. eto oh pagaralan mo https://kuppalli.wordpress.com/2011...n-your-local-machine-using-xampp-or-apache-2/