3 ms·
Because I can install nextcloud in a single cli line. With out it I need about 9 scripts worth of stuff (example of what I wrote to do it) https://github.com/O
by ohiovr 9y ago
Because I can install nextcloud in a single cli line. With out it I need about 9 scripts worth of stuff (example of what I wrote to do it) https://github.com/OhioVR/nextcloud_debian_install_scripts/tree/master/installation%20bash%20scripts https://github.com/OhioVR/nextcloud_debian_install_scripts/t...
If you want to learn a whole software stack, building and administration to just TRY a program ONCE I won't stop you. But there are better ways like using docker.
- zeta0134 9y agoI use docker for my build system for this very reason, as my chain depends on a difficult to install Autodesk SDK, which requires a very specific version of Python. I don't expect it to work properly on most modern Linux distributions without virtualenv and other advanced trickery, and there's not even a chance on Windows. With Docker though, once I had the environment set up, unfamiliar newcomers on the three major platforms can then compile and run the project with minimal fuss. (Of course, in the future I'll be working to remove that odd dependency entirely, but for now, this works.) It helps that in my particular case, the build _target_ is an embedded platform, so I don't need to worry about native details in the final executable; hiding the environmental details in the container doesn't matter all that much.
- xtrapolate 8y agoI'd personally just prepare a small VirtualBox image with everything required to build the code, and release that instead.
- azernik 9y agoMe too - though for me the installation tools are fairly standard (SBT + npm), it's still like 10-ish steps. Docker's basically a vehicle for safely running apt-get in a script on all my developers' machines.