How to build with electron-forge with no internet (airgap) - electron

Environment: electron 17.2.0, electron-forge 6.0.0-beta.63 on Ubuntu 20.04
I am developing a simple electron app on an Ubuntu VM. I now need to move the VM to an air-gapped environment (no Internet).
I have all my Node packages downloaded on the VM and the electron pre-built binaries are available in ~/.cache/electron.
How do I get the 'electron-forge make' command to use the cached pre-built binaries rather than trying to call out to GitHub?

Related

How to run Github Desktop on Manjaro

I am new to Manjaro and Linux in general. I downloaded the AppImage from the github repsitory: https://github.com/shiftkey/desktop/releases/tag/release-2.9.14-linux2 and set the properties to be able to run as program. How can i start Github Desktop from the terminal now? What is the recommended folder to store .AppImage files in my system?
Update: I enabled AUR download, downloaded the Github Desktop from AUR.
To run the application from the terminal you have to type github-desktop

I am a newbie to Docker. I want to install .net Framework4.7.1 developer offline pack in windows server core2019 Through DOCKER as a windows container

I want to install .netframework 4.7.1 Developer offline pack in windows server core 2019 through docker and run it in a windows container. I have tried this command but no use in my Dockefile by copying it from my local directory to container.
**RUN start /w .\dotnet-framework-installer.exe /q **
I have downloaded .net framework dev pack from this site (https://dotnet.microsoft.com/en-us/download/dotnet-framework/net471)
I want to know which command to use in Dockerfile, so it can install in a container.
I have found the solution. You can find the dockerfile to install a developer pack offline mode in below git hub repo https://github.com/hrushikesh2000/Docker_Dev_pack-insta-.git.

Use a Docker container as an install set

I'm currently building a Docker container that contains all the libraries needed for deployment of our app on a test machine, such as, for example, OpenCV 3.3 built with CUDA 9.
So, on a clean minimal OS install we can download the container and fire up our app in the desired environment, which is as I understand it one of the main reasons to use Docker.
So, after a while we decide to do our tests on the bare metal without the Docker file system, etc, in the way. Can we somehow replay the Dockerfile commands or image command history to run the apt-get, etc of not just the current package, but all FROM packages that are not yet installed on the raw environment?

Docker for linux is giving error

I am new learner for Docker.I have a very simple question.
I want my application to work on Linux system but I am writing application in Windows.So do I need to install Docker for Windows or Linux?
If I run using Docker for Linux,i am not getting option to run in windows and it is getting failed(I understand it might be some other unrelated error) but I need to confirm if my approach is correct or not.
Am I right in installing Docker for Linux?
Also,in case I plan to move to AWS, what docker I need in that case.
Thanks
Consider docker as any software. if your OS is windows you install windows version of a software. if your is a linux distro then you install linux version of a software.
So you need to install docker for windows afterwards you can install any docker image/container you want under your operating system. Could be windows, linux or anything else.

Installing Mosquitto with Busybox

I'm trying to put a Mosquitto client onto a small monitoring server that uses busybox on a linux machine. I've unzipped the mosquitto tar file. But because I only have busybox I don't have apt-get, aptitude, make, cmake, dbuild, makepkg, pacman to finish the install.
Any ideas?
Assuming that it doesn't have some other package management system (and a mosquitto package) then the usual solution to problems like this is to compile mosquitto on a different machine with all the required tools then just copy the binaries only.
You've not said what architecture the target machine is but you normally don't even need it to be the same as the build machine as you can cross-compile binaries for different platforms.

Resources