Discourse + ActivityPub plugin
-
There is a new plugin for Discourse that make each category available as an "actor" that can be followed on the fediverse. (NodeBB is also getting there by the way)
so I was wondering if it could be possible to package it by default, so that each server admin could enable it if they wish so ?the plugin dropped on the discourse main forum 8 days ago : https://meta.discourse.org/t/activitypub-plugin/266794
here are the how to install plugins : https://meta.discourse.org/t/install-plugins-in-discourse/19157
here is the code of the plugin itself : https://github.com/discourse/discourse-activity-pubI have not tested this locally or anything, but it appears that the plugin could be packaged and enabled on demand ?
-
So apparently it installs but then, it fails the migration, but I'm not sure it's because of the plugin, I've seen these errors popup when I installed this fresh discourse instance :
for some reasons it fails to connect to the mongodb service or something similar, but again, this was even before touching the plugin install..
something is odd, because this is a fresh install.
still investigatingcd /app/code/plugins git clone https://github.com/discourse/discourse-activity-pub cd /app/code bundle exec rake plugin:install_gems['discourse-activity-pub'] # the line below will force assets to be rebuilt on next application restart rm -rf /run/discourse/public/assets/*
-
Error trace
Caused by: Jun 23 19:59:51 ArgumentError: Unknown migration version "7.0"; expected one of "4.2", "5.0", "5.1", "5.2", "6.0", "6.1" Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration/compatibility.rb:11:in `find' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:567:in `[]' Jun 23 19:59:51 /app/code/plugins/discourse-activity-pub/db/migrate/20230227144934_create_discourse_activity_pub_actors.rb:2:in `<main>' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/loaded_features_index.rb:88:in `register' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/zeitwerk-2.6.0/lib/zeitwerk/kernel.rb:35:in `require' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1045:in `load_migration' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1041:in `migration' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1037:in `disable_ddl_transaction' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1387:in `use_transaction?' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1379:in `ddl_transaction' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1328:in `execute_migration_in_transaction' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1302:in `each' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1302:in `migrate_without_lock' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1251:in `block in migrate' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1401:in `block in with_advisory_lock' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1416:in `block in with_advisory_lock_connection' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:462:in `with_connection' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1416:in `with_advisory_lock_connection' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1397:in `with_advisory_lock' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1251:in `migrate' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1086:in `up' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/migration.rb:1061:in `migrate' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/tasks/database_tasks.rb:237:in `migrate' Jun 23 19:59:51 /app/code/lib/tasks/db.rake:218:in `block (2 levels) in <main>' Jun 23 19:59:51 /app/code/lib/distributed_mutex.rb:33:in `block in synchronize' Jun 23 19:59:51 /app/code/lib/distributed_mutex.rb:29:in `synchronize' Jun 23 19:59:51 /app/code/lib/distributed_mutex.rb:29:in `synchronize' Jun 23 19:59:51 /app/code/lib/distributed_mutex.rb:14:in `synchronize' Jun 23 19:59:51 /app/code/lib/tasks/db.rake:210:in `block in <main>' Jun 23 19:59:51 /app/code/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>' Jun 23 19:59:51 /usr/local/bin/bundle:23:in `load' Jun 23 19:59:51 /usr/local/bin/bundle:23:in `<main>' Jun 23 19:59:51 Tasks: TOP => db:migrate
-
I've checked the full log, since the app install, and even during the installation steps, it was outputting this kind of errors
2023-06-23T14:51:30.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.20.85:80 2023-06-23T14:51:40.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.20.85:80 2023-06-23T14:51:46.000Z > Seeding theme and color schemes 2023-06-23T14:51:50.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.20.85:80
not sure if it's related, but this error keeps going, even tho I managed to login, change root email etc..
-
@rmdes For discourse, I would hold on a bit since it has issue with installing plugins in general. Discourse has moved on to 3.0 and needs redis 7. The new Cloudron releas will bring Redis 7. Our e2e has almost passed, so a Cloudron release will happen soon.