ULYSSIS documentation - User contributions [en]

Setting up WordPress

2023-09-28T06:59:17Z

Ziik: /* Finishing up installation */

This page will go through a basic setup of WordPress, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS.

==Putting setup-files in place==

First you need to download WordPress from their website, https://wordpress.org/download/. After you've
received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>.

Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP.
If you need further instructions, you can find detailed instructions on: [[Accessing your files]].

== Setting up a database ==
Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br>
'''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases.

== Installing WordPress ==
Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username).
This is where you have to set up your website. The easiest way to do this, is by following the wizard.

The setup will ask you for your database configuration:
*'''Database Name/Databasenaam:''' the name of the MySQL database
*'''Username/Gebruikersnaam:''' your username
*'''Password/Wachtwoord:''' your MySQL database password
*'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code>
*'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br>
So it will look something like this:<br>
[[File:wordpress_screenshot.png|thumb|left|600px]]
In the next step you need to fill in your own preferences.

== Finishing up installation ==
Finally you will be prompted to log into your WordPress website. Now the installation is finished.

{{info|We advise all WordPress users to enable automatic updates for their plugins, themes and WordPress itself. You can find detailed instructions on [[Updating WordPress]].}}

To help you design your website, there are a few guides from WordPress that can help you:
*https://wordpress.org/support/article/first-steps-with-wordpress-b/
*https://wordpress.org/support/article/using-themes/#get-new-themes
*https://wordpress.org/support/article/managing-plugins/

==Setting up multiple instances of WordPress==

If you want to have multiple instances of a WordPress site, you need to create a new folder in
your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this.

After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above.

You can also use WordPress' [https://wordpress.org/support/article/create-a-network/ multisite] option.
If you need more help with this, you can find it [https://wordpress.org/support/forum/multisite here].

[[Category:CMSs]]

Installing packages

2023-02-23T12:14:03Z

Ziik: Rework Composer

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 ==
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 ==
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 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. 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===
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, log in on SSH and then follow these steps to install Composer:
# Follow [https://getcomposer.org/download/ the manual steps] from "Command-line installation" to "php.ini" (the white code block).
# Type: <code>mkdir -p ~/.local/bin && mv composer.phar ~/.local/bin && echo 'export PATH=$PATH:~/.local/bin' >> ~/.bashrc</code> and press Enter.
You can now run <code>composer.phar</code> from anywhere.

[[Category:Shell]]

Installing packages

2023-02-22T22:30:00Z

Ziik: Add composer install guide

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 ==
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 ==
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 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.
===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].
===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]]