Cloudron Forum

Hard and permanently deleting topics in Discourse is a highly proteced feat.
The instructions say that one must invoke the Rails console and set

SiteSetting.can_permanently_delete = true

See: https://meta.discourse.org/t/introducing-permanently-delete-post-functionality/207109
Not getting this to work - throwing following log:
Is it the read-only!?
Cheers

/home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb/ext/save-history.rb:116:in `initialize': Read-only file system @ rb_sysopen - /home/cloudron/.irb_history (Errno::EROFS)
        from /home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb/ext/save-history.rb:116:in `open'
        from /home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb/ext/save-history.rb:116:in `save_history'
        from /home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb/ext/save-history.rb:60:in `block in extended'
        from /home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb.rb:504:in `block in run'
        from /home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb.rb:504:in `each'
        from /home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb.rb:504:in `run'
        from /home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/irb.rb:421:in `start'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/commands/console/console_command.rb:74:in `start'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/commands/console/console_command.rb:19:in `start'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/commands/console/console_command.rb:106:in `perform'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/thor-1.2.2/lib/thor/command.rb:27:in `run'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/thor-1.2.2/lib/thor/invocation.rb:127:in `invoke_command'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/thor-1.2.2/lib/thor.rb:392:in `dispatch'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/command/base.rb:87:in `perform'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/command.rb:48:in `invoke'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/commands.rb:18:in `<main>'
        from <internal:/home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
        from <internal:/home/cloudron/rbenv/versions/3.2.1/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
        from script/rails:8:in `<top (required)>'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/cli/exec.rb:58:in `load'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/cli/exec.rb:58:in `kernel_load'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/cli/exec.rb:23:in `run'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/cli.rb:492:in `exec'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/cli.rb:34:in `dispatch'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/cli.rb:28:in `start'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/exe/bundle:45:in `block in <top (required)>'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
        from /app/code/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.13/exe/bundle:33:in `<top (required)>'
        from /home/cloudron/rbenv/versions/3.2.1/bin/bundle:25:in `load'
        from /home/cloudron/rbenv/versions/3.2.1/bin/bundle:25:in `<main>'

Disclosure: question may be indicative of a complete lack of knowledge; take it for what it's worth ...

General case: can Cloudron as such be set up so (in very far and inappropriate analogy to mounting a remote volume) that a remote IP can be reached via VPN, Cloudron quasi "acting" (ie the underlying OS providing accessible VPN client software) as a VPN client? Making that IP accessible to all apps within ...

Specific use case: I've got a SQL-database crunching smarthome data running on a dedicated-small-footpring-pc behind my fritz.box router at home. I can get a.) access to that DB from the outside via fritz.box'es own tunneling or b.) set up an OpenVPN server at home and make the PC available via that setup.
Now I would like to connect to that DB using a Cloudron Grafana installation, with Cloudron and Grafana on it being hosted in the cloud far away from home.
Is there a way to get that to work - perhaps it boils down to what one can tell Grafana to do!?

Cheers

Hi there.

• You provide a short how-to on installing plugins for Discourse.
  cd /app/code/plugins
git clone <plugin-repo>
restart
• You also highlight, that installing plugins might break an otherwise healthy installation -> thank God for your excellent back-up features; though you do signal that "official" plugins as you list here should be OK.

There's 1.) a short query on instructions and 2.) a bit of frustration that a random selection of (official) plugin installs (docs, solved, graphviz) lead to Oops. The software powering this discussion forum encountered an unexpected problem.

1. In some previous posts on plugins for Discourse, there were a couple of more lines to the instructions mainly:
   cd /app/code
bundle exec rake plugin:install_gems['REPLACE_WITH_PLUGINS_NAME']
   Have they gone away on purpose?
2. Having attempted to install the docs plugin - it does not crash the system immediately; I do see the options in the admin->plugin section. If I go check to activate the plugin, it goes off to "Oops". For the solved and graphiz plugins: the "Oops" singularity comes about right after the mandatory restart; no accessing the admin->plugin, no accessing the system.

So clearly something is not working here and it might well be my particular installation, albeit it happend dito previously in a prior version; just haven't attempted since systematically. Am up to date on the Discourse version.

Regards and thanks

@girish said in Plugins ...:

Let me test and get back.

Thanks!

@girish : Good morning (CET) - has there been progress made on this topic?
Regards

@ari said in Note on upgrade to Discourse v3.1:

It's wonderful to see the Cloudron packaging updated so quickly after the Discourse release!

Installation version is still 2.8.14. Anything I missed?
Cheers

Ah, OK. So it was not my incompetence ...
And obviously, yeah: it would be cool to get plugins to work.
@jdaviescoates : You point out that

so that all official plugins work!

Am I missing something? My success rate was 0/3 plugins; are there some that do work? Maybe that might be a way of figuring out why others don't ...
Cheers

@girish : Just for my peace of mind - and not wanting to wait for things that might not happen -> will Cloudron be looking into the plugin question?
Thanks and regards

Thanks and Season's Greetings
Regards

Thanks! Will test the official ones I mentioned (i.e. docs, solved, graphviz) ASP.
Cheers

Thank you very much, will look into it.
It's just - I hate the prospect of spending another minute with these back office things ... Oh well.

Can't we just use a Cloudron LAMP stack, install it there and expose it only to the internal Cloudron network for use with Mastodon, Nextcloud, anything?
As with memory requirements: the instructions referenced above -> https://blog.thms.uk/2023/09/mastodon-elasticsearch , point out for smaller purposes = 4GB RAM ...
Cheers