ITSquad - Revision history

Ilja: /* Upgrading */

2023-08-18T07:25:11Z

Upgrading

← Older revision		Revision as of 09:25, 18 August 2023
Line 128:		Line 128:

	Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.		Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

			We also have unattended_upgrades running, so security and application upgrades should happen automatically.

	==== Landing page ====		==== Landing page ====

Ilja: /* Add issue pads not working after migrating */

2023-08-18T07:08:47Z

Add issue pads not working after migrating

← Older revision		Revision as of 09:08, 18 August 2023
Line 146:		Line 146:

	See https://github.com/YunoHost/issues/issues/2021 for an ad-hoc solution that was once used. Files have been reverted after ynh11, so this is possibly not active any more.		See https://github.com/YunoHost/issues/issues/2021 for an ad-hoc solution that was once used. Files have been reverted after ynh11, so this is possibly not active any more.

			==== Issues ====
			===== 2023-08-18 =====

			During the migration to ynh 11 the pads didn't work any more. Logs showed

			npm ERR! peer dep missing: eslint@^2 \|\| ^3 \|\| ^4 \|\| ^5 \|\| ^6 \|\| ^7.2.0 \|\| ^8, required by eslint-plugin-import@2.28.0

			This was worked around by doing

			su -s /bin/bash - etherpad_mypads
			mv node_modules/eslint-plugin-import eslint-plugin-import_bkp

			I also tried the following first, but that gave me other errors

			su -s /bin/bash - etherpad_mypads
			npm install "eslint@^2 \|\| ^3 \|\| ^4 \|\| ^5 \|\| ^6 \|\| ^7.2.0 \|\| ^8"
			npm install "eslint"

	=== Yunohost ===		=== Yunohost ===

Ilja: /* Mark that the ad-hoc spam thing is probably not there any more */

2023-08-18T06:52:51Z

Mark that the ad-hoc spam thing is probably not there any more

@@ Line 145: / Line 145: @@
 ==== Spam ====
-If we get too much spam from a specific domain or address, it's possible to block it in config files. Note that we'll be overwriting files with this approach, which means Yunohost wont provide updates or otherwise manage this file any more (I made an issue for it https://github.com/YunoHost/issues/issues/2021 ). It may be still be interesting to use this approach as a temporary solution.
+See https://github.com/YunoHost/issues/issues/2021 for an ad-hoc solution that was once used. Files have been reverted after ynh11, so this is possibly not active any more.
 === Yunohost ===

Ilja: /* Mark that Jirafeau isn't installed any more */

2023-08-18T06:51:39Z

Mark that Jirafeau isn't installed any more

@@ Line 141: / Line 141: @@
 ==== Jirafeau ====
-When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
+We used to have a Jirafeau instance, but it gave too much problems because people uploading unethical or illegal material. In the end it was simply not worth the effort.
 ==== Spam ====

Ilja: /* Spam */

2022-06-11T07:13:00Z

Spam

← Older revision		Revision as of 09:13, 11 June 2022
Line 160:		Line 160:
	==== Spam ====		==== Spam ====

	If we get too much spam from a specific domain or address, it's possible to block it in config files. Note that we'll be overwriting files with this approach, which means Yunohost wont provide updates or otherwise manage this file any more. It may be still be interesting to use this approach as a temporary solution.		If we get too much spam from a specific domain or address, it's possible to block it in config files. Note that we'll be overwriting files with this approach, which means Yunohost wont provide updates or otherwise manage this file any more (I made an issue for it https://github.com/YunoHost/issues/issues/2021 ). It may be still be interesting to use this approach as a temporary solution.

	First create or change the access file, '''nano /etc/postfix/access''', with the following content (replace "some_spammer@badcorp.com" with the address to block).		First create or change the access file, '''nano /etc/postfix/access''', with the following content (replace "some_spammer@badcorp.com" with the address to block).

Ilja: /* Spam */ i used too much spaces, woops

2022-06-10T17:29:36Z

Spam: i used too much spaces, woops

← Older revision		Revision as of 19:29, 10 June 2022
Line 164:		Line 164:
	First create or change the access file, '''nano /etc/postfix/access''', with the following content (replace "some_spammer@badcorp.com" with the address to block).		First create or change the access file, '''nano /etc/postfix/access''', with the following content (replace "some_spammer@badcorp.com" with the address to block).

	some_spammer@badcorp.com REJECT		some_spammer@badcorp.com REJECT

	Only using a domain should also work to block a whole domain. To block multiple addresses/domains, add multiple lines.		Only using a domain should also work to block a whole domain. To block multiple addresses/domains, add multiple lines.
Line 170:		Line 170:
	Then we change '''nano /etc/postfix/main.cf'''. Look for '''smtpd_sender_restrictions''' and add the line '''hash:/etc/postfix/access,''', so it looks like		Then we change '''nano /etc/postfix/main.cf'''. Look for '''smtpd_sender_restrictions''' and add the line '''hash:/etc/postfix/access,''', so it looks like

	smtpd_sender_restrictions =		smtpd_sender_restrictions =
	reject_sender_login_mismatch,		reject_sender_login_mismatch,
	permit_mynetworks,		permit_mynetworks,
	permit_sasl_authenticated,		permit_sasl_authenticated,
	reject_non_fqdn_sender,		reject_non_fqdn_sender,
	reject_unknown_sender_domain,		reject_unknown_sender_domain,
	hash:/etc/postfix/access,		hash:/etc/postfix/access,
	permit		permit

	Then run the following commands		Then run the following commands
	postmap hash:/etc/postfix/access		postmap hash:/etc/postfix/access
	systemctl restart postfix		systemctl restart postfix

	Check that postfix is running via the ynh admin webinterface or via the following command		Check that postfix is running via the ynh admin webinterface or via the following command

	systemctl status postfix		systemctl status postfix

	The ynh diagnostics will see the file /etc/postfix/main.cf has changed. Run the diagnostics, see that this is indeed a problem and ignore it. You can do it from the ynh admin webinterface, or via command line		The ynh diagnostics will see the file /etc/postfix/main.cf has changed. Run the diagnostics, see that this is indeed a problem and ignore it. You can do it from the ynh admin webinterface, or via command line

	yunohost diagnosis run		yunohost diagnosis run
	yunohost diagnosis show --issues		yunohost diagnosis show --issues
	yunohost diagnosis ignore --filter regenconf		yunohost diagnosis ignore --filter regenconf

	To roll this change back, you can unignore the diagnostic, run it, run the command to fix the file (diagnostic will tell you this), restart postfix and '''rm /etc/postfix/access'''.		To roll this change back, you can unignore the diagnostic, run it, run the command to fix the file (diagnostic will tell you this), restart postfix and '''rm /etc/postfix/access'''.

Ilja: /* Parley */

2022-06-10T16:23:03Z

Parley

← Older revision		Revision as of 18:23, 10 June 2022
Line 157:		Line 157:

	When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)		When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

			==== Spam ====

			If we get too much spam from a specific domain or address, it's possible to block it in config files. Note that we'll be overwriting files with this approach, which means Yunohost wont provide updates or otherwise manage this file any more. It may be still be interesting to use this approach as a temporary solution.

			First create or change the access file, '''nano /etc/postfix/access''', with the following content (replace "some_spammer@badcorp.com" with the address to block).

			some_spammer@badcorp.com REJECT

			Only using a domain should also work to block a whole domain. To block multiple addresses/domains, add multiple lines.

			Then we change '''nano /etc/postfix/main.cf'''. Look for '''smtpd_sender_restrictions''' and add the line '''hash:/etc/postfix/access,''', so it looks like

			smtpd_sender_restrictions =
			reject_sender_login_mismatch,
			permit_mynetworks,
			permit_sasl_authenticated,
			reject_non_fqdn_sender,
			reject_unknown_sender_domain,
			hash:/etc/postfix/access,
			permit

			Then run the following commands
			postmap hash:/etc/postfix/access
			systemctl restart postfix

			Check that postfix is running via the ynh admin webinterface or via the following command

			systemctl status postfix

			The ynh diagnostics will see the file /etc/postfix/main.cf has changed. Run the diagnostics, see that this is indeed a problem and ignore it. You can do it from the ynh admin webinterface, or via command line

			yunohost diagnosis run
			yunohost diagnosis show --issues
			yunohost diagnosis ignore --filter regenconf

			To roll this change back, you can unignore the diagnostic, run it, run the command to fix the file (diagnostic will tell you this), restart postfix and '''rm /etc/postfix/access'''.

	=== Yunohost ===		=== Yunohost ===

Ilja: /* Jirafeau */

2022-05-26T06:36:27Z

Jirafeau

← Older revision		Revision as of 08:36, 26 May 2022
Line 151:		Line 151:
	*** the maximum is a month		*** the maximum is a month
	** availability_default: 'week'		** availability_default: 'week'
	** maximal_upload_size: ~~'2000MB'~~		** maximal_upload_size: 2000
	** store_uploader_ip: false		** store_uploader_ip: false

Ilja: /* Jirafeau */

2022-05-26T06:26:29Z

Jirafeau

← Older revision		Revision as of 08:26, 26 May 2022
Line 143:		Line 143:
	When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.		When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
	* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/config.original.php''.		* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/config.original.php''.
	* ~~The default time to keep a file is a week~~, ~~the maximum is a month~~.		** organisation: 'Parley'
	* ~~The max uploadlimit is 2000MB (2GB)~~		** preview: false
	* ~~You can set an admin user.~~ If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface ~~(at time of writing and afaik, this is only one user max)~~. Another option is to use a shared password and set that ~~instead.~~		*** This was done after [https://gitlab.com/mojo42/Jirafeau/-/merge_requests/103 an XSS vulnerability] was discovered. It's fixed now, but just in case.
			** admin_http_auth_user: <your-account?>
			*** If you're the one who mostly maintains this, you can add yourself. It's the username for the ynh user-interface. Another option is to use a shared password and set that in admin_password
			** availabilities:
			*** the maximum is a month
			** availability_default: 'week'
			** maximal_upload_size: '2000MB'
			** store_uploader_ip: false

	Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See this [https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau blog post] and/or [https://gitlab.com/mojo42/Jirafeau/-/issues/19#note_681349145 comment on the Jirafeau issue tracker] on how it's set up.		Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See this [https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau blog post] and/or [https://gitlab.com/mojo42/Jirafeau/-/issues/19#note_681349145 comment on the Jirafeau issue tracker] on how it's set up.

Ilja: /* Jirafeau */

2022-05-26T06:04:37Z

Jirafeau

← Older revision		Revision as of 08:04, 26 May 2022
Line 142:		Line 142:

	When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.		When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
	* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''~~/var/www/jirafeau/lib~~/var/www/jirafeau/lib/config.original.php''.		* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/config.original.php''.
	* The default time to keep a file is a week, the maximum is a month.		* The default time to keep a file is a week, the maximum is a month.
	* The max uploadlimit is 2000MB (2GB)		* The max uploadlimit is 2000MB (2GB)
	* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.		* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

	Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau		Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See this [https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau blog post] and/or [https://gitlab.com/mojo42/Jirafeau/-/issues/19#note_681349145 comment on the Jirafeau issue tracker] on how it's set up.

	When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)		When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)