Alright, just for future similar issues,

here is the solution : sudo -u www-data php -f /app/code/occ files:scan "username"

https://docs.cloudron.io/apps/nextcloud/#rescan-files

So I used the cloudron file browser to try and move the "files" folder from my previous user to the newly mapped user folder generated by nextcloud on the new nextcloud instance.

I can login but the files are not present, as if they were never uploaded in the first place.

So basically I have a working nextcloud instance with 30GB of files that I can't see from the nextcloud interface, even tho they are inside the container.

something is missing, this cannot be how I should migrate right ?

@nebulon Yes in both cases it use cloudron users management.

I managed to create a user group and then added this group and their users to the app management itself, I managed to login, but each users has no files, this is like a new nextcloud install, even tho the files, they are inside the container, I can see the files from the Cloudron File explorer, but when I login with the user that was the original owner of these files, there is nothing, but default nextcloud files.

I was about to delete the original app on the original cloudron, but now I'm waiting because I could have lost everything. I'm not sure what I can do next so that all the files are restored to each user, this is worrying.

@nebulon Interesting, because that's exactly the case, but I cannot login, even the original admin account, does not work and the logs are not being particularly useful.

I simply installed Nextcloud on the other cloudron, then I restored the backup using the UI, container setting are the same then the other cloudron, so i'm not sure what I'm doing wrong

@girish does this also apply to NextCloud ?
I have moved my nextcloud app to another cloudron but I can't login anymore and i'm wondering how to recover my access, I still have the old container app running in the old cloudron, but no matter what I try I can't login on the second cloudron using the same credentials, even tho, users match on both side.

Anything I'm missing?

@whitespace have you tried @robi link already ?
deleting the app config files and hitting the save button on the "location" view in the UI to regenerated nginx config for each app ?

@whitespace What does sudo systemctl status nginx says ?

@girish Oh my bad!! I completely missed that !!
thanks a lot for pointing me in the right direction !

@jdaviescoates Yes the plugin works just fine for me !
you can see it at work here : ukrainewararchive.eu/

So just to confirm there is no way to change

From the cloudron package ?

I wish we could set those via an env file like in many other apps

It's a bit sad because this app is really nice but without being able to adapt basic elements to personalize it for the user, it's a bit worthless.

Trying to understand what's the purpose of the admin/pass login for this feature, anyone knows ?

I restarted the app, tried to install again, it works !

@girish

I can't get it to install but something totally weird is happening on my instance, since last month, since I the last time I came here, my instance is auto uploading the target channel I initially managed to configure but it does not make sense because the plugin is not installed...??.?

log file : https://paste.armada.digital/cageyixumu.md

I don't have any LDAP errors, I'm wondering if this is even related?

@girish on the Administration plugin/theme view

Using default Peertube cloudron package.

@BrutalBirdie Sorry have been busy and thanks for documenting my steps

The docker part is done on the /etc/crowdsec/acquis.yml
I'm not entirely convinced my regex call works appropriately
or even that in the cloudron context this is entirely needed (I have one cloudron with & without not seeing much difference)

# Docker context
source : docker
container_name_regexp:
  - ^[a-zA-Z0-9_.-]*$
labels:
  type: log_type
---

@nebulon from what I can see here : https://docs.joinpeertube.org/maintain-tools?id=remote-tools
or better here : https://docs.joinpeertube.org/maintain-tools?id=server-tools

There is nothing that indicate how to specify this on the command line.

@nebulon I tried to find this information but up to now I have nothing

So the peertube cli has now a neat feature to remember instances it is being used to upload from the cli :

peertube auth :

add [options] remember your accounts on remote instances for easier use
del <url> unregisters a remote instance
list lists registered remote instances
set-default <url> set an existing entry as default
help [command] display help for command

Examples:

$ peertube auth add -u https://peertube.cpy.re -U "PEERTUBE_USER" --password "PEERTUBE_PASSWORD"
$ peertube auth add -u https://peertube.cpy.re -U root
$ peertube auth list
$ peertube auth del https://peertube.cpy.re

When I try to use it, I get this :

node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^

[Error: ENOENT: no such file or directory, mkdir '/root/.config'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: '/root/.config'
}

Going to try this out now that cron job is integrated in the app on cloudron side.

With the latest version, it seems there is now an 'official' YT plugin to import entire channels from the UI but the plugin crash at install because node is trying to install inside the app/code/server read-only file system.

Do you think this is something that could be fixed in the cloudron package ?

Fresh update with the latest version on a fresh cloudron :

when I follow the doc here : https://docs.cloudron.io/apps/peertube/ to import a video from cli
I get

peertube import --url https://domain.com --username user --password bloodypass --target-url https://www.youtube.com/watch?v=xxxx --tmpdir /tmp

the shell returns this :
--username field is required
--password field is required

Anything changed perhaps for the cli & latest peertube version ?

@girish I don't understand the Deprecation part...

@nj Amazing work !!!

edit : actually it recovered all the workflows, my bad
now I just have to create second user and share workflow with members

/run/discourse/log/unicorn.stderr.log

Passing 'script' command to redis as is; administrative commands cannot be effectively namespaced and should be called on the redis connection directly; passthrough has been deprecated and will be removed in redis-namespace 2.0 (at /app/code/vendor/bundle/ruby/2.7.0/gems/sidekiq-6.3.1/lib/sidekiq/scheduled.rb:45:in `zpopbyscore')

/run/discourse/log/unicorn.stdout.log

Loading Sidekiq in process id 89
2022-03-20T07:55:12.418Z pid=89 tid=cex WARN:

WARNING: Your Redis instance will evict Sidekiq data under heavy load.
The 'noeviction' maxmemory policy is recommended (current policy: 'allkeys-lru').
See: https://github.com/mperham/sidekiq/wiki/Using-Redis#memory

Can't find any hint to help us here on the production.log file

@girish Hard to find something at that location regarding the error but the cloudron container log
have this : Mar 20 08:54:40 2022/03/20 07:54:40 [error] 64#64: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "domain.org"

I'v been testing https://cwtch.im/ it's quite interesting, since you can host the server home
and join other chats/servers or one-to-one over tor

@timconsidine I was thinking Briar like other suggested but also https://cwtch.im/

@nebulon This is a long time running Discourse forum we have, this is after the upgrade.

@girish org.discourse.cloudronapp@1.7.1

Anyone had any issue with Discourse ?

I have a Discourse container that I can't get running again since last upgrade
Logs :
https://paste.armada.digital/okalicopuv.apache

@nebulon Correct, should have done the screenshot before remounting it,
but the state the cloudron rebooted was no backup index and sshfs unmounted.

I got the entire bug all over again after reboot, lost mountpoint and lost index of backups, not sure what I can do to provide more context/log ?

@thetomester13 Oh thanks, exactly what I'm looking for

@robi main domain seems to be dead ?

I stumbled on a Gitea domain with all the non-store app in one place, can anyone provide the link again, I can't find it...:/

@BrutalBirdie from my epxerience, Apps in recovery mode or in any other state than "running" do not get certs or updates.

@andreasdueren I think this covers pretty much the subject : https://cactusautomation.com/blog/how-to-customize-the-design-of-mautic-forms-to-be-less-vanilla/

@girish actually the app seems to be working amazing, the problem in the current ssb eco system "state", if there are issues it's more with the client(s) I think(Manyverse mobile/desktop or Patchfox), sometimes you have to relogin to your pub to see it in your connections list, but beside that (which I think is client related) I'm not seeing any problem so far

the experience on mobile is not there yet, it's slow, keep having to resync with the database, feed does not update, but all of this is local problem in the device, not the go-ssb-server implementation or the docker/cloudron package.

@chetbaker This could be a path to explore outside of a cloudron context, but within cloudron I'm not sure I have the know-how to talk about this, maybe @nebulon can chime in?

@chetbaker I don't think so, better wait for LDAP support cos it will bring you authentication and a closed jitsi server in one shot

@chetbaker both
You can use this approach to create several users/pass allowing other people to join
but the moment you put this in place, you can't access the jitsi without a user/pass

@nebulon Oh thanks, going to test this for one user without any specific nextcloud app installed and see how it goes, should be enough along with reconfiguring his nextcloud local client to the new URL

I'm looking for advice to rationalize my nextcloud usage :

• let's say I have cloud.domain1.com and cloud.domain2.com each with a bunch of users
• let's say I want to reunite them in one nextcloud instance (domain does not matter much)
  each under it's own user stuff correctly moved from another nextcloud.

How do I do this without loosing anything from the users ?

Bonus question - without knowing which nextcloud they may have installed ?

Moving files would be already nice, if I can reinstall the nextcloud builtin app they use manually..

is there a better way to do this ?

This idea would be neat !!

@BrutalBirdie That must have been intense !!

In this example I think there are some ideas that I can take for Tanzawa, mainly
getting the domain used by cloudron into a variable, which would allow the docker image to be agnostic and not tied/built to a specific domain (mine in my case)

i've learned a few stuff packaging go-ssb-rooms, will start from scratch for Tanzawa and hopefully have it working smooth

@robi Actually there is no migration apply, look here : https://github.com/jamesvandyne/tanzawa/issues/179

Surprise : https://github.com/rmdes/go-ssb-room-docker/blob/main/README.md

@girish @nebulon I think we have a new app for cloudron

Hello SSB

From manyverse desktop :

Go-SSB-Room on Coudron:

Invite : https://ssb.armada.digital/join?token=S-PirqYiwqz5I_yk7jL-spmujRmVFFF0IP6blNOMCUb19EvwkjRE_B2-ZI_wg_KLK0E%3D

I'm almost done with it !

• got the sqlite database in /app/data/
• .env file symlink (but can't write to it yet??!!)
• /app/code contains all the code and packaging env

Issues

• I'm not sure what's happening this weekend but my container kept starting in migration loop
• if I recovery into the container and start the python server, all is fine, connected, writable
• when I restart, instead of skipping the steps of migration and start the server, it bootloop in migration, while saying there is no migration to do (obviously, everything is like 1 step before working....Grrrr)

@ocelotsloth a temporary "fix" would be to add a basic auth with .htpasswd authentication
in the nginx conf file of your jitsi app /etc/nginx/applications/

find the name of your nginx conf file with

step 2 and step 3 from here https://www.cyberciti.biz/faq/nginx-password-protect-directory-with-nginx-htpasswd-authentication/ should do the work

beware you're modifying a cloudron generated file that could change later and remove your changes.

Another thing I would like to improve : it seems the sql file is run by root (at least the file is owned by root) I don't think it's a good idea/best practice, so I'm wondering if by running the last command of the start.sh, the python server, with gosu cloudon:cloudron would solve this..

My latest build is at https://hub.docker.com/r/buzzworkers/tanzawa/tags
tag Number 7

You can try it with : cloudron install --image buzzworkers/tanzawa:7 --no-wait

and then cloudron update --image buzzworkers/tanzawa:8 --no-wait --app your.domain.com

why these two tags ?

Because I have not figured out how to do the steps of the README.md (tanzawa repo)
in one single shot and directly boot the python server.

So tag number 7 setup the database correctly (but then stay in migration loop)
and tag8 comment the migration parts (start.sh) so that the server boots

using the web terminal to python3 /app/code/apps/manage.py createsuperuser
to create your admin user.

Dashboard is at your.domain.com/a/
Wordpress import at your.domain.com/wordpress

I would love to have this last steps of the setup completely automated but I lack know-how

SQL path : Yes I have finally made it ! thanks to this https://django-environ.readthedocs.io/en/latest/

but thanks @robi

But I still have a few things blocking me, like, tanzawa need to know the domain it is installed into
and this is configured in the .env file but the thing is I don't want people to have to clone the github repo, add their domain, build, push and install to their cloudron

Ideally I need to add something so that the domain variable is passed to the .env file before it runs the first DB migration (which create the sql file the first time and apply migration the second time)

Also now in the current state of my dockerfile, I have managed to put all the code in /app/code and only the .env and the staticfile & micropub media folder in /app/data/ which is exactly what I wanted...

So this is moving forward..

@andreasdueren I fixed my Mautics instances by checking out the log provided inside the Mautic app, there I found a lot of errors related to theme's I had added manually when Mautic moved from the old email builder to GrapeJS, once the old themes removed, everything went back to normal !

issues I'm having :

the env.sample define an SQLITE database at the root of the image, so I tried to symlink it to /appa/data so that the DB would be backedup but above all writable, the problem is that no matter what I tried, It never worked, in the end my current image has the tanzawa code and the data in the same /app/data space and the only part that works in /app/code is the virtualenv environment used to build the image in the first place.

so the current state of the package is not final, ideally, the entire code should live inside /app/code/ and only staticfiles, media and the SQLite database should be in /app/data/

I tried to find other python packages using sqlite but could find one, so my next step I was thinking of adapting the way the .env defines the variables to build in a way that is closer to how other cloudron packages load environments variables.

I'm also researching for a way to define the sqlite db not from a URL but from a PATH instead, so that I could simple use /app/data/ directly.

if anyone has advice on how to move this forward, I'm taking it

This is the current state of my cloudron package : https://github.com/rmdes/tanzawa

• git clone
• confirm docker login
• docker build -t username/tanzawa:yourtag . --no-cache
• docker push username/tanzawa:yourtag
• cloudron install --image username/tanzawa:yourtag --no-wait

OR if update

• cloudron update --image username/tanzawa:yourtag --no-wait --app your.cloudron.domain

@girish I had to remove old themes I had manually added from Mautic 3.x to regain the ability to edit previous email campaigns, not sure if this is related in any way, but once the offending themes removed, everything went fine !

@micmc the moment I stumbled on the #indieweb wiki/Irc and community I knew I had found the kind of internet I want to help building, it also connected me back to early 2003 when the internet was very different and blogs were powering a lot of different conversations online.

I miss that time and after a few years of using Known (another indieweb ready blog engine) but also testing the WP and Drupal Indieweb implementation I'm convinced that to make it work, the access to deploying indieweb tools should almost be one-click deploy instead of everyone's cooking their own implementation in their corner, I believe that for this to take off and for people to actually use the built-in "social network" already part of the open web, we need to make it really easy to join, deploy and use.

In many ways the indieweb concepts are so simple and elegant that for many people that don't remember or never met the web before the platforms, it all feels really abstract and complicated, i want to help to change that !

My cloudron package is running since a few days and I'm quite happy with it
my next steps should be :

• making the package more alligned with cloudron best practice (have code a data separated)
• talk with upstream to see how we could use progreSQL and Redis addons from cloudron
• finetune some details like a proper logo, description etc..

then it should be ready to be shared with the community