Tech Documentation - Revision history

PositiveSpin: /* As of 2023 */ Actual name of the utility

2023-07-24T03:40:29Z

As of 2023: Actual name of the utility

← Older revision		Revision as of 03:40, 24 July 2023
Line 16:		Line 16:
	* lists.bikecollectives.org (MailMan3 email lists, including The ThinkTank)		* lists.bikecollectives.org (MailMan3 email lists, including The ThinkTank)
	* RoundCube email client for tech administrative mail (e.g. DMARC reports)		* RoundCube email client for tech administrative mail (e.g. DMARC reports)
	* ~~Restic backup~~		* Resticker - automatic restic backups
	* PassBolt password manager for administrative logins		* PassBolt password manager for administrative logins
	*Apprise - push notifications		*Apprise - push notifications

PositiveSpin: /* MediaWiki */ Restart is all that is required.

2023-07-23T22:06:20Z

MediaWiki: Restart is all that is required.

← Older revision		Revision as of 22:06, 23 July 2023
Line 27:		Line 27:
	* Settings for Mediawiki are in /home/bikebike/docker/bikecollectives/LocalSettings.php		* Settings for Mediawiki are in /home/bikebike/docker/bikecollectives/LocalSettings.php
	* Extensions are in the container at /var/www/html/w/extensions		* Extensions are in the container at /var/www/html/w/extensions
	* To make changes happen after editing, you issue a<code>docker compose ~~up -d~~</code>in the /home/bikebike/docker/bikecollectives directory		* To make changes happen after editing, you issue a<code>docker compose restart</code>in the /home/bikebike/docker/bikecollectives directory
	* The yellowish box at the top of the wiki can be edited at [[MediaWiki:Sitenotice]]		* The yellowish box at the top of the wiki can be edited at [[MediaWiki:Sitenotice]]

PositiveSpin: /* As of July 23, 2023 */ Pointing out the script that makes this happen.

2023-07-23T21:40:43Z

As of July 23, 2023: Pointing out the script that makes this happen.

← Older revision		Revision as of 21:40, 23 July 2023
Line 55:		Line 55:
	However, Bumbleberry broke when BikeBike was dockerized, and was updated to more recent and secure Ruby libraries. This means that it no longer updates properly without breaking BikeBike. In the absense of using Bumbleberry directly to update the css, when browser version are identified by BikeBike, if they don't exist in /public/stylesheets/* the browser renders a responsive view, which doesn't look right for normal size screens.		However, Bumbleberry broke when BikeBike was dockerized, and was updated to more recent and secure Ruby libraries. This means that it no longer updates properly without breaking BikeBike. In the absense of using Bumbleberry directly to update the css, when browser version are identified by BikeBike, if they don't exist in /public/stylesheets/* the browser renders a responsive view, which doesn't look right for normal size screens.

	Godwin recommended using the most recent css for the newer versions. This works well for modern browsers. To enable this feat, the most recent browsers have to be identified, and the css from the most recent version has to be copied over to the newer version. The irony is we could avoid this exercise, and only support modern browsers with one css file, but in the spirit of browser justice let's not assume obscure browsers are not being used anymore.		Godwin recommended using the most recent css for the newer versions. This works well for modern browsers. To enable this feat, the most recent browsers have to be identified, and the css from the most recent version has to be copied over to the newer version. The irony is we could avoid this exercise, and only support modern browsers with one css file, but in the spirit of browser justice let's not assume obscure browsers are not being used anymore. This is now handled by [https://git.bikeshopi.dev/bike/BikeBikeBike/src/branch/master/caniuse.js caniuse.js].

	The only disadvantage to this approach would be if a new browser with unknown css arose. Fortunately, this probably won't be an issue for a long time to come, since new browsers projects almost always adopt the identity of a major engine: and_chr, and_ff, and_qq, and_uc, android, baidu, bb, chrome, edge, firefox, ie, ie_mob, ios_saf, kaios, op_mini, op_mobm, opera, safari, samsung		The only disadvantage to this approach would be if a new browser with unknown css arose. Fortunately, this probably won't be an issue for a long time to come, since new browsers projects almost always adopt the identity of a major engine: and_chr, and_ff, and_qq, and_uc, android, baidu, bb, chrome, edge, firefox, ie, ie_mob, ios_saf, kaios, op_mini, op_mobm, opera, safari, samsung

PositiveSpin: /* Bumbleberry History */

2023-07-23T21:25:45Z

Bumbleberry History

← Older revision		Revision as of 21:25, 23 July 2023
Line 40:		Line 40:
	==bikebike.org==		==bikebike.org==

	===~~Bumbleberry~~ History===		===History===

	bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.		bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.

PositiveSpin: /* As of July 23, 2023 */ Improving dating

2023-07-23T21:00:45Z

As of July 23, 2023: Improving dating

← Older revision		Revision as of 21:00, 23 July 2023
Line 40:		Line 40:
	==bikebike.org==		==bikebike.org==

	===~~As of July 23, 2023~~===		===Bumbleberry History===

	bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.		bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.
Line 52:		Line 52:
	truncate nohup.out -s 0 && nohup sh -c 'cd /home/rails && RAILS_ENV=production bundle exec rake bumbleberry:update && RAILS_ENV=production bundle exec rake assets:precompile && RAILS_ENV=production bundle exec rake assets:clean && kill `cat /home/unicorn/production.pid`; RAILS_ENV=production bundle exec unicorn_rails -E production -D -c /home/rails/config/unicorn.rb && kill `cat /home/unicorn/sidekiq_production.pid`; bundle exec sidekiq -d -C config/sidekiq_production.yml -e production -c 25' &		truncate nohup.out -s 0 && nohup sh -c 'cd /home/rails && RAILS_ENV=production bundle exec rake bumbleberry:update && RAILS_ENV=production bundle exec rake assets:precompile && RAILS_ENV=production bundle exec rake assets:clean && kill `cat /home/unicorn/production.pid`; RAILS_ENV=production bundle exec unicorn_rails -E production -D -c /home/rails/config/unicorn.rb && kill `cat /home/unicorn/sidekiq_production.pid`; bundle exec sidekiq -d -C config/sidekiq_production.yml -e production -c 25' &

			=== As of July 23, 2023 ===
	However, Bumbleberry broke when BikeBike was dockerized, and was updated to more recent and secure Ruby libraries. This means that it no longer updates properly without breaking BikeBike. In the absense of using Bumbleberry directly to update the css, when browser version are identified by BikeBike, if they don't exist in /public/stylesheets/* the browser renders a responsive view, which doesn't look right for normal size screens.		However, Bumbleberry broke when BikeBike was dockerized, and was updated to more recent and secure Ruby libraries. This means that it no longer updates properly without breaking BikeBike. In the absense of using Bumbleberry directly to update the css, when browser version are identified by BikeBike, if they don't exist in /public/stylesheets/* the browser renders a responsive view, which doesn't look right for normal size screens.

PositiveSpin: /* Bumbleberry & CSS issues (resolved) */

2023-07-23T20:58:27Z

Bumbleberry & CSS issues (resolved)

← Older revision		Revision as of 20:58, 23 July 2023
Line 48:		Line 48:
	====Bumbleberry & CSS issues (resolved)====		====Bumbleberry & CSS issues (resolved)====

	Bumbleberry is a chunk of code (Ruby Module?) that tries to generate CSS suitable for whatever browser the viewer is using. It was a great idea ten years ago, but not so necessary now, and it needs to be manually updated every time a new browser version is released. At DigitalOcean we updated with a cron job:		Bumbleberry is a chunk of code (Ruby Module) that tries to generate CSS suitable for whatever browser the viewer is using. It was a great idea ten years ago, but not so necessary now, and it needs to be manually updated every time a new browser version is released. At DigitalOcean we updated with a cron job:

	truncate nohup.out -s 0 && nohup sh -c 'cd /home/rails && RAILS_ENV=production bundle exec rake bumbleberry:update && RAILS_ENV=production bundle exec rake assets:precompile && RAILS_ENV=production bundle exec rake assets:clean && kill `cat /home/unicorn/production.pid`; RAILS_ENV=production bundle exec unicorn_rails -E production -D -c /home/rails/config/unicorn.rb && kill `cat /home/unicorn/sidekiq_production.pid`; bundle exec sidekiq -d -C config/sidekiq_production.yml -e production -c 25' &		truncate nohup.out -s 0 && nohup sh -c 'cd /home/rails && RAILS_ENV=production bundle exec rake bumbleberry:update && RAILS_ENV=production bundle exec rake assets:precompile && RAILS_ENV=production bundle exec rake assets:clean && kill `cat /home/unicorn/production.pid`; RAILS_ENV=production bundle exec unicorn_rails -E production -D -c /home/rails/config/unicorn.rb && kill `cat /home/unicorn/sidekiq_production.pid`; bundle exec sidekiq -d -C config/sidekiq_production.yml -e production -c 25' &

PositiveSpin: /* MediaWiki */ Improving the mediawiki instructions

2023-07-23T20:57:46Z

MediaWiki: Improving the mediawiki instructions

← Older revision		Revision as of 20:57, 23 July 2023
Line 27:		Line 27:
	* Settings for Mediawiki are in /home/bikebike/docker/bikecollectives/LocalSettings.php		* Settings for Mediawiki are in /home/bikebike/docker/bikecollectives/LocalSettings.php
	* Extensions are in the container at /var/www/html/w/extensions		* Extensions are in the container at /var/www/html/w/extensions
	* ~~I think to~~ make changes happen you ~~have to rebuild and restart the container with <code>docker compose build</code> &~~ <code>docker compose up -d</code> in the /home/bikebike/docker/bikecollectives directory		* To make changes happen after editing, you issue a<code>docker compose up -d</code>in the /home/bikebike/docker/bikecollectives directory
	* The yellowish box at the top of the wiki can be edited at [[MediaWiki:Sitenotice]]		* The yellowish box at the top of the wiki can be edited at [[MediaWiki:Sitenotice]]

Line 36:		Line 36:
	* edit ~/docker/bikecollectives/default.conf		* edit ~/docker/bikecollectives/default.conf
	* I used [https://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rewrite rewrite] directives in the relevant server sections, but I think return directives would also work.		* I used [https://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rewrite rewrite] directives in the relevant server sections, but I think return directives would also work.
	* <code>docker compose build</code> & <code>docker compose up -d</code>		* <code>docker compose build</code> (because default.conf is copied over to nginx) and a <code>docker compose up -d</code>

	==bikebike.org==		==bikebike.org==

PositiveSpin: /* bikecollectives.org */ Bringing this closer to current events. :)

2023-07-23T20:49:40Z

bikecollectives.org: Bringing this closer to current events. :)

← Older revision		Revision as of 20:49, 23 July 2023
Line 7:		Line 7:
	Hosted on: RackNerd		Hosted on: RackNerd

	Services ~~hosted~~ include:		Services are run with Docker containers, and include:

	* bikecollectives.org front page		* [https://github.com/nginx-proxy/nginx-proxy Automated Nginx reverse proxy] with [https://github.com/nginx-proxy/acme-companion automated letsencrypt certificates].
			*Mail stack with [https://docker-mailserver.github.io/docker-mailserver/latest/ docker-mailserver]
			*bikecollectives.org front page
			*BikeBike.org - running/maintained/developed as a [https://git.bikeshopi.dev/bike/BikeBikeBike docker service].
	* Bike Collectives Wiki (MediaWiki)		* Bike Collectives Wiki (MediaWiki)
	* lists.bikecollectives.org (MailMan3 email lists, including The ThinkTank)		* lists.bikecollectives.org (MailMan3 email lists, including The ThinkTank)
	* RoundCube email for tech administrative mail (e.g. DMARC reports)		* RoundCube email client for tech administrative mail (e.g. DMARC reports)
	* ~~restik~~ backup		* Restic backup
	* PassBolt password manager for administrative logins		* PassBolt password manager for administrative logins
	* some other things		*Apprise - push notifications
			*Ofelia - job scheduling
	~~All services are running in Docker containers~~, ~~with nginx-proxy routing requests.~~		* some other things, and more coming!

	[[User:PositiveSpin\|Jonathan Rosenbaum]] and [[User:DarinWick\|Darin April Wick]] have shell accounts; contact them if you need access.		[[User:PositiveSpin\|Jonathan Rosenbaum]] and [[User:DarinWick\|Darin April Wick]] have shell accounts; contact them if you need access.
Line 37:		Line 40:
	==bikebike.org==		==bikebike.org==

	===As of 2023===		===As of July 23, 2023===

	bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.		bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.
Line 43:		Line 46:
	Here are some notes on working with the existing bikebike.org: https://www.bikecollectives.org/wiki/Tech_Meeting_2022.07.16		Here are some notes on working with the existing bikebike.org: https://www.bikecollectives.org/wiki/Tech_Meeting_2022.07.16

	====Bumbleberry & CSS issues====		====Bumbleberry & CSS issues (resolved)====

	Bumbleberry is a chunk of code (Ruby Module?) that tries to generate CSS suitable for whatever browser the viewer is using. It was a great idea ten years ago, but not so necessary now, and it needs to be manually updated every time a new browser version is released. ~~Ideally~~ we~~'d put this on~~ a cron job ~~or just switch to static CSS, but for now, when it breaks, it can be fixed by logging into a shell account on bikebike.org and running...~~		Bumbleberry is a chunk of code (Ruby Module?) that tries to generate CSS suitable for whatever browser the viewer is using. It was a great idea ten years ago, but not so necessary now, and it needs to be manually updated every time a new browser version is released. At DigitalOcean we updated with a cron job:

	truncate nohup.out -s 0 && nohup sh -c 'cd /home/rails && RAILS_ENV=production bundle exec rake bumbleberry:update && RAILS_ENV=production bundle exec rake assets:precompile && RAILS_ENV=production bundle exec rake assets:clean && kill `cat /home/unicorn/production.pid`; RAILS_ENV=production bundle exec unicorn_rails -E production -D -c /home/rails/config/unicorn.rb && kill `cat /home/unicorn/sidekiq_production.pid`; bundle exec sidekiq -d -C config/sidekiq_production.yml -e production -c 25' &		truncate nohup.out -s 0 && nohup sh -c 'cd /home/rails && RAILS_ENV=production bundle exec rake bumbleberry:update && RAILS_ENV=production bundle exec rake assets:precompile && RAILS_ENV=production bundle exec rake assets:clean && kill `cat /home/unicorn/production.pid`; RAILS_ENV=production bundle exec unicorn_rails -E production -D -c /home/rails/config/unicorn.rb && kill `cat /home/unicorn/sidekiq_production.pid`; bundle exec sidekiq -d -C config/sidekiq_production.yml -e production -c 25' &

	~~As of 2023~~.05.~~02,~~ the ~~above is now scheduled~~ to ~~run daily at midnight (Pacific Time~~, ~~I think?). It is~~ a ~~cron job in root~~'~~s crontab~~.		However, Bumbleberry broke when BikeBike was dockerized, and was updated to more recent and secure Ruby libraries. This means that it no longer updates properly without breaking BikeBike. In the absense of using Bumbleberry directly to update the css, when browser version are identified by BikeBike, if they don't exist in /public/stylesheets/* the browser renders a responsive view, which doesn't look right for normal size screens.

	~~====email issues====~~		Godwin recommended using the most recent css for the newer versions. This works well for modern browsers. To enable this feat, the most recent browsers have to be identified, and the css from the most recent version has to be copied over to the newer version. The irony is we could avoid this exercise, and only support modern browsers with one css file, but in the spirit of browser justice let's not assume obscure browsers are not being used anymore.

	~~Sometimes bikebike.org fails to send emails.~~ The ~~first thing~~ to ~~check is <code>/home/rails/log/unicorn.log</code>;~~ if ~~there is~~ a ~~line that says <code>Net::SMTPAuthenticationError (534-5.7.9 Please log in~~ with ~~your web browser and then try again~~. ~~Learn more at):</code> then you need to contact Godwin and ask him to log in~~ to the ~~gmail account that bikebike uses for its smtp server. (we're planning to move to our own smtp server soon~~, ~~which should resolve this.~~		The only disadvantage to this approach would be if a new browser with unknown css arose. Fortunately, this probably won't be an issue for a long time to come, since new browsers projects almost always adopt the identity of a major engine: and_chr, and_ff, and_qq, and_uc, android, baidu, bb, chrome, edge, firefox, ie, ie_mob, ios_saf, kaios, op_mini, op_mobm, opera, safari, samsung

			If a new engine does arise, we will deal with that issue when it occurs.
	==email accounts==		==email accounts==

Angel: sort by year

2023-07-23T18:20:59Z

sort by year

← Older revision		Revision as of 18:20, 23 July 2023
Line 3:		Line 3:
	==bikecollectives.org==		==bikecollectives.org==

	As of 2023~~...~~		===As of 2023===

	Hosted on: RackNerd		Hosted on: RackNerd
Line 21:		Line 21:
	[[User:PositiveSpin\|Jonathan Rosenbaum]] and [[User:DarinWick\|Darin April Wick]] have shell accounts; contact them if you need access.		[[User:PositiveSpin\|Jonathan Rosenbaum]] and [[User:DarinWick\|Darin April Wick]] have shell accounts; contact them if you need access.

	===MediaWiki===		====MediaWiki====
	* Settings for Mediawiki are in /home/bikebike/docker/bikecollectives/LocalSettings.php		* Settings for Mediawiki are in /home/bikebike/docker/bikecollectives/LocalSettings.php
	* Extensions are in the container at /var/www/html/w/extensions		* Extensions are in the container at /var/www/html/w/extensions
Line 27:		Line 27:
	* The yellowish box at the top of the wiki can be edited at [[MediaWiki:Sitenotice]]		* The yellowish box at the top of the wiki can be edited at [[MediaWiki:Sitenotice]]

	=== URL Rewrites ===		==== URL Rewrites ====
	A few notes from adding URL rewrites to the nginx config in April 2023 so that bikecollectives.org/en-es and bikecollectives.org/es-en both redirect to the [[Language Exchange]] page for easier posting on social media, etc.		A few notes from adding URL rewrites to the nginx config in April 2023 so that bikecollectives.org/en-es and bikecollectives.org/es-en both redirect to the [[Language Exchange]] page for easier posting on social media, etc.

Line 37:		Line 37:
	==bikebike.org==		==bikebike.org==

	As of 2023~~...~~		===As of 2023===

	bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.		bikebike.org hosts a Ruby on Rails application that helps with registration for Bike!Bike! conferences. It's old and fragile and we've duct-taped some stuff on to keep it going and make it work for Bike!Bike! Everywhere! virtual conferences, but it is still the best thing we have for the purpose. It has the excellent feature of being trilingual (EN/ES/FR) by design on the frontend, though the backend administrative interface is English-only.
Line 43:		Line 43:
	Here are some notes on working with the existing bikebike.org: https://www.bikecollectives.org/wiki/Tech_Meeting_2022.07.16		Here are some notes on working with the existing bikebike.org: https://www.bikecollectives.org/wiki/Tech_Meeting_2022.07.16

	===Bumbleberry & CSS issues===		====Bumbleberry & CSS issues====

	Bumbleberry is a chunk of code (Ruby Module?) that tries to generate CSS suitable for whatever browser the viewer is using. It was a great idea ten years ago, but not so necessary now, and it needs to be manually updated every time a new browser version is released. Ideally we'd put this on a cron job or just switch to static CSS, but for now, when it breaks, it can be fixed by logging into a shell account on bikebike.org and running...		Bumbleberry is a chunk of code (Ruby Module?) that tries to generate CSS suitable for whatever browser the viewer is using. It was a great idea ten years ago, but not so necessary now, and it needs to be manually updated every time a new browser version is released. Ideally we'd put this on a cron job or just switch to static CSS, but for now, when it breaks, it can be fixed by logging into a shell account on bikebike.org and running...
Line 51:		Line 51:
	As of 2023.05.02, the above is now scheduled to run daily at midnight (Pacific Time, I think?). It is a cron job in root's crontab.		As of 2023.05.02, the above is now scheduled to run daily at midnight (Pacific Time, I think?). It is a cron job in root's crontab.

	===email issues===		====email issues====

	Sometimes bikebike.org fails to send emails. The first thing to check is <code>/home/rails/log/unicorn.log</code>; if there is a line that says <code>Net::SMTPAuthenticationError (534-5.7.9 Please log in with your web browser and then try again. Learn more at):</code> then you need to contact Godwin and ask him to log in to the gmail account that bikebike uses for its smtp server. (we're planning to move to our own smtp server soon, which should resolve this.		Sometimes bikebike.org fails to send emails. The first thing to check is <code>/home/rails/log/unicorn.log</code>; if there is a line that says <code>Net::SMTPAuthenticationError (534-5.7.9 Please log in with your web browser and then try again. Learn more at):</code> then you need to contact Godwin and ask him to log in to the gmail account that bikebike uses for its smtp server. (we're planning to move to our own smtp server soon, which should resolve this.

DarinWick at 04:24, 30 June 2023

2023-06-30T04:24:55Z

← Older revision		Revision as of 04:24, 30 June 2023
Line 54:		Line 54:

	Sometimes bikebike.org fails to send emails. The first thing to check is <code>/home/rails/log/unicorn.log</code>; if there is a line that says <code>Net::SMTPAuthenticationError (534-5.7.9 Please log in with your web browser and then try again. Learn more at):</code> then you need to contact Godwin and ask him to log in to the gmail account that bikebike uses for its smtp server. (we're planning to move to our own smtp server soon, which should resolve this.		Sometimes bikebike.org fails to send emails. The first thing to check is <code>/home/rails/log/unicorn.log</code>; if there is a line that says <code>Net::SMTPAuthenticationError (534-5.7.9 Please log in with your web browser and then try again. Learn more at):</code> then you need to contact Godwin and ask him to log in to the gmail account that bikebike uses for its smtp server. (we're planning to move to our own smtp server soon, which should resolve this.

			==email accounts==

			===bikebikeeverywhere@gmail.com===

			* Primary email account for all B!B!E! communications
			* Used for many of our online accounts as well (e.g. zoom, discord, domain registrar)
			* Sometimes it's a nuisance to log in to, because gmail gets uncomfortable with logins from lots of different geographical locations and thinks they're spam and asks for confirmation. Confirmation codes usually go to Angel
			* We use it instead of an @bikecollectives.org or @bikebike.org account because (1) it contains a lot of institutional memory for B!B!E! and (2) sometimes bikecollectives and bikebike break down, and gmail is pretty reliable.
			* As of June 2023, forwards all emails to bbe@bikecollectives.org, which can be viewed at [http://chocolate.bikecollectives.org chocolate.bikecollectives.org]

			===bbe@bikecollectives.org===

			* Primary address for automated emails related to tech
			** DMARC reports
			** anything related to mailman (including the ThinkTank mailing list) administration
			** notifications about automated site backups
			* All messages sent to bikebikeeverywhere@gmail.com are forwarded here. If you can't log in to the gmail, this provides a sort of backdoor.