rbachwiki - Recent changes [en]

Setup SSL

Bacchas — Fri, 13 Nov 2026 16:15:50 GMT

Revoking and Removing a Certificate

@@ Line 85: / Line 85: @@
   certbot certonly --cert-name example.com -d example.org,www.example.org
 =[[Linode]]=
 [[Category:Linode]]

Moving To New Server

Bacchas — Wed, 11 Nov 2026 17:31:25 GMT

← Older revision		Revision as of 17:31, 11 November 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
			=Moving Joomla to a new Server=

	==On the old server, dump the database:==		==On the old server, dump the database:==
	mysqldump -u root -p --single-transaction --routines DBNAME > joomla.sql		mysqldump -u root --single-transaction --routines DBNAME > joomla.sql

	Copy the files while preserving permissions and timestamps:		Copy the files while preserving permissions and timestamps:
Line 9:		Line 11:

	===Create the database in phpmyadmin===		===Create the database in phpmyadmin===
	1. Log in to phpMyAdmin (as root or another admin user).		* Log in to phpMyAdmin (as root or another admin user).
	2. Click Databases in the top tab bar.		* Click Databases in the top tab bar.
	3. Under “Create database,” enter the name and pick the collation utf8mb4_unicode_ci (or utf8mb4_general_ci). Click Create.		* Under “Create database,” enter the name and pick the collation utf8mb4_unicode_ci (or utf8mb4_general_ci). Click Create.

			==Import from the command line==
			mysql -u root DBNAME < joomla.sql

Moving To New Server

Bacchas — Wed, 11 Nov 2026 17:29:03 GMT

Created page with "==On the old server, dump the database:== mysqldump -u root -p --single-transaction --routines DBNAME > joomla.sql Copy the files while preserving permissions and timestamps: rsync -avz --progress /var/www/joomla/ user@newserver:/var/www/joomla/ == On the new server, create the database and user, then import: == ===Create the database in phpmyadmin=== 1. Log in to phpMyAdmin (as root or another admin user). 2. Click Databases in the top tab bar. 3. Under “Create..."

New page

==On the old server, dump the database:==
mysqldump -u root -p --single-transaction --routines DBNAME > joomla.sql

Copy the files while preserving permissions and timestamps:

rsync -avz --progress /var/www/joomla/ user@newserver:/var/www/joomla/

== On the new server, create the database and user, then import: ==

===Create the database in phpmyadmin===
1. Log in to phpMyAdmin (as root or another admin user).
2. Click Databases in the top tab bar.
3. Under “Create database,” enter the name and pick the collation utf8mb4_unicode_ci (or utf8mb4_general_ci). Click Create.

Joomla

Bacchas — Wed, 11 Nov 2026 17:25:26 GMT

← Older revision		Revision as of 17:25, 11 November 2026
Line 1:		Line 1:
	== [[Joomla Tips]] ==		== [[Joomla Tips]] ==
	== [[Smartform Gold]]==		== [[Smartform Gold]]==
			==[[Moving To New Server]]==

MYSQL DATABASE RESTORE

Bacchas — Wed, 11 Nov 2026 14:44:23 GMT

Script to import a CSV File into an existing Database

← Older revision		Revision as of 14:44, 11 November 2026
Line 13:		Line 13:
	<hr />		<hr />

	== <h4 class="yellowbackground">Script to import a CSV File into an existing Database</h4> ==		== <p class="yellowbackground">Script to import a CSV File into an existing Database</p> ==
	<p style="background-color: #77a8f7; font-weight: bold; font-size: 1.2rem;">The csv file has to be in a specific directory. /var/lib/mysql-files/</p>		<p style="background-color: #77a8f7; font-weight: bold; font-size: 1.2rem;">The csv file has to be in a specific directory. /var/lib/mysql-files/</p>
	<p style="background-color: #77a8f7; font-weight: bold; font-size: 1.2rem;">The table has to already exist </p>		<p style="background-color: #77a8f7; font-weight: bold; font-size: 1.2rem;">The table has to already exist </p>

Docker Deploy App

Bacchas — Tue, 10 Nov 2026 18:18:27 GMT

@@ Line 212: / Line 212: @@
 If migrating an existing hostname, keep the old server running while DNS changes propagate.
-== 8. Enable HTTPS ==
+== 8. [[Setup_SSL]] ==
 Ensure the HTTPS virtual host retains the ProxyPass and ProxyPassReverse settings, including timeout=600.

Docker Deploy App

Bacchas — Tue, 10 Nov 2026 18:03:40 GMT

Created page with "= Deploy PDF Extractor to a New Server = This guide deploys PDF Extractor using Docker Compose, with Apache providing HTTPS access. == Requirements == * An Ubuntu server with Apache and Docker already installed. * SSH access with root or sudo privileges. * A domain or subdomain pointing to the new server. * The complete application deployment ZIP, including: ** Dockerfile ** compose.yaml ** requirements.txt ** app.py ** static/ directory '''Use the complete deploymen..."

New page

= Deploy PDF Extractor to a New Server =

This guide deploys PDF Extractor using Docker Compose, with Apache providing HTTPS access.

== Requirements ==

* An Ubuntu server with Apache and Docker already installed.
* SSH access with root or sudo privileges.
* A domain or subdomain pointing to the new server.
* The complete application deployment ZIP, including:
** Dockerfile
** compose.yaml
** requirements.txt
** app.py
** static/ directory

'''Use the complete deployment ZIP for a new installation. An update-only ZIP may not contain everything required.'''

== Example Settings ==

Replace these example values where necessary:

{| class="wikitable"
! Setting !! Example
|-
| Application directory || /opt/pdfextractorwebapp
|-
| Website address || pdf.example.com
|-
| Deployment archive || pdf-extractor-web-full-deploy-2026-11-10.zip
|-
| Local application port || 8000
|}

The project files reside in /opt/pdfextractorwebapp on the server. The application runs inside its Docker container.

== 1. Upload the Application ==

Upload the complete deployment ZIP to the new server's /tmp/ directory using SCP, SFTP, or your preferred file-transfer application.

== 2. Check Docker Compose ==

Connect to the server using SSH, then run:

<pre>
sudo docker --version
sudo docker compose version
</pre>

Both commands should display version information.

If the second command fails, install the Docker Compose plugin for your Docker installation before continuing.

== 3. Extract the Application ==

Install unzip and curl if needed:

<pre>
sudo apt update
sudo apt install -y unzip curl
</pre>

Create the application directory and extract the archive:

<pre>
sudo mkdir -p /opt/pdfextractorwebapp
cd /opt/pdfextractorwebapp

sudo unzip -o /tmp/pdf-extractor-web-full-deploy-2026-11-10.zip
</pre>

Confirm the project files are directly inside this directory:

<pre>
ls -la
</pre>

Dockerfile and compose.yaml should be visible.

== 4. Build and Start the Container ==

From the application directory, run:

<pre>
sudo docker compose up -d --build
</pre>

The first build downloads dependencies and may take several minutes.

* --build builds the application image.
* -d runs the container in the background.

Check the container:

<pre>
sudo docker compose ps
</pre>

Its status should show '''Up'''.

The supplied compose.yaml includes a restart policy so the application restarts after a server reboot, provided Docker starts automatically.

Enable Docker at startup:

<pre>
sudo systemctl enable --now docker
</pre>

== 5. Test the Application Directly ==

Before configuring Apache, test the application locally:

<pre>
curl -fsS http://127.0.0.1:8000/health
curl -I http://127.0.0.1:8000/
</pre>

Expected results:

* The health endpoint returns {"status": "ok"}.
* The application page returns HTTP 200.

'''Do not continue until these checks pass.'''

To investigate a failure:

<pre>
cd /opt/pdfextractorwebapp
sudo docker compose logs --tail=100 pdf-extractor
</pre>

The supplied configuration binds port 8000 to 127.0.0.1. Keep this setting so Apache handles public access.

== 6. Configure Apache ==

Enable the reverse-proxy modules:

<pre>
sudo a2enmod proxy proxy_http
</pre>

Create an Apache site configuration:

<pre>
sudo nano /etc/apache2/sites-available/pdfextractor.conf
</pre>

Paste the following, replacing pdf.example.com with your actual hostname:

<pre>
<VirtualHost *:80>
ServerName pdf.example.com

ProxyRequests Off
ProxyPreserveHost On
ProxyTimeout 600

LimitRequestBody 53477376

ProxyPass "/" "http://127.0.0.1:8000/" connectiontimeout=5 timeout=600
ProxyPassReverse "/" "http://127.0.0.1:8000/"

ErrorLog ${APACHE_LOG_DIR}/pdfextractor-error.log
CustomLog ${APACHE_LOG_DIR}/pdfextractor-access.log combined
</VirtualHost>
</pre>

The timeout accommodates longer PDF exports. The request-body limit accommodates the application's default 50 MB upload limit plus metadata.

If this hostname already has an Apache configuration, update that configuration instead of creating a competing virtual host.

Enable the site and validate the configuration:

<pre>
sudo a2ensite pdfextractor.conf
sudo apache2ctl configtest
</pre>

If the result is '''Syntax OK''', reload Apache:

<pre>
sudo systemctl reload apache2
</pre>

Test Apache's connection to the application:

<pre>
curl -i -H "Host: pdf.example.com" http://127.0.0.1/health
</pre>

Expected result: HTTP 200 and {"status": "ok"}.

== 7. Configure DNS and Firewall Access ==

At your DNS provider:

# Set the hostname's A record to the new server's public IPv4 address.
# If an AAAA record exists, update it to the new server's IPv6 address, or remove it if IPv6 is unused.

Allow inbound TCP ports '''80''' and '''443''' through the server firewall and any hosting-provider firewall.

If UFW is already active, allow Apache traffic:

<pre>
sudo ufw allow 'Apache Full'
</pre>

Do not enable UFW without first ensuring SSH access is allowed.

Port 8000 does not need public access.

If migrating an existing hostname, keep the old server running while DNS changes propagate.

== 8. Enable HTTPS ==

After DNS points to the new server, install Certbot and its Apache plugin if needed:

<pre>
sudo apt install -y certbot python3-certbot-apache
</pre>

Obtain a certificate and enable redirection to HTTPS:

<pre>
sudo certbot --apache -d pdf.example.com --redirect
</pre>

Follow the prompts.

Check the configuration and certificate renewal:

<pre>
sudo apache2ctl configtest
sudo certbot renew --dry-run
</pre>

Ensure the HTTPS virtual host retains the ProxyPass and ProxyPassReverse settings, including timeout=600.

== 9. Verify the Deployment ==

Test the public HTTPS endpoint:

<pre>
curl -fsS https://pdf.example.com/health
</pre>

Open the website in a browser and verify:

# The interface loads.
# A PDF can be uploaded.
# Page previews work.
# An export downloads successfully.
# Multiple PDFs can be processed together.

== Updating the Application Later ==

Upload the update ZIP to /tmp/, then run:

<pre>
cd /opt/pdfextractorwebapp

sudo unzip -o /tmp/UPDATE-FILENAME.zip
sudo docker compose up -d --build

curl -fsS http://127.0.0.1:8000/health
curl -I http://127.0.0.1:8000/
</pre>

Replace UPDATE-FILENAME.zip with the actual archive name.

Refresh the website after rebuilding.

== Useful Commands ==

Run these commands from /opt/pdfextractorwebapp.

=== View Container Status ===

<pre>
sudo docker compose ps
</pre>

=== View Recent Application Logs ===

<pre>
sudo docker compose logs --tail=100 pdf-extractor
</pre>

=== Follow Application Logs ===

<pre>
sudo docker compose logs -f pdf-extractor
</pre>

Press Ctrl+C to stop following logs. This does not stop the container.

=== Restart the Application ===

<pre>
sudo docker compose restart
</pre>

Restarting does not apply source-code changes copied into the Docker image. Use a rebuild after updating application files.

=== Rebuild After Changes ===

<pre>
sudo docker compose up -d --build
</pre>

=== Stop the Application ===

<pre>
sudo docker compose stop
</pre>

=== View Apache Errors ===

<pre>
sudo tail -n 100 /var/log/apache2/pdfextractor-error.log
</pre>

== Troubleshooting ==

=== Apache Displays a Proxy Error ===

Check the application directly:

<pre>
curl -i --max-time 10 http://127.0.0.1:8000/health
curl -I --max-time 10 http://127.0.0.1:8000/
sudo docker compose logs --tail=100 pdf-extractor
</pre>

If the local application works, inspect the Apache configuration and error log.

=== Permission Denied for Static Files ===

If the container logs report PermissionError for /app/static/index.html, correct the source-file permissions and rebuild:

<pre>
cd /opt/pdfextractorwebapp

sudo chmod 755 static
sudo chmod 644 app.py static/index.html static/app.js static/style.css

sudo docker compose up -d --build
</pre>

The corrected Dockerfile also normalizes these permissions during the build.

=== Exports Time Out ===

Confirm the active HTTPS virtual host includes timeout=600 on its ProxyPass directive.

Validate and reload Apache after changing its configuration:

<pre>
sudo apache2ctl configtest
sudo systemctl reload apache2
</pre>

For unusually large exports, try fewer pages or smaller batches.

== References ==

* [https://docs.docker.com/reference/cli/docker/compose/up/ Docker Compose: build and start containers]
* [https://httpd.apache.org/docs/2.4/en/howto/reverse_proxy.html Apache reverse-proxy guide]
* [https://eff-certbot.readthedocs.io/en/stable/man/certbot.html Certbot documentation]

Docker

Bacchas — Tue, 10 Nov 2026 18:00:09 GMT

← Older revision		Revision as of 18:00, 10 November 2026
Line 1:		Line 1:
	==[[Docker on Raspberry Pi]]==		==[[Docker on Raspberry Pi]]==
	==[[Docker tutorial]]==		==[[Docker tutorial]]==
			==[[Docker Deploy App]]==

INSTALL PHYMYADMIN

Bacchas — Tue, 10 Nov 2026 17:03:14 GMT

Installing phpMyAdmin on Ubuntu Server

← Older revision		Revision as of 17:03, 10 November 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
			== Installing phpMyAdmin on Ubuntu Server ==

			==== 1. Install the packages ====

	sudo apt update		sudo apt update
	sudo apt install -y phpmyadmin php-mbstring php-zip php-gd php-json php-curl		sudo apt install -y phpmyadmin php-mbstring php-zip php-gd php-json php-curl


			==== 2. Answer the installer prompts ====
			{\| class="wikitable"
			! Prompt !! Action
			\|-
			\| Web server to configure \|\| Press '''Space''' to select '''apache2''', then Tab and Enter
			\|-
			\| Configure database with dbconfig-common \|\| Choose '''Yes'''
			\|-
			\| Password for the phpmyadmin user \|\| Set a password, or leave blank for a random one
			\|}

			{{Note\|If you skip selecting apache2, phpMyAdmin will not be wired into Apache.}}

			==== 3. Enable mbstring and restart Apache ====

			sudo phpenmod mbstring
			sudo systemctl restart apache2


			phpMyAdmin is now available at <code>http://your-server-ip/phpmyadmin</code>.

			=== Creating an admin user ===
			On Ubuntu, MySQL's root account uses socket authentication, so logging in as root with a password through phpMyAdmin will fail. Create a dedicated admin user instead:

			sudo mysql

			CREATE USER 'pmaadmin'@'localhost' IDENTIFIED BY 'a-strong-password';
			GRANT ALL PRIVILEGES ON . TO 'pmaadmin'@'localhost' WITH GRANT OPTION;
			FLUSH PRIVILEGES;
			EXIT;


			Log in to phpMyAdmin as <code>pmaadmin</code>.

			=== Security hardening ===
			phpMyAdmin is a frequent target for bots. If the server is reachable from the internet, apply the following.

			==== Restrict access by IP ====
			Edit <code>/etc/apache2/conf-available/phpmyadmin.conf</code> and add this inside the <code><Directory /usr/share/phpmyadmin></code> block:

INSTALL PHYMYADMIN

Bacchas — Tue, 10 Nov 2026 16:39:57 GMT

Created page with " sudo apt update sudo apt install -y phpmyadmin php-mbstring php-zip php-gd php-json php-curl"

New page

sudo apt update
sudo apt install -y phpmyadmin php-mbstring php-zip php-gd php-json php-curl

Mysql

Bacchas — Tue, 10 Nov 2026 16:39:27 GMT

← Older revision		Revision as of 16:39, 10 November 2026
Line 1:		Line 1:
	=[[DADABIK]]=		=[[DADABIK]]=
	=[[MYSQL COMMANDS]]=		=[[MYSQL COMMANDS]]=
			=[[INSTALL PHYMYADMIN]]=
	=[[MYSQL DATABASE RESTORE]]=		=[[MYSQL DATABASE RESTORE]]=
	=[[MYSQL DATABASE BACKUP]]=		=[[MYSQL DATABASE BACKUP]]=