Installing packages - Revision history

Ziik: Rework Composer

2023-02-23T12:14:03Z

Rework Composer

← Older revision		Revision as of 14:14, 23 February 2023
Line 14:		Line 14:
	The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities.		The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities.

	After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.		After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. You can look at the second step in [[Installing packages#Composer]] for an example on how to make a program accessible everywhere. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.
	===Node.js===		===Node.js===
	We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here].		We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here].
Line 20:		Line 20:
	We do not provide a global installation of Composer to our users because of different version requirements set by different applications which are not compatible with our setup. If you want to run Composer, you can do a manual install of it.		We do not provide a global installation of Composer to our users because of different version requirements set by different applications which are not compatible with our setup. If you want to run Composer, you can do a manual install of it.

	First ~~off~~, ~~access our shell servers over~~ SSH~~. You can refer to [[Accessing shell servers over SSH\|this page]] if you're unsure of how to do so.~~		First, log in on SSH and then follow these steps to install Composer:
	~~Once you're logged in,~~ follow these steps to install Composer ~~to the current directory~~:		# Follow [https://getcomposer.org/download/ the manual steps] from "Command-line installation" to "php.ini" (the white code block).
	# ~~Download the installer script: type <code>php -r "copy('~~https://getcomposer.org/~~installer', 'composer~~-~~setup~~.~~php');~~"</code~~> in the command line and press Enter~~.		# Type: <code>mkdir -p ~/.local/bin && mv composer.phar ~/.local/bin && echo 'export PATH=$PATH:~/.local/bin' >> ~/.bashrc</code> and press Enter.
	# ~~Run the installer script~~: ~~type~~ <code>~~php~~ composer~~-setup~~.~~php~~</code> and press Enter.		You can now run <code>composer.phar</code> from anywhere.
	~~# Composer is now installed.~~ You can ~~remove the installer by typing~~ <code>rm composer~~-setup~~.~~php~~</code> ~~and pressing Enter~~.

	~~You can now run Composer by typing <code>php composer.phar</code> in the directory where you installed it and pressing Enter.~~
	[[Category:Shell]]		[[Category:Shell]]

Ziik: Add composer install guide

2023-02-22T22:30:00Z

Add composer install guide

← Older revision		Revision as of 00:30, 23 February 2023
Line 15:		Line 15:

	After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.		After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.
	== Node.js ==		===Node.js===
	We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here].		We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here].
			===Composer===
			We do not provide a global installation of Composer to our users because of different version requirements set by different applications which are not compatible with our setup. If you want to run Composer, you can do a manual install of it.

			First off, access our shell servers over SSH. You can refer to [[Accessing shell servers over SSH\|this page]] if you're unsure of how to do so.
			Once you're logged in, follow these steps to install Composer to the current directory:
			# Download the installer script: type <code>php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"</code> in the command line and press Enter.
			# Run the installer script: type <code>php composer-setup.php</code> and press Enter.
			# Composer is now installed. You can remove the installer by typing <code>rm composer-setup.php</code> and pressing Enter.

			You can now run Composer by typing <code>php composer.phar</code> in the directory where you installed it and pressing Enter.
	[[Category:Shell]]		[[Category:Shell]]

Bert at 11:14, 15 May 2020

2020-05-15T11:14:55Z

← Older revision		Revision as of 13:14, 15 May 2020
Line 16:		Line 16:
	After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.		After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.
	== Node.js ==		== Node.js ==
	We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/~~creationix~~/nvm#~~installation~~ here].		We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here].

	[[Category:Shell]]		[[Category:Shell]]

Bert at 19:09, 4 November 2019

2019-11-04T19:09:22Z

← Older revision		Revision as of 21:09, 4 November 2019
Line 1:		Line 1:
	While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course ~~also~~ limits to what is realistic for us to install. More on that below.		While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course limits to what is realistic for us to install. More on that below.

	== Using a programming language, library or tool that is not installed ==		== Using a programming language, library or tool that is not installed ==

Bert at 15:22, 28 August 2019

2019-08-28T15:22:21Z

← Older revision		Revision as of 17:22, 28 August 2019
Line 17:		Line 17:
	== Node.js ==		== Node.js ==
	We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/creationix/nvm#installation here].		We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/creationix/nvm#installation here].

			[[Category:Shell]]

Principis: Added Node.js paragraph

2018-12-23T17:51:27Z

Added Node.js paragraph

← Older revision		Revision as of 19:51, 23 December 2018
Line 15:		Line 15:

	After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.		After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.
			== Node.js ==
			We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/creationix/nvm#installation here].

Bert at 14:19, 21 January 2018

2018-01-21T14:19:51Z

← Older revision		Revision as of 16:19, 21 January 2018
Line 12:		Line 12:
	It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well.		It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well.

	The way you install your software ~~rewall~~ differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities.		The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities.

	After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.		After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.

Bert at 03:09, 21 January 2018

2018-01-21T03:09:47Z

← Older revision		Revision as of 05:09, 21 January 2018
Line 2:		Line 2:

	== Using a programming language, library or tool that is not installed ==		== Using a programming language, library or tool that is not installed ==
	If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation\|Manual installation]]		If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation\|Manual installation]].

	== Using a newer/different version ==		== Using a newer/different version ==
			As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation\|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation.

			== Manual installation ==
			If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account.

			It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well.

			The way you install your software rewall differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities.

	~~== Manual installation ==~~		After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location.

Bert at 02:58, 21 January 2018

2018-01-21T02:58:31Z

← Older revision		Revision as of 04:58, 21 January 2018
Line 2:		Line 2:

	== Using a programming language, library or tool that is not installed ==		== Using a programming language, library or tool that is not installed ==
	If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to [[https://packages.ubuntu.com/]] to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation\|Manual installation]]		If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation\|Manual installation]]

	== Using a newer/different version ==		== Using a newer/different version ==

Bert at 02:58, 21 January 2018

2018-01-21T02:58:17Z

← Older revision		Revision as of 04:58, 21 January 2018
Line 1:		Line 1:
	== ~~I want to use~~ a programming language, library or tool that is not installed ==		While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course also limits to what is realistic for us to install. More on that below.

			== Using a programming language, library or tool that is not installed ==
			If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to [[https://packages.ubuntu.com/]] to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation\|Manual installation]]

			== Using a newer/different version ==


			== Manual installation ==