I have an app in which I want to have a complete custom installer. I've looked at NSIS, Squirrel, WiX etc. But I want something fully customizable comparable with the Microsoft Teams and Discord clients.
My first idea was to separate the installer and the application so by downloading the installer and running it, a "oneclick installer" will silently install and look for updates with the autoUpdater, install the real client and remove the installed installer files, but I see a couple of problems here though: I want the user to be able to choose install directory, which I cannot figure out if that is possible through electron and the "autoUpdater" alone.
If NSIS or other can be made completely custom, please inform me because I cannot find anything about it that is of interest.
Related
Trying to delve into Node.js terminology and functionality. Been consulting the following MVC example https://www.sitepoint.com/node-js-mvc-application/ that also has its GitHub repository https://github.com/sitepoint-editors/notes-board. However, when I build the app with all npm installed packages, except sqlite3 (I installed version 5), app is irresponsive in case there is a need to write to sqlite db, however it is able to read and delete any queries, but when there is a need to publish, it simply does not show any reactions. I am banging my head for a while now, so is there any advice or instruction out there what to do....
I have a simple CLI application written in Javascript using Node that is for internal use by a small team. It runs in the Linux terminal as a CLI app. The app consists of a single ".js" file and requires a few Node packages. The problem I face now is how to deploy it to our internal team using a simple method that fits with our routine process of keeping end user computers updated.
Our app needs to be installed once per workstation / laptop and to be available to all users on that computer. Any user should be able to open a terminal and enter the command to run the app.
It seems a lot of people have discussed using Javascript for shell programming, but this issue of deploying the completed app is not widely discussed. I have not found anything on the topic. So far I have been recommended solutions that are appropriate for either development environments or web servers.
This app is not a web app and it is not deployed on a server. It needs to run offline. I am also not asking about developing or maintaining the app on a development workstation.
The installation process should ideally be as about simple as installing a shell script in /usr/local/bin and setting permissions so all permitted users on a computer can run it. We are looking for an installation method like this:
copy the Javascript file only once to each computer (to a location on the $PATH) and make sure the Node packages are available globally on that computer.
I specifically want to avoid having to do an npm install for each user account on each computer.
I also want to avoid having to update Node packages for each user account on each computer.
A developer will keep the app updated so it is always compatible with the latest version of the Node packages, and all computers it is deployed on will always have the latest versions of those packages installed.
One specific problem I encountered is discussed here, but the answers assume a different set of requirements (such as the need for "multiple applications running on different package versions").
For those requirements, if the actual problem is solving the EACCESS error (you should edit the question to include that information), then you should look at the permissions of all directories, and make sure that the user account that manages node packages on each computer has correct permissions.
One way to do that is to give /usr/local a special group, set the sticky bit with chmod (see man chmod), and use chgrp -R on the existing tree.
Then make the installing account a member of that group, and don't use sudo for npm install -g.
(Never using sudo for installations into /usr/local has the additional advantage that you can't accidentally install something somewhere else, for example because you didn't set paths in this local package source correctly.)
We are using these two approaches for similar deployments:
the programs live on a specific network mount. All users can run the same package from there. The developer only updates this package. No copying to local machines.
we use a simple deployment script which runs on all machines on logon. It pushes and copies the latest version to the local machine.
I want deploy a Meteor application on a wago industrial PLC 750-8202.
Wago supports Boards Support Package with the PTXdist tooling support (Communicate with CoDeSys program on a Linux-based WAGO PFC200 PLC).
I have no idea how i can utilize meteor on such a platform.
Have you any ideas how the steps can be realized to add meteor support for wago plcs ?
It is has linux on it, just SSH to your PLC. Make sure it is connected to your local network.
Now you can install node and everything else. It is like you have your own VPS. Configure everything. You can even install ftp server and upload your files over FTP. Or create small script that will be triggered from Github hooks and update your PLC as soon as you push changes to master branch.
We have an application which installs to a custom folder and now we have to create an installer for an application extension (plugin).
The installer of the host application was created with a cross-platform tool, which permits the user to choose the installation folder and even it permits to install multiple versions on the same system.
The host application is not just an "app", as in case of many Mac programs, but a directory which contains several files + an "app".
The plugin installer should:
1. be pkgbuild/productbuild based, because we doesn't want to use cross-platform installer because it is Java based and we had troubles with it
2. query all installed host applications with CFBundleIdentifier and choose one to install
3. install the content of the payload to the directory of the chosen host application
I managed to find solutions for the first two requirements, but I don't know how to proceed with the third.
Is there any solution to change the installation path from the Distribution.xml?
I played with choice.customLocation attribute, but I didn't managed to modify from JavaScript.
Is there any "elegant" solution for it?
Thanks.
I currently have the latest version of Eclipse (Juno) and I have installed ADT with no problem. I have moved on to a web based project and I require support for JavaScript and HTML etc. I installed WTP through the update manager and you can see that all of the required packages appear to be installed:
However, within Eclipse there is very little evidence that anything has been installed. I have read in this jsdt tutorial that I should be able to create web projects such as "Static Web Project" and have text editting support for HTML and JavaScript. However, I see no web project options, HTML or JavaScript file options, no perspective options for HTML or JavaScript, and no support for editing html/javascript files.
Here you can see an html file I attempted to create. Notice the lack of syntax colouring:
Here you can also see all the project creation options that are available to me:
So how should I have installed WTP? Should I not have installed it thought Eclipse's software manager? I would like to do this without having to re-install Eclipse if possible.
This problem seems to exclusively occur in Windows 7. I managed to successfully install the desired software by right clicking on the Eclipse icon, selecting "Run As Administrator" and then re-installing all packages. I did not have to do this in Windows Vista.
If you are experiencing this problem and you are using Windows then follow these steps.
Right click on the Eclipse icon and select Run As Administrator.
Once you have opened your Workspace go to Help -> Install New Software.
Any installed packages that you installed when you did not Run As Administrator should now not appear to be installed. So install them again.
Restart eclipse (normally if you wish) and your desired packages should be installed correctly.