As a test, I tried deleting the folder and installing the plugin anew following the steps in the documentation. The plugin (translator) was displayed correctly but not working for some reason (unable to detect the post language I guess). I finally restored a backup made just before this test.
mononym
Posts
-
Updating Plugins -
Updating PluginsYes. This is the content:
root@973fc516-e3d4-4f67-b18b-3f55c5bd086f:/app/data/plugins/discourse-translator# ls -asl total 3944 4 drwxr-xr-x 11 cloudron cloudron 4096 May 8 2024 . 4 drwxr-xr-x 4 cloudron cloudron 4096 Feb 25 05:03 .. 4 -rw-r--r-- 1 cloudron cloudron 110 May 8 2024 .discourse-compatibility 4 -rw-r--r-- 1 cloudron cloudron 60 May 8 2024 .eslintrc.cjs 4 drwxr-xr-x 8 cloudron cloudron 4096 May 8 2024 .git 4 drwxr-xr-x 3 cloudron cloudron 4096 May 8 2024 .github 4 -rw-r--r-- 1 cloudron cloudron 88 May 8 2024 .gitignore 4 -rw-r--r-- 1 cloudron cloudron 62 May 8 2024 .prettierrc.cjs 4 -rw-r--r-- 1 cloudron cloudron 51 May 8 2024 .rubocop.yml 4 -rw-r--r-- 1 cloudron cloudron 50 May 8 2024 .streerc 4 -rw-r--r-- 1 cloudron cloudron 67 May 8 2024 .template-lintrc.cjs 4 -rw-r--r-- 1 cloudron cloudron 134 May 8 2024 Gemfile 4 -rw-r--r-- 1 cloudron cloudron 1228 May 8 2024 Gemfile.lock 4 -rw-r--r-- 1 cloudron cloudron 1080 May 8 2024 LICENSE 4 -rw-r--r-- 1 cloudron cloudron 227 May 8 2024 README.md 4 drwxr-xr-x 4 cloudron cloudron 4096 May 8 2024 assets 4 drwxr-xr-x 3 cloudron cloudron 4096 May 8 2024 config 4 drwxr-xr-x 3 cloudron cloudron 4096 May 8 2024 db 3668 -rw-r--r-- 1 cloudron cloudron 3755037 May 8 2024 example.gif 4 drwxr-xr-x 5 cloudron cloudron 4096 Feb 8 05:04 gems 4 drwxr-xr-x 3 cloudron cloudron 4096 May 8 2024 lib 4 -rw-r--r-- 1 cloudron cloudron 213 May 8 2024 package.json 8 -rw-r--r-- 1 cloudron cloudron 6541 May 8 2024 plugin.rb 4 drwxr-xr-x 3 cloudron cloudron 4096 May 8 2024 services 12 -rw-r--r-- 1 cloudron cloudron 11777 May 8 2024 setup.png 4 drwxr-xr-x 8 cloudron cloudron 4096 May 8 2024 spec 4 -rw-r--r-- 1 cloudron cloudron 208 May 8 2024 translator.yml 160 -rw-r--r-- 1 cloudron cloudron 161368 May 8 2024 yarn.lock
The issue is exactly the same in the
/app/data/plugins/discourse-data-explorer
directory.FYI, I recently pulled an update for my GravCMS and there
sudo -u www-data git config --add safe.directory <theme/directory>
+sudo -u www-data git pull
worked as expected. -
Updating PluginsSimple git commands (
stauts
&log
, tested with and withoutsudo -u www-data
) give:fatal: detected dubious ownership in repository at '/app/data/plugins/discourse-translator' To add an exception for this directory, call: git config --global --add safe.directory /app/data/plugins/discourse-translator
When trying to solve the ownership with
git config --add safe.directory /app/data/plugins/discourse-translator
(with and withoutsudo -u www-data
) I get :fatal: not in a git directory
In the case of the translator plugin, I could maybe reinstall instead of update. As it is just a connection to a LibreTranslate instance. But that's probably not a solution for other plugins.
-
Updating Plugins@joseph said in Updating Plugins:
/data/
My bad. I was in
app/code/...
. Did not know the plugin exists in both locations.But unfortunately the git command still gives a
fatal: not in a git directory
even in the data subdirectory. -
Updating Plugins@joseph Yes, I'm wondering about the same thing.
root@973fc516-e3d4-4f67-b18b-3f55c5bd086f:/app/code/plugins/discourse-translator# ls -a . .github .template-lintrc.cjs assets lib spec .. .gitignore Gemfile config package.json translator.yml .discourse-compatibility .prettierrc.cjs Gemfile.lock db plugin.rb yarn.lock .eslintrc.cjs .rubocop.yml LICENSE example.gif services .git .streerc README.md gems setup.png
-
Updating PluginsI tried to as well but I get a
fatal: not in a git directory
error when removing the--global
flag. -
Updating PluginsThanks. Unfortunately, I'm already stuck at the git command. I've tried the following:
cd /app/code/plugins/discourse-translator sudo -u www-data git pull # fatal: detected dubious ownership in repository at '/app/data/plugins/discourse-translator' # To add an exception for this directory, call: # git config --global --add safe.directory /app/data/plugins/discourse-translator sudo -u www-data git config --global --add safe.directory /app/data/plugins/discourse-translator # error: could not lock config file /var/www/.gitconfig: Read-only file system sudo -u www-data git config --add safe.directory /app/data/plugins/discourse-translator # without the global flag # fatal: not in a git directory
-
Updating PluginsThanks for the reply. Sounds good. I wonder if I have to repeat the installation procedure just with a pull instead of clone like this :
cd /app/code/plugins/<plugin-repo> # installed plugin directory git config --global --add safe.directory /app/data/plugins/<plugin-repo> # make git work git pull <plugin-repo> # pull instead of clone cd .. # continue with install procedure chown -R cloudron:cloudron <plugin-dir> cd /app/code gosu cloudron:cloudron bundle exec rake plugin:install_all_gems gosu cloudron:cloudron bundle exec rake db:migrate gosu cloudron:cloudron bundle exec rake assets:precompile
or only the pull ?
-
Updating PluginsHello. I want to update the discourse-translator plugin due to coming core changes in Discourse. With v3.4 a banner appeared:
[Admin Notice] One of your themes or plugins needs updating for compatibility with upcoming Discourse core changes. (id:discourse.post-menu-widget-overrides) Identified plugin: 'discourse-translator'
When looking at the plugins (commit hash) in the Discourse admin settings menu, it seems like the plugins do not update automatically.
Is updating plugins identical to installing them ?
-
Dashboard offline but apps not under primary domain runningHa! Maybe I was around just the wrong moment in time. All works fine again and nothing suspicious in the logs.
-
Dashboard offline but apps not under primary domain runningHello. Since this morning (update ?) my Cloudron dashboard indicates the
Cloudron is offline. Reconnecting…
state. All primary domain apps are not reachable but all other apps not located under the primary domain are doing fine.
What steps could I undertake to resolve this ? Thank you -
Auto-tagging ollama setup@girish
Smaller in size than the phi3-mini-4k is llama3.2:1b. -
Grav Git syncI cloned my grav theme repository (https link) into
app/code/user/themes
and use it in one direction only by pulling changes withsudo -u www-data git pull
to update the website.The git-sync extension basically adds (automatic) pushing as well by initializing a git directory in the
app/code/user
directory. -
Theme development workflow ?Yes indeed, that's how I proceeded in the end. It worked fairly well.
BTW, I just came across the remote development feature of the Zed editor (https://zed.dev/docs/remote-development). Don't know if that could work in an app/code/ directory but if, it will make coding Grav easier.
-
Auto-tagging ollama setup@necrevistonnezr
I think that idea is somewhat discussed here: https://forum.cloudron.io/topic/11576/access-ollama-base-url-from-n8n -
Auto-tagging ollama setup@girish
I guess there's a point to package Ollama in the app as that is what the hosted version of Linkwarden does as well. And they also recommend a lightweight model in the docs (phi3:mini-4k
) so there should be no issues with ressources. -
Auto-tagging ollama setupHello. Would be interesting to know if the auto-tagging AI feature (v2.9) is possible on a Cloudron install. And eventually adding the setup process to the docs.
https://docs.linkwarden.app/self-hosting/ai-worker -
Grav Git sync@charlesnw
The webhook is on the gitea side: it triggers the sending of changes to grav when new commits/push occurs. -
Starting issuesWaited for the night and a reboot of the server did the trick. Could even scale the memory back to 2Gb
-
Starting issuesThe app seems to start normally. And starts the checking of the watched websites until this point:
[...] 2024-12-30 21:29:31.529 | INFO | changedetectionio.store:__init__:93 - Tag: c23a2ba5-4b69-4c79-a999-75f9046ad745 events 2024-12-30 21:29:31.530 | INFO | changedetectionio.store:sync_to_json:384 - Saving JSON.. (46) wsgi starting up on http://0.0.0.0:5000 2024-12-30 21:29:31.667 | DEBUG | changedetectionio.flask_app:ticker_thread_check_time_launch_checks:1766 - System env MINIMUM_SECONDS_RECHECK_TIME 3 2024-12-30 21:29:40.633 | INFO | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0. 2024-12-30 21:29:40.633 | INFO | __main__:stats_thread_func:325 - Memory: Used 84.4% (Limit 90%) - Available 125.8MB. [...] (46) accepted ('172.18.0.1', 59538) 2024-12-30 21:31:52.623 | DEBUG | changedetectionio.model.Watch:history:188 - Reading watch history index for ffed72ab-b794-4480-8fe5-386f93606401 [...] 2024-12-30 21:31:53.162 | DEBUG | changedetectionio.model.Watch:history:188 - Reading watch history index for 72e8402e-aec7-413a-be65-352e1ac71608 172.18.20.151,172.18.0.1 - - [30/Dec/2024 21:31:53] "GET /rss?token=a241cfb4fe6a2db2dbe59b627b3299c3 HTTP/1.1" 200 22333 0.575938 (46) accepted ('172.18.0.1', 59552) 172.18.20.151,172.18.0.1 - - [30/Dec/2024 21:31:53] "GET / HTTP/1.1" 302 610 0.002872 (46) accepted ('172.18.0.1', 59560) 172.18.20.151,172.18.0.1 - - [30/Dec/2024 21:31:53] "GET / HTTP/1.1" 302 610 0.002134 2024-12-30 21:32:00.767 | INFO | __main__:stats_thread_func:320 - Connections: Active count 0 of max 10, Total processed: 0. 2024-12-30 21:32:00.768 | INFO | __main__:stats_thread_func:325 - Memory: Used 85.4% (Limit 90%) - Available 124.8MB. [...]