I looked at the package center in the synology OS but only the Magento version is available at the package center. I've searched for answers online but can't seem to find the right one.
The easiest way to install packages is to browse Package Center, which displays a list of approved packages compatible with your Synology NAS model.
Some third-party developers make it simple to check for available applications by creating an .spk repository.
When you want to install a specific version of an application, or when Internet access is not available for automatic download of application files, you can install applications on Synology NAS using .spk files saved on a local computer. Package .spk files are available at Synology's Download Center
https://www.synology.com/en-us/support/download
Related
I am curious to know if there are methods where I can add additional packages to the anaconda installer. I am basically looking for a solution for creating an anaconda installer which has some extra python packages added along with it. Thus the participants to whom I give the installer need not be worrying about Internet connectivity or to add additional commands.
This is meant for an introductory hands-on python session. Hence the objective is to make the whole installation process less confusing as possible to the participants of the session.
I am aware of using docker as well as using environments. I am looking for something more simpler, say as seamless as anaconda installation for my participants.
Currently, I am thinking of doing the following.
1) Provide the .tar.gz file of the packages along with the installer
2) After installation and creating environments, install the libraries using pip from the .tar.gz
python -m pip install c:\mymodule\great.tar.gz
Any method which is simpler than the above one is welcome.
From the conda documentation on creating custom channels:
If you do not wish to upload your packages to the Internet, you can
build a custom repository served either through a web server or
locally using a file:// URL.
The instructions on that page tell you how to create a local custom repository from conda packages. They're aimed at people who are building their own packages but as far as I can see you can also use the existing packages that you can download from the repositories at https://repo.continuum.io/pkgs/.
You can then use the file:// URL of that repository in the -c specification of conda create and/or conda install commands to set up the environment for your users to work in.
I need to install software on Windows clients that are completely offline. That means they have no Internet access.
An example. Let's say I want to install Paint.Net. I go to a reference machine (with INet) and install Paint.Net with Chocolatey.
choco install paint.net -y
After the install is finished I have the software installed and two artifacts:
The package file "paint.net.nupkg" in %ChocolateyInstall%/lib/paint.net
and
the the installer file "paint.net.4.0.6.install.zip" in %Temp%\chocolatey.
I now put these two files on a USB stick. Then I go to the offline machine, plug in the USB stick and want to install the package.
Is it possible to install the software without modifying the package? I am aware that inside the nupkg file there is a tools/chocolateyInstall.ps1 file with a $url variable defined. But I want to install the package without changing the package content or modifying the URL by hand.
I played around with the parameters --cache and --source but with little to no luck.
I have seen that this kind of question is asked before. But never (to my knowledge) with the intend to run the installer file from the stick too (and not only the package file). So I hope this is not a duplicate.
Caching Downloads - Not Deterministic
While there are ways to set the original nupkg (with the version on it, not the one in the packages directory - use download from left side of package's page on the Chocolatey community package repository) and the cache onto a USB stick somewhere, it's not always deterministic that it will work. You can also override the cache location, so that the folder is somewhere not in TEMP. See choco config, choco config -h and choco config set cacheLocation c:\some\location to do this.
Create Your Own Packages - Better
For packages you need offline, you have the ability to manage your own packages and you can embed software right into the package. This is desired when you want to manage software offline as most things on the community repository are subject to copyright law and distribution rights (why they don't simply have the software they represent embedded).
Creating and working with your own packages is very secure, reliable, and repeatable (and can be completely offline), but it does tend to take up time. If you are doing this for yourself, then it could override any time-savings you get as a consumer using Chocolatey and the community repository.
Internalized Packages - Best
The best thing you can do here is a process called internalizing, where you download and extract the package, download all of the resources and embed them in the package (or put them somewhere local/UNC share), edit the scripts to use those embedded/local resources and recompile the package.
This allows you to take advantage of existing package logic without the issue of the internet.
For more details see Recompiling Packages and Package Internalizer - Automatically Recompile Packages.
NOTE: As a side note, we are thinking of offering the ability to auto recompile with Chocolatey Pro edition and not just the Business edition.
Organization Use of Chocolatey
Most organizations using Chocolatey are doing some combination of creating packages and recompiling packages, because they need absolute trust and control over those packages when being used in production scenarios.
I'm stucked with installation of CCRCCLI on the Windows machine. I read this question, but it still not clear for me.
IBM's installation manual requires setting up variable CCSHARED to the directory of Shared Resources, which can be found in IBM Installation Manager. But I installed CCRC directly from ClearCase server and I had no IBM Installation Manager installed, so I don't know how to find Shared Resources Directory. Later I installed Installation Manager, but it didn't show me any IBM products installed (as expected).
I try to point CCSHARED to plugins subdirectory of CCRC, but it seems to be incorrect.
What it Shared Resources Directory and how to find it on my computer?
Later I installed Installation Manager
It is best to uninstall any IBM-ClearCase related product first, then install the IM (Installation Manager, most recent as possible 1.8.1+), then use it to install other Rational projets.
The CCRC CLI (the tool that provides a command-line interface for ClearCase® Remote Client (CCRC) users to perform commonly used ClearCase® operations over a WAN) needs:
the CCRC
Java Runtime Environment (JRE)
Version 1.5 (Java 5) for CCRC CLI V 7.1.x.
Version 1.6 (Java 6) for CCRC CLI V 8.0.
the right compatibility between CCRC CLI and the CM Server.
system requirements similar to the ones for CCRC.
If CCRCCLI needs Shared Folder, said folder is usually called IBMIMShared, at the same level as other IBM products (you can see path examples in this technote).
It acts essentially as an Eclipse p2 repository, with its artifacts.xml file, plugins/ and features/ folders. Installing IM is a good way to create that folder.
However, that Shared Folder won't reference the existing CCRC already installed (hence my initial advice).
I have an installer implemented with "Packages" which contains the payload and after running some plugins and a post install script it successfully installs the product.
The same package bundle is used for making updates too, as we run it in background with root privileges and it overwrites the current/old installation files.
We now have the requirement to make a lightweight installer having the components (different Packages inside the product) in a web location to be downloaded and installed.
As I know that this is possible in other systems as Windows/InstallShield with "Releases of Web Type", I would like to know if this is possible in OS X. Otherwise, I will have implement it all from scratch (packages management, download, packages versions compare to make selective updates, privileges escalation, etc).
Well, it was long ago and I almost started doing a web installer from scratch but then I found out that the option is in Packages itself. Hope this helps.
It is the "Package Reference" option.
According to the Packages documentation
A Package Reference lets you use a package that is hosted on a web
server or a removable media and to which you may not have a direct
access. This package will not be built during the built phase.
I think that any referenced package will have its own pre-post-scripts so there would be no problem because of the limited options in the Package Reference. But I need to test it.
I don't know how to install Joomla 1.7.3 and it's hard to know from joomla web page. Can anybody tell me how to install joomla 1.7.3 step-by-step.
Thank you
There's an old guide here, although it still mostly applies:
http://help.joomla.org/content/category/15/99/132/
In short: Create a database, Upload the Joomla files, follow the installer. In more detail:
Make sure you meet the system requirements:
http://www.joomla.org/technical-requirements.html
Create a MySQL database (note down the name, username, and password to access it)
Get the Joomla files from here:
http://www.joomla.org/download.html
Upload all the files from that package to your hosting
Browse to your site - the Joomla installer will automatically run. There's a guide for the steps here:
http://docs.joomla.org/Installer
Follow the instructions and fill in the boxes in the Joomla installer.
Once the installation is complete, delete the 'installation' folder (the installer will tell you to do this).
You now have Joomla :)
Have you checked this page? http://docs.joomla.org/Installation
It provides a step by step installation guide, I think it's quite easy to install Joomla. Generally talking, all you have to do is:
Download the latest Joomla version ( I guess you already did this )
Unzip the downloaded file, then copy it into your webroot ( if you have multiple sites, you should create a folder within your webroot dir and copy the files there )
Access via your browser your web dir, and installation process will start.
It's important that you check that your Apache user is able to read and write your Joomla files. If you're using virtual hosts, you should also create and configure the new virtual host.