The programming languages used to build the web often find their way into apps, too. That’s largely due to software that allows developers to “reuse” the code they write for the web in products they build to run on operating systems like Linux, Android, Windows, and macOS.
See the full article here
You need A Fully Qualified Domain Name (FQDN) pointing to a dedicated IP address of the webserver.
This needs to be configured by your DNS administrator or provider.
1 – Install Certbot in Centos 8
sudo curl -O https://dl.eff.org/certbot-auto
chmod 0755 /usr/local/bin/certbot-auto
2 – Configure Nginx server_name on nginx.conf
Edit nginx.conf an change the variable server_name to the same FQDN
of your server for example: server_name www.mysphere.com.br;
3 – Run the certbot command:
Execute sudo /usr/local/bin/certbot-auto –nginx and follow the instructions
Test if your Nginx server using https://<server_name>
I am creating a server (Centos 8) to develop a system that will use an application using REACT as a front end to show data from different sensors. I will use NGINX as a webserver and Node-red as a back end. In this first post I describe how to install NGINX.
Install nginx package using the yum command on CentOS 8:
sudo yum update
sudo yum install nginx
Update firewall settings and open TCP port 80 and 443. Run:
sudo firewall-cmd –permanent –zone=public –add-service=https –add-service=http
sudo firewall-cmd –reload
Enable nginx service by running systemctl command so that it starts at server boot time:
sudo systemctl enable nginx
start the service, run:
sudo systemctl start nginx
Commands to start/stop/restart nginx server
Run command as per your needs.
sudo systemctl start nginx <– start the server ##
sudo systemctl stop nginx <– stop the server ##
sudo systemctl restart nginx <– restart the server ##
sudo systemctl reload nginx <– reload the server ##
sudo systemctl status nginx <– get status of the server ##
You must open and enable port 80 and 443 using the firewall-cmd command:
sudo firewall-cmd –permanent –zone=public –add-service=http –add-service=https
sudo firewall-cmd –reload
sudo firewall-cmd –list-services –zone=public
Now nginx is installed. Bellow are some important directories (defaults) i
Config directory – /etc/nginx/
Maibn global config file – /etc/nginx/nginx.conf
TCP ports opened by Nginx – 80 (HTTP), 443 (HTTPS)
Default web document root directory – /usr/share/nginx/html
Access log file – /var/log/nginx/access.log
Error log file – /var/log/nginx/error.log
I meet several people when i was in Las Vegas. No one know about my city until i talk about 2014 Soccer World Cup and tell about Germany 7 x 1 Brazil game.
The video bellow, show another face of the city.
You can enable Cross Origin Resource Sharing (CORS) for your web applications on a Liberty server.
Enabling CORS will allow JavaScript clients to make requests against your application on the Liberty server even if the client and the server are on two different domains. Web browsers prevent these requests due to same-origin policy.
I create the following configuration on my local machine on server.xml file:
<cors domain="/ApplicationContext" <-- application context. It will work only for this app.
allowedOrigins="http://localhost:8080" <-- this is my local Node.js Server.
allowedMethods="GET, HEAD, POST, PUT"
allowedHeaders="Referer, Cache-Control, Pragma, Accept, Accept-Language, Accept-Encoding, Accept-Charset, Content-Type, Content-Length, User-Agent, Authorization, passwd, X-Update-Nonce, X-Shindig-ST, X-IC-CRE-Request-Origin, X-IC-CRE-User, X-LConn-Auth, Accept*, Content*, Access-Control-Allow-Origin*"
exposeHeaders="Content-Type, Last-Modified, etag"
allowCredentials="true" maxAge="3600" />
In a world full of API’s and JSON this is a nice tool.
JSLint is a JavaScript program that looks for problems in JavaScript programs. It is a code quality tool.
Working this week on a new WebSphere Portal Project.
Several content are using AngularJS and some calls to get data go to another server in another domain.
To avoid CORS we implement a reverse proxy on the IHS side.
Bellow the config of my httpd.conf.
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
SSLProxyEngine on
KeyFile /opt/IBM/HTTPServer/bin/key.kdb
SSLStashfile /opt/IBM/HTTPServer/bin/key.sth
Proxypass /acme/products https://anotherdomain/api/v1/products
ProxypassReverse /acme/products https://anotherdomain/api/v1/products
Flash’s death has been slow and painful, and now Google is planning to deal it another blow. Google has detailed plans to start blocking most Flash content with Chrome, with the change targeted toward the end of this year.
Under its current vision, nearly every website would have Flash content blocked by default. Visitors would still be able to enable Flash content on a site-by-site basis, but they would have to specifically choose to do so. Chrome would display a prompt offering to enable Flash; if chosen, Chrome would remember to run Flash on that site for all future visits.
See the full article here
