Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
netFIELD Compact Gateway ...
Forum: Hardware
Last Post: DSongra
February-27th-2023, 08:38 AM
» Replies: 10
» Views: 3,225
|
Forum is becoming read-on...
Forum: News
Last Post: Armin@netPI
February-19th-2023, 05:04 PM
» Replies: 0
» Views: 1,210
|
NIOT-E-NPIX-RS485
Forum: Software
Last Post: Armin@netPI
January-21st-2023, 05:20 PM
» Replies: 6
» Views: 4,391
|
netPI device series is di...
Forum: News
Last Post: Armin@netPI
January-21st-2023, 08:34 AM
» Replies: 0
» Views: 848
|
Forum "netHAT" is being c...
Forum: News
Last Post: Armin@netPI
December-21st-2022, 01:17 PM
» Replies: 0
» Views: 909
|
netFIELD Compact Gateway ...
Forum: Software
Last Post: Armin@netPI
December-20th-2022, 10:34 AM
» Replies: 1
» Views: 3,268
|
netPI not found in networ...
Forum: Hardware
Last Post: Armin@netPI
December-13th-2022, 11:40 PM
» Replies: 1
» Views: 3,421
|
Proxy Settings
Forum: Software
Last Post: Armin@netPI
December-5th-2022, 06:21 PM
» Replies: 9
» Views: 7,040
|
Node Red configuration
Forum: Software
Last Post: Armin@netPI
November-30th-2022, 05:14 PM
» Replies: 3
» Views: 1,761
|
443 port issue
Forum: Software
Last Post: LucioFiam
November-21st-2022, 05:39 PM
» Replies: 5
» Views: 2,272
|
|
|
Multi-stage builds for slim container images |
Posted by: Armin@netPI - February-7th-2019, 04:14 PM - Forum: Software
- No Replies
|
|
These days it was time to think about Docker's multi-stage build feature and to provide an example of how it works.
Multi-stage builds are always then of any interest if applications need to be compiled first before getting them to an executeable state and as such be installed in the final container image ... but without all the necessary development tools, environments and compilers. This keeps the image small and away from all unnecessary data needed during compilation times only.
We found that the bluetooth registry on DockerHub would be best for a demonstration. Its Dockerfile contains two FROM commands the build process turns into two separate builds. Build STEP 1 creates a temporary container and compiles the bluetooth stack ... Build STEP 2 builds the final output container that is just copying the required outputs files of STEP 1.
Happy testing
Armin
|
|
|
Proxy Settings |
Posted by: Motzi - February-7th-2019, 12:05 PM - Forum: Software
- Replies (9)
|
|
We want to use the netPI in a network that uses proxy to connect to the internet.
Unfortunately I can't see any options where I can set the proxy settings.
Is there any way to setup the proxy connection?
Kind regards
Julian
|
|
|
[INFO] CODESYS V3.5.14.0 compatibility confirmed |
Posted by: Armin@netPI - February-6th-2019, 01:20 PM - Forum: Software
- No Replies
|
|
End of the year 2018 company 3S released a new Service Pack Version SP14 of CODESYS Control V3.5.
We checked the netPI compatibility to this version and can confirm netPI's compatibility to this version.
Follow the README instuctions in the Repository and you will be fine.
|
|
|
[INFO] TeamViewer comes to netPI |
Posted by: Armin@netPI - February-4th-2019, 04:41 PM - Forum: Software
- No Replies
|
|
Many of you know TeamViewer as remote support tool transmitting the screen of a remotely installed device to a local display over the Internet.
An Internet server between TeamViewer Host installed on the device and the TeamViewer Client as management console negotiates the traffic.
Today we released a TeamViewer example container that allows controlling a root login console session within the containers context.
Now it is easier than ever to log on to a remotely installed container application and manage and control it from outside.
The Docker Example container can be found here
The Build Script for the container can be found here
Please take a notice of TeamViewer's End User License Agreement Using it commercially is not for free.
Thx
Armin
|
|
|
System software V1.1.5.0 out now! |
Posted by: Armin@netPI - January-30th-2019, 10:34 AM - Forum: News
- No Replies
|
|
In the today's netPI system software release V1.1.5.0 we realized the following change:
- Possibility to shift away netPI's occupied HTTP/S ports 80 and 443 to any other port. This allows containers to take over those ports for own web applications listening on port 80/443.
By default netPI includes a port forwarding from port HTTP 80 to port HTTPS 443 to ensure any connection goes across a secure connection. For example if you enter netPI's plain IP address in your browser like 192.168.0.1 you will be forwared to https://192.168.0.1 (:443) automatically. Now, if you change the default port HTTP 80 to any other port in version 1.1.5.0 the port forwarding is getting deactivated. In this case the only valid address to access/reach your netPI is entering the HTTPS + IP ADDRESS + PORT e.g. https://<NETPI IP ADDRESS>:<YOUR PORT>. Neither addresses like <NETPI IP ADDRESS> nor a https://<NETPI IP ADDRESS> will work.
Thx
Armin
|
|
|
|