Plum (Photo) - Revision history

Wikisailor: /* Updates */

2026-02-28T03:05:25Z

Updates

← Older revision		Revision as of 03:05, 28 February 2026
Line 5:		Line 5:
	==Updates==		==Updates==

	Both Logan and [[Lime]] have been retired with all of their website setup file and database moved to Plum as vhosts. Postfix is also running from Plum as well.		Both Logan and '''[[Lime]]''' have been retired with all of their website setup file and database moved to Plum as vhosts. '''[[Postfix Installation\| Postfix ]]'''is also running from Plum as well.

	==Initial Setup==		==Initial Setup==

Wikisailor: /* Introduction */

2026-02-28T03:03:15Z

Introduction

← Older revision		Revision as of 03:03, 28 February 2026
Line 2:		Line 2:

	The host plum.seaoffate.net will be at an IP address of production.20. The purpose will be to show photos using Piwigo. The main premise is that plum will have a SSD hard drive for it's OS as normal but it will have a large hard drive from the ZFS Proxmox storage to store the photos and video. We can add the hd as soon as the VM is created but leave it to be formatted and mounted later.		The host plum.seaoffate.net will be at an IP address of production.20. The purpose will be to show photos using Piwigo. The main premise is that plum will have a SSD hard drive for it's OS as normal but it will have a large hard drive from the ZFS Proxmox storage to store the photos and video. We can add the hd as soon as the VM is created but leave it to be formatted and mounted later.

			==Updates==

			Both Logan and [[Lime]] have been retired with all of their website setup file and database moved to Plum as vhosts. Postfix is also running from Plum as well.

	==Initial Setup==		==Initial Setup==

Sailor: /* Initial Setup */

2025-03-16T23:17:27Z

Initial Setup

← Older revision		Revision as of 23:17, 16 March 2025
Line 40:		Line 40:
	GRANT ALL PRIVILEGES ON piwigo_db.* TO 'piwigo_user'@'192.168.100.22';		GRANT ALL PRIVILEGES ON piwigo_db.* TO 'piwigo_user'@'192.168.100.22';
	FLUSH PRIVILEGES;		FLUSH PRIVILEGES;
	exit?		exit;
	Armed with our newly created database and user we can now start the web installation so we need to go get a web browser to https://photo.seaoffate.local. if that takes us to the nginix holding page we will need to setup raisin to do the reverse proxy thing or we could continue from a client inside the Pfsense but if we do that we still have to do the raisin set up at some point. so we may as well do so now so SSH to raisin		Armed with our newly created database and user we can now start the web installation so we need to go get a web browser to https://photo.seaoffate.local. if that takes us to the nginix holding page we will need to setup raisin to do the reverse proxy thing or we could continue from a client inside the Pfsense but if we do that we still have to do the raisin set up at some point. so we may as well do so now so SSH to raisin
	cd /etc/nginx/sites-available		cd /etc/nginx/sites-available

Sailor: /* Initial Setup */

2025-03-16T23:12:57Z

Initial Setup

@@ Line 46: / Line 46: @@
   sudo cp wiki.seaoffate.local.ssl.conf photo.seaoffate.local.ssl.conf
   sudo cp wiki.seaoffate.net.conf photo.seaoffate.net.conf
-Then modify them to replace the servernames and ip addresses. While it is not pretty it does work and the scripts that we had generated forwarding loops so we can't use them. It looks like the reverse proxy was redirecting as well as the origin so it was causing a problem for browsers, we should only have the origin browser do any redirect between 80 and 443. Once this is done proceed to the web browser part of the piwigi installation. Keep a record of passwords in a password manager. Most of the install is now done. we could use the application as is but we would run out of storage for photos before too long so we will add a big hard drive to the installation mounting it inside public_html.
+Then modify them to replace the servernames and ip addresses. While it is not pretty it does work and the scripts that we had generated forwarding loops so we can't use them. It looks like the reverse proxy was redirecting as well as the origin so it was causing a problem for browsers, we should only have the origin browser do any redirect between 80 and 443. Once this is done proceed to the web browser part of the piwigi installation. Keep a record of passwords in a password manager. The Details that need to be entered on the web install are:

Sailor: /* Initial Setup */

2025-03-16T22:57:26Z

Initial Setup

← Older revision		Revision as of 22:57, 16 March 2025
Line 28:		Line 28:
	This will create a dir called piwigo and so we rename it to public_html		This will create a dir called piwigo and so we rename it to public_html
	sudo mv piwigo /var/www/plum.seaoffate.local/public_html		sudo mv piwigo /var/www/plum.seaoffate.local/public_html
	so we now should have all of the files extracted in to the docroot of our website we now need to change the ~~ownersip~~ to the apache user		so we now should have all of the files extracted in to the docroot of our website we now need to change the permissions & ownership to the apache user
	sudo chown -R www-data:www-data /var/www/plum.seaoffate.local/public_html/		sudo chown -R www-data:www-data /var/www/plum.seaoffate.local/public_html/
			sudo chmod 755 -R /var/www/plum.seaoffate.local/public_html/

	Before we can proceed with the installation at a web browser we have to create a database and for piwigo to use so ssh to mandarin and start a MySQL session with		Before we can proceed with the installation at a web browser we have to create a database and for piwigo to use so ssh to mandarin and start a MySQL session with
	sudo mysql -u root -p		sudo mysql -u root -p

Sailor: /* Initial Setup */

2025-03-16T22:53:37Z

Initial Setup

← Older revision		Revision as of 22:53, 16 March 2025
Line 25:		Line 25:
	sudo rm -rf /var/www/plum.seaoffate.local/public_html		sudo rm -rf /var/www/plum.seaoffate.local/public_html
	and then unzip the file with		and then unzip the file with
	unzip piwigo-15.4.0.zip -d .		sudo unzip piwigo-15.4.0.zip -d .
	This will create a dir called piwigo and so we rename it to public_html		This will create a dir called piwigo and so we rename it to public_html
	sudo mv piwigo /var/www/plum.seaoffate.local/public_html		sudo mv piwigo /var/www/plum.seaoffate.local/public_html

192.168.100.9: /* Initial Setup */

2025-03-16T12:49:22Z

Initial Setup

← Older revision		Revision as of 12:49, 16 March 2025
Line 44:		Line 44:
	sudo cp wiki.seaoffate.local.ssl.conf photo.seaoffate.local.ssl.conf		sudo cp wiki.seaoffate.local.ssl.conf photo.seaoffate.local.ssl.conf
	sudo cp wiki.seaoffate.net.conf photo.seaoffate.net.conf		sudo cp wiki.seaoffate.net.conf photo.seaoffate.net.conf
	Then modify them to replace the servernames and ip addresses. While it is not pretty it does work and the scripts that we had generated forwarding loops so we can't use them. It looks like the reverse proxy was redirecting as well as the origin so it was causing a problem for browsers, we should only have the origin browser do any redirect between 80 and 443.		Then modify them to replace the servernames and ip addresses. While it is not pretty it does work and the scripts that we had generated forwarding loops so we can't use them. It looks like the reverse proxy was redirecting as well as the origin so it was causing a problem for browsers, we should only have the origin browser do any redirect between 80 and 443. Once this is done proceed to the web browser part of the piwigi installation. Keep a record of passwords in a password manager. Most of the install is now done. we could use the application as is but we would run out of storage for photos before too long so we will add a big hard drive to the installation mounting it inside public_html.

192.168.100.9: /* Initial Setup */

2025-03-16T12:42:56Z

Initial Setup

← Older revision		Revision as of 12:42, 16 March 2025
Line 39:		Line 39:
	FLUSH PRIVILEGES;		FLUSH PRIVILEGES;
	exit?		exit?
	Armed with our newly created database and user we can now start the web installation so we need to go get a web browser to https://photo.seaoffate.local		Armed with our newly created database and user we can now start the web installation so we need to go get a web browser to https://photo.seaoffate.local. if that takes us to the nginix holding page we will need to setup raisin to do the reverse proxy thing or we could continue from a client inside the Pfsense but if we do that we still have to do the raisin set up at some point. so we may as well do so now so SSH to raisin
			cd /etc/nginx/sites-available
			sudo cp wiki.conf photo.conf
			sudo cp wiki.seaoffate.local.ssl.conf photo.seaoffate.local.ssl.conf
			sudo cp wiki.seaoffate.net.conf photo.seaoffate.net.conf
			Then modify them to replace the servernames and ip addresses. While it is not pretty it does work and the scripts that we had generated forwarding loops so we can't use them. It looks like the reverse proxy was redirecting as well as the origin so it was causing a problem for browsers, we should only have the origin browser do any redirect between 80 and 443.

Sailor: /* Initial Setup */

2025-03-16T08:51:04Z

Initial Setup

← Older revision		Revision as of 08:51, 16 March 2025
Line 30:		Line 30:
	so we now should have all of the files extracted in to the docroot of our website we now need to change the ownersip to the apache user		so we now should have all of the files extracted in to the docroot of our website we now need to change the ownersip to the apache user
	sudo chown -R www-data:www-data /var/www/plum.seaoffate.local/public_html/		sudo chown -R www-data:www-data /var/www/plum.seaoffate.local/public_html/
			Before we can proceed with the installation at a web browser we have to create a database and for piwigo to use so ssh to mandarin and start a MySQL session with
			sudo mysql -u root -p
			at the mysql> prompt we need to create the database
			CREATE DATABASE piwigo_db;
			and then the user with privileges to the database, we will restrict this user to the plum host only
			CREATE USER 'piwigo_user'@'192.168.100.22' IDENTIFIED BY 'your_strong_password';
			GRANT ALL PRIVILEGES ON piwigo_db.* TO 'piwigo_user'@'192.168.100.22';
			FLUSH PRIVILEGES;
			exit?
			Armed with our newly created database and user we can now start the web installation so we need to go get a web browser to https://photo.seaoffate.local

Sailor: /* Initial Setup */

2025-03-16T08:23:37Z

Initial Setup

← Older revision		Revision as of 08:23, 16 March 2025
Line 14:		Line 14:
	Now that we have the first scripts we can execute them		Now that we have the first scripts we can execute them
	./lamp_client_install.sh		./lamp_client_install.sh
	and then setup the ~~config on apache~~. We ~~are going to be referring to~~ the ~~website as~~ photo.seaoffate.net~~, photo~~.seaoffate.~~local~~ and ~~plum~~.~~seaoffate~~.~~local~~ and this will ~~setup all three both as http: and https: disable~~ the ~~default website~~ and ~~enable~~ the ~~photo websites with~~		and then setup the websites with the other script
	sudo ~~a2dissite 000~~-~~default~~.~~conf~~		./create_apache_config.sh photo
	sudo ~~a2ensite photo~~.seaoffate.local.~~conf photo~~.~~seaoffate~~.~~net~~.~~conf~~ plum.seaoffate.local~~.conf~~		This script will create the configs for the hostname(plum) and the parameter in this case photo. We will get 6 configs both the http and https for plum.seaofffate.local and photo.seaoffate.local and photo.seaoffate.net. We will should check that the seaoffate.crt is in the /etc/ssl/certs dir
	~~sudo systemctl reload apache2~~		ls -l /etc/ssl/certs/
	sudo ~~systemctl status apache2~~		If it is missing then we should get the cert and key and mv it to the /etc/ssl/ dirs it should be called "seaoffate" (.crt & .key) to match the Apache configs that we just created. The next thing we need to do is get the piwigo zip file. Probably the best thing is to get it downloaded on to one of the desktop Linux VMs and scp it to this at the home dir. We will need to copy the zip to the public_html (best to cp rather than mv in case we need to redo the install and we would just delete everything in public_html). First we install zip, then cp the zip file then cd to where we want to extract to
			sudo apt install zip
			sudo cp piwigo-15.4.0.zip /var/www/plum.seaoffate.local
			cd /var/www/plum.seaoffate.local
			Then delete the existing public_html
			sudo rm -rf /var/www/plum.seaoffate.local/public_html
			and then unzip the file with
			unzip piwigo-15.4.0.zip -d .
			This will create a dir called piwigo and so we rename it to public_html
			sudo mv piwigo /var/www/plum.seaoffate.local/public_html
			so we now should have all of the files extracted in to the docroot of our website we now need to change the ownersip to the apache user
			sudo chown -R www-data:www-data /var/www/plum.seaoffate.local/public_html/