The CLI examples here that used to work - https://docs.cloudron.io/apps/peertube/#cli -
are now different after the v6 update.
instead of "peertube" as the command. It is now the standard "peertube-cli"
This caused me a bit of trauma until I discovered this.
Just wanted to pass this along.
Steve
This looks like a very good project, but it seems that the self hosted version does not allow you to share or even save a project. This renders it as close to useless. Too bad, it is a very nice app other wise.
Back to Draw.io using the "Sketch" theme.
Unless anyone sees a fix to this?
OK again I asked too quickly. You must be logged out for this to work. I was testing sending an invite to myself before I sent them to the rest of the team... All good!
Any Progress on this? It would be a great addition to our toolkit!
Thanks everyone, I will try to tackle this tomorrow, I will be back with questions/feedback.
Any Chance we will see multi-server Cloudron soon? 
This supports Peertube instances with the right settings, I am told. I am going to try to setup a test docker to try.
@fbartels said in Move Chatwoot:
How did the move go?
Well it has not happened yet. The client decided wait until other issues are resolved. But it is still on the roadmap. I will post when it comes back around.
Any updates on this package?
https://github.com/alexta69/metube
https://github.com/alexta69/metube/raw/master/screenshot.gif
Run using Docker
docker run -d -p 8081:8081 -v /path/to/downloads:/downloads ghcr.io/alexta69/metube
Run using docker-compose
services:
metube:
image: ghcr.io/alexta69/metube
container_name: metube
restart: unless-stopped
ports:
- "8081:8081"
volumes:
- /path/to/downloads:/downloads
Configuration via environment variables
Certain values can be set via environment variables, using the -e parameter on the docker command line, or the environment: section in docker-compose.
UID: user under which MeTube will run. Defaults to 1000.
GID: group under which MeTube will run. Defaults to 1000.
UMASK: umask value used by MeTube. Defaults to 022.
DEFAULT_THEME: default theme to use for the ui, can be set to light, dark or auto. Defaults to auto.
DOWNLOAD_DIR: path to where the downloads will be saved. Defaults to /downloads in the docker image, and . otherwise.
AUDIO_DOWNLOAD_DIR: path to where audio-only downloads will be saved, if you wish to separate them from the video downloads. Defaults to the value of DOWNLOAD_DIR.
DOWNLOAD_DIRS_INDEXABLE: if true, the download dirs (DOWNLOAD_DIR and AUDIO_DOWNLOAD_DIR) are indexable on the webserver. Defaults to false.
CUSTOM_DIRS: whether to enable downloading videos into custom directories within the DOWNLOAD_DIR (or AUDIO_DOWNLOAD_DIR). When enabled, a drop-down appears next to the Add button to specify the download directory. Defaults to true.
CREATE_CUSTOM_DIRS: whether to support automatically creating directories within the DOWNLOAD_DIR (or AUDIO_DOWNLOAD_DIR) if they do not exist. When enabled, the download directory selector becomes supports free-text input, and the specified directory will be created recursively. Defaults to true.
STATE_DIR: path to where the queue persistence files will be saved. Defaults to /downloads/.metube in the docker image, and . otherwise.
TEMP_DIR: path where intermediary download files will be saved. Defaults to /downloads in the docker image, and . otherwise.
Set this to an SSD or RAM filesystem (e.g., tmpfs) for better performance
Note: Using a RAM filesystem may prevent downloads from being resumed
DELETE_FILE_ON_TRASHCAN: if true, downloaded files are deleted on the server, when they are trashed from the "Completed" section of the UI. Defaults to false.
URL_PREFIX: base path for the web server (for use when hosting behind a reverse proxy). Defaults to /.
PUBLIC_HOST_URL: base URL for the download links shown in the UI for completed files. By default MeTube serves them under its own URL. If your download directory is accessible on another URL and you want the download links to be based there, use this variable to set it.
HTTPS: use https instead of http(CERTFILE and KEYFILE required). Defaults to false.
CERTFILE: HTTPS certificate file path.
KEYFILE: HTTPS key file path.
PUBLIC_HOST_AUDIO_URL: same as PUBLIC_HOST_URL but for audio downloads.
OUTPUT_TEMPLATE: the template for the filenames of the downloaded videos, formatted according to this spec. Defaults to %(title)s.%(ext)s.
OUTPUT_TEMPLATE_CHAPTER: the template for the filenames of the downloaded videos, when split into chapters via postprocessors. Defaults to %(title)s - %(section_number)s %(section_title)s.%(ext)s.
OUTPUT_TEMPLATE_PLAYLIST: the template for the filenames of the downloaded videos, when downloaded as a playlist. Defaults to %(playlist_title)s/%(title)s.%(ext)s. When empty then OUTPUT_TEMPLATE is used.
DEFAULT_OPTION_PLAYLIST_STRICT_MODE: if true, the "Strict Playlist mode" switch will be enabled by default. In this mode the playlists will be downloaded only if the url strictly points to a playlist. Urls to videos inside a playlist will be treated same as direct video url. Defaults to false .
DEFAULT_OPTION_PLAYLIST_ITEM_LIMIT: Maximum numer of playlist items that can be downloaded. Defaults to 0 (no limit).
YTDL_OPTIONS: Additional options to pass to youtube-dl, in JSON format. See available options here. They roughly correspond to command-line options, though some do not have exact equivalents here, for example --recode-video has to be specified via postprocessors. Also note that dashes are replaced with underscores.
YTDL_OPTIONS_FILE: A path to a JSON file that will be loaded and used for populating YTDL_OPTIONS above. Please note that if both YTDL_OPTIONS_FILE and YTDL_OPTIONS are specified, the options in YTDL_OPTIONS take precedence.
ROBOTS_TXT: A path to a robots.txt file mounted in the container
The following example value for YTDL_OPTIONS embeds English subtitles and chapter markers (for videos that have them), and also changes the permissions on the downloaded video and sets the file modification timestamp to the date of when it was downloaded:
environment:
- 'YTDL_OPTIONS={"writesubtitles":true,"subtitleslangs":["en","-live_chat"],"updatetime":false,"postprocessors":[{"key":"Exec","exec_cmd":"chmod 0664","when":"after_move"},{"key":"FFmpegEmbedSubtitle","already_have_subtitle":false},{"key":"FFmpegMetadata","add_chapters":true}]}'
The following example value for OUTPUT_TEMPLATE sets:
It turns out that the install source folder name needs to be the exact same as destination name inside the plug-in. My folder name plugin-v1.1.0 was the issue. Thanks
when I try to add a team Member - they get the email, but this is what they get...
I have successfully moved whole cloudron setups to other servers, but now I have a different issue.
We have a client that wanted to try chatwoot to see it if worked for them. We spun it up on our Cloudron and set it up with connections to their email. We connect the storage to an s3 bucket in our system. After a few months we find that it works great for them, but now they want to move it to their own cloudron instance/domain. They can keep the data in the same s3, but move everything else.
Is this possible to restore just the Chatwoot App from a backup of the current system to another cloudron on my.cloudron-new.com. ??
They use email connections only and want the conversations to stay intact.
Thanks for any help here..
@nebulon So, I am looking for the web terminal and this file manager. I am sure I am missing something simple.....
Ahh I found them - they are in the app that is installed! Got it!
After trying to use NextCloud (To slow and too much) and xBackbone (s3 is broken) This seems to be perfect for us - simple s3 front-end. I am going to try the docker, but this would be awesome for Cloudron
Hello all, I am excited to try n8n to automate some of our work. I am starting here because this is a Cloudron install of n8n.
I cannot seem to get anything with local files or folders to work. I want to build some watch folder automations.
I cannot get the "local file/folder" trigger to do anything.
or the read write local files to do anything.
I am on windows and the n8n is Cloudron running on a hosted platform.
Any ideas on where to start?
Thanks!
I just signed up for the premium plan. I think Cloudron is pretty cool so far, but I am still trying to figure it out.
I have 2 apps running on a server
hello.example.com & goodbye.example.com
Now I want to add another server with a single app and connect it to the same domain.
3rdapp.example.com
How can I do this?
Surely, I am missing something.
Thanks for the cool product.
I just reinstalled castopod - (I had just started working with it) it seems to be working now. So much for troubleshooting - sorry.
N8N_DEFAULT_BINARY_DATA_MODE=filesystem
@msbt Thanks! so just add "secondaryserver.example.com" during the setup?
Wow, so it is on the roadmap to manage multiple servers from one dashboard? I was not asking about that to be honest - that will be huge!