This guide is intended for developers who wish to use the ORM Propel on a hosting environment where command-line access is restricted.

Preamble

• The ORM allows linking application objects to database tables. Data is manipulated via PHP objects rather than writing raw SQL.
• Propel is the abstraction layer that manages these interactions (relations, joins, pagination) to simplify code maintenance.

Particularities & limitations

• Propel is not pre-installed via Pear.
  • You must install it manually in your project.
  • It is imperative to download the "Conventional Package" version of Propel.
• CLI commands (such as propel-gen) are not executable on the server.
  • Consequently, Propel is only used in "Runtime" mode in production. Class generation (build) must be performed locally.
  • The workflow involves generating code in a development environment and then transferring the resulting files to the server.
• Dependencies:
  • The complete set of libraries required for Propel is available, except for Phing.
  • The absence of Phing does not impact production, as this tool is only required during the local generation phase.

This guide is intended for users who have chosen Infomaniak, a hosting provider committed to the planet: you will find below the details of the calculation method used to display CO2 on invoices, as well as tips to reduce your own digital footprint.

Preamble

• For Web hosting and Mail services, Infomaniak displays the amount of CO2 emitted annually, data that is based on a rigorous Life Cycle Analysis (LCA) method that adds two key factors:
  1. Material impact (Full life cycle)
     • Thanks to the emission factors of the ResilioDB database, the calculation includes the emissions generated during the manufacturing (BLD), transport (DIS) and end-of-life/recycling (EOL) of each piece of equipment (servers, RAM, disks, etc.).
  2. Energy impact (Actual consumption)
     • The actual electrical consumption of the servers is measured via IPMI probes.
     • This energy is then converted into CO2 equivalent according to Infomaniak's specific energy mix, which is very low in carbon (11.77g CO2eq/kWh).
• The total impact is then distributed according to the unit of use of the customers (per hosted website or per mailbox).

How can you act at your level?

If the hosting provider optimizes its infrastructures upstream, the end user also plays a key role. Here's how to reduce the footprint of your services.

For Websites

The goal is to minimize the energy consumption of servers and visitors' terminals:

• Technical optimization: Compress images, minify scripts, and use modern formats (WebP).
• Clean design: Limit autoplay videos, ads, and heavy scripts that consume bandwidth.
• Best practices: For WordPress in particular, it is recommended to consult the GreenIT sheets.

For Messaging

Email communication can also be optimized:

• Sobriety: Prefer plain text emails over HTML and limit heavy graphical signatures.
• Attachments: Prefer sending download links (via kDrive or SwissTransfer) to large attachments, or use the compressed PDF format.
• Cleanup: Unsubscribe from unnecessary newsletters and use tracking tools to avoid sending unopened emails.

It is recommended to regularly monitor statistics to improve ecological performance. While waiting for Infomaniak's future integrated tools, it is possible to audit the impact of web pages via GreenFrame.io.

Este guia trata da otimização de sites Web e, mais especificamente, do uso de um motor de cache no site.

Introdução

• Quando a Infomaniak constata que o seu site Web consome mais recursos do que outros sites no mesmo servidor, é realizada uma análise.
  • Na maioria das vezes, verifica-se que uma simples modificação de uma consulta ou de um parâmetro permitiria otimizar o seu site e reduzir a carga do servidor.
  • Será então contactado por e-mail com as instruções a seguir, que incluem frequentemente a instalação ou ativação de um motor de cache.
• O consumo de recursos não está necessariamente relacionado com o número de visitantes.
  • Um site bem otimizado, atualizado e com um motor de cache corretamente configurado pode suportar dezenas de milhares de visitantes diários, enquanto um site mal otimizado pode consumir muitos recursos com apenas algumas visitas por dia.
• Um motor de cache armazena temporariamente dados frequentemente utilizados para os fornecer mais rapidamente durante novas solicitações.
  • Isto melhora significativamente a velocidade do site e reduz a carga nas bases de dados ou serviços Web.
  • Para instalar um sistema de cache avançado (Redis, Memcached) no Servidor Cloud da Infomaniak, consulte este guia.

Ativar um motor de cache…

… no WordPress

O WordPress tem muitos plugins de cache. Aqui estão os mais populares e eficazes:

• WP Rocket (pago, a solução "tudo-em-um" mais eficiente e simples).
• WP Super Cache (gratuito, desenvolvido pela Automattic, muito fiável).
• LiteSpeed Cache (gratuito, extremamente completo).

Procedimento de ativação padrão:

1. Inicie sessão na sua administração WordPress.
2. Acesse Extensões > Adicionar.
3. Procure um dos plugins mencionados, instale-o e ative-o.
4. Configure as opções de cache: cache de páginas, minificação de CSS/JS e, principalmente, o Carregamento Preguiçoso (Lazy Load) para as imagens.

Consulte também este outro guia sobre o assunto.

… no Joomla (v4 & v5)

1. Acesse Sistema > Configuração geral.
2. Selecione a guia Sistema.
3. Na seção Configurações de cache, ative o cache (o modo Conservador é o mais seguro para começar).
4. Selecione o gerenciador de cache (Arquivo padrão).
5. Em seguida, vá para Sistema > Plugins e certifique-se de que o plugin Sistema - Cache esteja ativado para armazenar em cache as páginas inteiras.

… no PrestaShop (v1.7 & v8+)

1. Acesse Configurações avançadas > Desempenho.
2. Smarty: marque "Nunca recompilar os arquivos de modelo" (em produção) e ative o "Cache".
3. CCC (Combinar, Comprimir e Armazenar em Cache): ative todas as opções (Cache inteligente de CSS, Cache inteligente de JS, Otimização Apache).
4. Cache: na parte inferior da página, ative "Usar cache". Em uma hospedagem compartilhada, priorize o sistema de arquivos; em um Servidor Cloud, use Memcached.

… no Drupal (v9, v10 & v11)

O cache está integrado nativamente e é muito poderoso no Drupal:

1. Acesse Configuração > Desenvolvimento > Desempenho.
2. Marque "Armazenar em cache as páginas para usuários anônimos".
3. Defina uma duração para "Tempo máximo de expiração do cache no navegador e no proxy" (por exemplo, 10 minutos).
4. Ative a agregação dos arquivos CSS e JavaScript.

… no Contao (v4 & v5)

1. O cache é agora gerenciado principalmente através do arquivo de configuração config/config.yaml ou através da interface de administração em Layout > Temas > Editar o layout da página.
2. Defina um "Tempo de expiração do cache" para a página em questão.
3. Use o Contao Manager para limpar o cache de produção (Symfony Cache) após modificações estruturais.

Verificar a eficácia

Após a ativação, teste seu site com estas ferramentas gratuitas:

• Google PageSpeed Insights
• GTmetrix

This guide explains how to report a phishing attempt that you are a victim of.

Introduction

• Phishing is a fraud and scam attempt aimed at fraudulently obtaining sensitive information.
• Generally, the victim receives a message in their inbox that appears to be from Infomaniak, their bank, or a trusted organization, indicating that a problem has occurred with their account or in their daily life:
  
• The purpose of this identity theft is generally for the user to voluntarily go to a page and provide private information that will then be used for various purposes, mainly financial ones.
• If it is not a message “pretending to be something it is not”, but only an unsolicited advertising message, it is better to report it as Spam.

Reporting a Phishing Email

Prerequisites

• Verify that the spam filter is active.
• For greater security, enable the display of external mail.

Then, if you find an email of this type directly in your inbox, you have the option to take action so that these messages decrease and eventually disappear from the messaging systems:

1. Click here to access the Infomaniak Mail web app (online service at ksuite.infomaniak.com/mail).
2. Open the phishing message.
3. Click on the action menu ⋮ on the right.
4. Click on Report message.
5. From the menu that appears, select Report as phishing:
   
6. Confirm the submission for processing.
7. Delete the email.

Once you have clicked on Report as phishing, an email is automatically sent to Infomaniak with all the information needed to process the scam report.

In the event of a more serious problem (when the message is directly addressed to you by someone you know or a contact, and it is not a mass mailing), it is recommended to contact an organization such as report.ncsc.admin.ch.

This guide explains how to view file activity on your Infomaniak hosting server.

FTP space activity logs

To know the activity of exchanges on your FTP space, contact Infomaniak support to request FTP logs by first authenticating with the credentials corresponding to the management of your web hosting.

Help reading logs: http://www.castaglia.org/proftpd/doc/xferlog.html

The possible indication information_schema does not concern you directly.

It is an internal database of MySQL that is a summary of the information from your own databases.

This guide concerns RTMP (Real-Time Messaging Protocol), a service that allows real-time multimedia content to be streamed over the Internet:

• This is a proprietary protocol developed by Adobe and its use requires the configuration of a dedicated RTMP server or the use of RTMP hosting services.
• Viewers can access the live stream using an RTMP-compatible media player, such as VLC.

By default, RTMP is blocked by Infomaniak security rules.

• Refer to this other guide to open the corresponding port.

This guide is for you if you encounter the error The web host does not exist when visiting the address of a site on an Infomaniak Web Hosting.

Preamble

• This type of error usually occurs because your domain name is not correctly linked to your site (your domain name is probably pointing to the wrong IP address or is misconfigured).
  • Example: a domain abc.xyz that is misconfigured and would point to an IPv4 Starter hosting and to a shared hosting in IPv6…

Resolve a Domain - Website Linking Issue

To get your site back online:

• Check the DNS zone of your domain name, especially its A records.
• Correct them if necessary by entering the IP address of your hosting.
  • Any DNS addition/modification can take up to 48 hours to propagate.

To do this, the easiest way is to use the Infomaniak DNS Diagnostic Tool to automatically correct the pointing, by previously grouping the products in the same Organization if necessary.

This guide explains how to prevent cyber attacks and how to avoid a website hack for the website you manage.

The role of the host

Infomaniak's job is to provide quality hosting, so it is crucial to respond extremely quickly to the various attacks that any Internet actor may be subject to. Infomaniak therefore does everything possible to take the maximum of precautions against hacking, notably by keeping the different versions of the technologies used up to date.

In the event of a proven hack, if it is possible to trace back to the author and the machine has been compromised due to a security flaw on Infomaniak's part, if the integrity of the servers is at stake, Infomaniak takes matters into its own hands.

The role of the site owner and the webmaster

If the hacking of your site is your responsibility (an outdated script, a security patch that has not been applied, etc.), Infomaniak contacts you to warn you of a problem that will need to be resolved quickly. Some organizations like Saferinternet can also suspend the domain name upstream, which will deactivate the site but also the email.

Infomaniak cannot counter exploits related to a bug in your PHP code or other. If the hacking is not detected, you will generally notice the intrusion quite quickly through suspicious elements in your pages or by receiving numerous error emails.

It is therefore your responsibility to take care of the evolution of your website over time and not to let it "die" in a corner, even if it means calling on a webmaster whose job it is.

Infomaniak recommendations

1. Regularly update all your web applications (WordPress, Joomla, Drupal, ownCloud, etc.).
2. Keep the PHP version of your site on Infomaniak servers up to date.
3. Keep your site up to date by migrating to new offers when they are proposed to you.
4. ‍Add a protection system on your contact forms (captcha, etc.) and on any "recommend to a friend" tools (tell-a-friend...).
5. Regularly run an antivirus analysis of the hosting.
6. Monitor the vulnerability detection tool.
7. Remove anything you have not developed yourself and for which the author has not provided an update/correction for several months.
8. Make a regular backup of your site (refer to this other guide if you use WordPress) when everything is fine and keep it safe (as automatic backups are only kept for a few days and this is sometimes not far enough back to go back after you notice an intrusion).
9. Consult ibarry.ch.

If a problem has occurred...

1. Change the passwords of your Web applications, your FTP accounts and your databases by previously checking that no virus is on your computer.
2. Restore a backup but update immediately what can be updated as soon as the restoration is complete.
3. If you encounter a problem with third-party software, contact its publisher or a Partner and refer to the support policy as well as section 11.9 of the Infomaniak Terms of Service.

The CGID module for Apache has been disabled on Infomaniak's shared web hosting offers.

If necessary, you should consider changing your plan to a Cloud Server if you are currently on a shared web hosting plan. This can be done transparently: refer to this other guide on the subject.

This guide concerns YAZ, a software library used to implement the Z39.50 protocol, an information retrieval protocol that enables communication between different library management systems (LMS) such as PMB, widely used in France.

Infomaniak for efficient library management

On Infomaniak's Web Hosting, PMB is supported and YAZ is activated by default.

However, if you encounter errors such as Call to undefined function yaz_connect(), you will need to open ports via the Manager. Port 210 is the standard port used for Z39.50 communications, but do not hesitate to consult the documentation of your applications.

For older Infomaniak hosting plans, consider changing your offer.

This guide explains how to increase the max_children value on Managed Cloud Server to increase the number of simultaneous PHP processes that can be used by your site. This will be very useful for resolving infinite page loading issues on your site.

Preamble

• By default on all hosting, the max_children limit is set to 20.
  • Although it is possible to increase this value from the Infomaniak Manager, the max_children limit is automatically adjusted based on the configuration of your Managed Cloud Server.
  • To increase this limit on shared hosting, migrate to Managed Cloud Server.
• To understand how to calculate the max_children needed as accurately as possible, refer to this article on the subject.

Increase the max_children value

Prerequisites

• Ensure that you have the necessary resources on the Managed Cloud Server.
• Ensure that all resources of the Managed Cloud Server are not being used; if it turns out that they are fully used, increasing the max_children value will have no effect (Modify Managed Cloud Server resources).
• Monitor the resources of your server, in case the resources of your server are reached, it will be necessary to check the optimization of processes and your site before considering increasing the max_children value.
• Consult the PHP error reports from the /ik-logs folder (master process php logs - file name: php-fpm.log) to check if the "max_children" limit has been exceeded... example of error: [05-Jul-2024 09:08:58] WARNING: [pool www.infomaniak.ch] server reached max_children setting (20), consider raising it

To access the management of PHP / Apache parameters of the site for which you need to increase the max_children value on Managed Cloud Server, refer to this other guide.

You will be able to...

• ... choose a new max_children value:
  

Limits depending on the server

Limit of max_children depending on the resources of the Managed Cloud Server:

This guide is for you if you wish to perform vulnerability tests on your site / server hosted by Infomaniak.

Tolerated and restricted

You are free to perform vulnerability tests (SQL injection, XSS, etc.), intrusion, or penetration testing (pentest) on your Infomaniak hosting only under the following conditions:

• ... between 9 AM and 5 PM CET
• ... from Monday to Friday
• ... with the minimum number of attack packets regardless of the software used (AppScan for example)
• ... without ever performing a single DoS or DDoS (Denial of Service) attack
• ... by respecting the Infomaniak Terms of Service, in particular the shared framework of the services

This guide explains how to optimize the caching of web resources using HTTP headers.

Preamble

• A good caching strategy can significantly improve the performance of your site by avoiding the unnecessary retransmission of unchanged files.
• Web caching relies on two complementary mechanisms:
  1. The cache validity period (via the Expires header) which indicates how long a resource can be reused without contacting the server.
  2. Conditional validation (via the Last-Modified/If-Modified-Since headers) which allows checking if a resource has changed before re-downloading it.

Configuring the cache duration with Expires

The Expires header allows specifying a duration during which the browser can directly reuse resources from its local cache. Here is how to configure it in your .htaccess file:

1. Create or open the .htaccess file at the root of your site (usually in /web or /sites/domain.xyz).

2. Add the configuration of the expires module:

   <IfModule mod_expires.c>

3. Define the appropriate cache durations for each type of resource:

   ExpiresActive On
   ExpiresByType text/html "access plus 1 week"
   ExpiresByType image/jpeg "access plus 1 month"
   ExpiresByType text/css "access plus 1 month"
   ExpiresByType application/javascript "access plus 1 month"

   These directives mean that:

   • HTML pages will be cached for one week.
   • JPEG images, CSS files, and JavaScript will be kept for one month.

   Adjust these durations according to the frequency of updates to your resources.

4. Close the configuration section:

   </IfModule>

Conditional validation with Last-Modified

Even when a resource has expired in the cache, it is not always necessary to completely re-download it. The conditional validation mechanism allows the browser to check if its cached version is still up-to-date. This process works as follows:

1. The server automatically sends a Last-Modified header with each resource, indicating its last modification date.
   • Apache handles this natively for static files - no additional configuration is required.

2. When the browser requests the resource again, it sends an If-Modified-Since header containing the date it has in cache:

   GET /resource HTTP/1.1
   Host: www.example.com
   If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT

3. The server compares this date with the actual file modification date:
   • If the file has not changed, it simply returns a 304 Not Modified code, thus saving bandwidth.
   • If the file has been modified, it returns the new version with a 200 OK code.

This guide explains why an FTP account (and most of the time Web Hosting as well) can suddenly become blocked.

Preamble

• Infomaniak uses an antivirus solution on all shared servers to combat the sending of viruses via FTP and scripts.
• The antivirus allows for the detection of:
  • potential FTP account hacks
  • the intentional or unintentional sending of files (WordPress themes, fraudulent modules, etc.) containing malicious code lines or inclusions

Detection of malicious file

The antivirus scans all files sent under 1 MB to prevent any upload of viruses / spam scripts / etc.

If a suspicious element is detected, the FTP account password is automatically changed and the incriminated files on the server are locked (FTPban).

The FTP server then sends the FTP client a message of the type

550 Virus Detected and Removed: botnet.infomaniak.5.UNOFFICIAL

or

550 Virus Detected and Removed: winnow.botnet.ff.trojans.15900.UNOFFICIAL

What to do if the account is blocked?

If your FTP account is suddenly blocked, you will receive an email; follow the procedure indicated in it to unlock the situation. In particular:

• Clean your site and analyze what you wanted to send to the server.
• Check if the web applications and CMS you use are up to date:
  • The cause of most hacks comes from a security deficit in outdated web applications or weak passwords.

Resolve the problem definitively

To prevent your site from being hacked and blocked again, perform the following actions:

• Update the web applications (WordPress, Joomla, etc.) and extensions used.
• Delete unused web applications.
• Change the password for all your FTP accounts.
• Change the passwords to access web applications (WordPress, Joomla, etc.).
• Change the password for MySQL database users.
• Delete MySQL database users that you are not using.
• Use a different, complex password each time, with at least 8 characters.
• Run a manual antivirus scan on your hosting.
• Install and use an up-to-date antivirus (regardless of the operating system).
• Refer to this other guide if you are looking for information on monitoring and resolving vulnerabilities in hosted scripts.

This guide details the use of Perl or Python scripts on Infomaniak hosting and the management of their modules.

Prerequisites

To run Python or Perl scripts via Apache on Cloud Server, the interpretation of files with the extensions .py and .pl is not active by default.

Using your FTP software/client or the Web FTP, add and adapt the following directive in the .htaccess file located in the folder containing your scripts:

AddHandler cgi-script .pl .cgi .py
Options +ExecCGI

Installation of additional modules

On a Cloud Server, you have the possibility to install third-party libraries that are not present by default.

Python

• The installation is done through PIP, which is a package manager used to install and manage packages written in Python.
• Infomaniak offers PIP and PIP3 via the Fast Installer tool.
• Once PIP is installed, you will be able to install Python modules by specifying --user during the command. For example:

• pip3 install mysql-connector-python --user

Perl

• The addition of Perl modules is also done via SSH (console). It is necessary to install them in the user directory and to define the full path within the scripts.

Important technical information

• Interpreter Path: /usr/bin/python
• Extensions: Scripts must have the extension .pl, .cgi or .py.
• Limitations: The mod_python module is not supported.

Error Resolution (CGIWrap)

If you encounter the following error when loading an image:

CGIWrap Error: Execution of this script not permitted
Request Data:Extra Path Info: /dossier/.../image.PL.12.34.gif

The server interprets the file as a script because it contains ".PL" (or .PY) in its name.
Solution: Simply rename the file to remove this mention (example: image-12-34.gif).

This guide explains how to resolve an issue with importing a .csv file into a MySQL table. The proposed alternative is to read the CSV file line by line with PHP and insert the data into the MySQL database.

Disabled “LOAD DATA LOCAL INFILE” function

The LOAD DATA LOCAL INFILE function allows importing a CSV file directly into a MySQL table. However, this feature is often exploited by attackers to gain unauthorized access to sites hosted on servers that accept it.

To prevent any security risks and protect customer data, Infomaniak has disabled the LOAD DATA LOCAL INFILE function. Users who import their CSV files via phpMyAdmin (without checking the “CSV via LOAD DATA” option) are not affected.

Here is an alternative method to import CSV-formatted data into a MySQL table. The example below shows how to properly handle errors when opening the CSV file and inserting data into the database.

This script uses mysqli to connect to the database and prepared statements to insert the data. This ensures better security, optimal compatibility with recent versions of PHP, and simple integration into your project, whether in an existing script or a new file located in the /web directory:

$fileName = "data.csv";

// Connect to MySQL database using mysqli
$link = new mysqli("localhost", "username", "password", "database");

// Check database connection
if ($link->connect_error) {
   die("Connection failed: " . $link->connect_error);
}

// Open the CSV file for reading
if (($handle = fopen($fileName, "r")) !== FALSE) {

   // Read each line of the CSV file
   while (($data = fgetcsv($handle, 1000, ";")) !== FALSE) {

       // Prepare the SQL query dynamically
       $query = "INSERT INTO `test` VALUES (" . str_repeat('?,', count($data) - 1) . "?)";
       $stmt = $link->prepare($query);

       // Check if query preparation was successful
       if ($stmt === FALSE) {
           die("Query preparation failed: " . $link->error);
       }

       // Bind parameters (assuming all columns are strings)
       $types = str_repeat('s', count($data));
       $stmt->bind_param($types, ...$data);

       // Execute the query
       if (!$stmt->execute()) {
           die("Query execution failed: " . $stmt->error);
       }

       // Close the statement
       $stmt->close();
   }

   // Close the CSV file
   fclose($handle);

} else {
   echo "Error: unable to open the file.\n";
   exit(1);
}

// Close the database connection
$link->close();
?>

Get help

Unfortunately, it is not possible to specify exactly where in the script these lines of code should be inserted.

If this method causes issues (for example, when importing multiple CSV files simultaneously without an error message), it is possible that the table structure or field indexing is the cause. In this case, contact your webmaster for verification.

Also refer to the official PHP documentation regarding the fgetcsv() function.

This guide helps you protect the reputation of your domain name, to maintain the trust of Internet users and service providers in your website or business, thereby facilitating the smooth operation of your email.

The web reputation

There are different types of reputation on the Internet, including personal reputation, corporate reputation, and domain reputation.

Domain reputation is essentially a score that determines how email systems decide what to let through to users' inboxes. Fundamentally, the reputation of your domain is a measure of the health and legitimacy of your domain. This reputation can be influenced by the security of your email and website.

For example, the reputation of a domain can decrease if…

• … the site visible at the domain address is hacked, leading to the mass sending of fraudulent emails,
• … the domain's email is exploited for the involuntary sending of spam.

If the reputation of your domain remains poor, your emails may be marked as spam and not reach their intended audience. This can harm email deliverability (see this other guide in English on this topic).

Improving domain reputation

By following these few tips, you can improve the reputation of your domain and, for example, boost all your email marketing efforts:

• Set up and verify SPF, DKIM, and DMARC records that help protect your domain from identity theft attacks.
• Check the reputation of your domain with tools such as Google Postmaster Tools, Sender Score, Microsoft SNDS, McAfee or Talos Intelligence and identify potential issues.
• Only send emails to users who have chosen to subscribe!
• Get trusted links or backlinks…

See this other guide about RBLs.

This guide explains how to obtain the EPP code for your domain name with Hostpoint to transfer it to Infomaniak.

Preamble

• The terms "EPP", "AuthCode", "AuthInfo", "transfer code" and "authorization code" all refer to alphanumeric sequences specific to the domain whose main purpose is to verify the owner's authorization before a transfer between Registrars.
• Refer to the main guide regarding the rest of the transfer procedure.
• ⚠️ This is about transferring a domain name that you own with a different provider than Infomaniak, so that the future management of this domain is done with Infomaniak; this is therefore not an internal transfer from one holder to another and the code to be obtained is therefore not a code for an internal transfer with your current provider.

Transfer the domain name to Infomaniak

To obtain the authorization code with the current provider:

1. Refer to the complete procedure provided by Hostpoint to obtain the code and keep it safe.
2. Once the authorization code is obtained, refer to the main Infomaniak guide regarding the rest of the domain name transfer procedure.

This guide will help you if, for example, you want to deploy a package like pymysql and it requires a Python version higher than the default one provided on your hosting.

Preamble

• Anaconda is a free and open-source distribution of the programming languages Python and R; it aims to simplify package management and deployment.
• It is recommended to use Miniconda (a lightweight version of conda); it installs in your user space, avoiding any conflict with the system Python and not requiring administrator rights.
• Refer to the official documentation.

1. Download the installer

 For example, the 64-bit Linux version for Python 3.11.

user@server:~$ wget https://repo.anaconda.com/miniconda/Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
--2024-03-10 12:00:00--  https://repo.anaconda.com/miniconda/Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
Resolving repo.anaconda.com... 104.16.131.3, 104.16.130.3
Connecting to repo.anaconda.com|104.16.131.3|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 72787200 (69M) [application/x-sh]
Saving to: ‘Miniconda3-py311_23.10.0-1-Linux-x86_64.sh’

Miniconda3-py311_23.10.0-1-Linux-x86_64.sh  100% [===================>]  69.42M  --.-KB/s    in 0.3s

2. Check the integrity (SHA256 Hash)

user@server:~$ sha256sum Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
6c714a33ea348303f909194246990422e698889417d74b9714856b3e9a7e6c3a  Miniconda3-py311_23.10.0-1-Linux-x86_64.sh

3. Run the installation

The -b argument allows for a silent installation. By default, Miniconda will install in ~/miniconda3.

user@server:~$ bash Miniconda3-py311_23.10.0-1-Linux-x86_64.sh -b
PREFIX=/home/clients/your_client_hash/miniconda3
Unpacking payload ...
Collecting package metadata (current_repodata.json): done
Solving environment: done
Executing transaction: done
installation finished.

4. Initialize and activate Conda

To use conda immediately and with each SSH connection:

user@server:~$ ~/miniconda3/bin/conda init bash
no change     /home/clients/your_client_hash/miniconda3/condabin/conda
...
modified      /home/clients/your_client_hash/.bashrc

user@server:~$ source ~/.bashrc

5. Install a package (example: pymysql)

Once activated, the (base) prefix appears before your command prompt. You can then install your tools without sudo or --user.

(base) user@server:~$ python -V
Python 3.11.5

(base) user@server:~$ pip install pymysql
Collecting pymysql
  Downloading PyMySQL-1.1.0-py3-none-any.whl (44 kB)
Installing collected packages: pymysql
Successfully installed pymysql-1.1.0