How does Cloudron work? What does it do? etc :)
-
@staff is there a handy list of all the addons Cloudron currently has? Ideally with a brief description of what they do/ what they are for? Thanks
-
-
@nebulon said in How does Cloudron work? What does it do? etc
:
@jdaviescoates I rotated the video now and uploaded it to https://videos.cloudron.io/videos/watch/79a34d05-a60b-4ec3-9327-fd736016494c
Just realised you're missing about half an hour on that video!
-
@jdaviescoates Nice catch! You're right, seems to be cut off at the end.
-
@robi indeed, have to see why that happened
So the root cause is that either the video on persicope is cut off or the download from periscope just stops at some point. Not sure, however I wasn't able to fully download it thus far.
-
@nebulon I've got the complete original from periscope if that helps?
When I tried Alltube, it didn't work, but that periscope download link I shared above worked for me.
This one https://pscp.download/?url=https%3A%2F%2Fwww.pscp.tv%2Fw%2F1YqKDBZVqjvJV
-
@jdaviescoates how long is the video length. The one I downloaded (a week ago) directly is 31:26
-
@jdaviescoates Do you think you can upload the have somewhere, so we can download it? I tried periscope again and only got a 30min video.
-
@jdaviescoates I'd suggest a file.pizza link so we can help seed/speed it around.
-
@girish @robi there is clearly something very wrong with the timestamps in the original hence why we've got all these different timing!
Anyways, here is the 295.2MB original I managed to get off Periscope (which says it's 1:16:26 when I open it with VLC):
(well, this is taking forever to process for some reason, so will come back and add the link if it ever finishes)
FilePizza still says processing so here it is via Surfer:
https://files.uniteddiversity.coop/BayLISA_Cloudron.mp4 (although again, something strange about this video as Surfer wont play it when it normally does play videos - plays fine for me in VLC though)And here is a 147.4MB rotated version (using @nebulon's command) which is bizarrely 1:19:24
https://transfer.uniteddiversity.coop/beef/spinach/oregano/broccoli
-
@jdaviescoates thanks, I managed to download the unrotated version. I will try to rotate and upload it now.
-
@jdaviescoates Thanks, file.pizza delivered! I have re-uploaded to https://videos.cloudron.io/videos/watch/206fc4b7-9641-4453-8be0-67450f2574b1
-
@girish I have a small question about this video I've been meaning to ask for ages... somewhere you mention that Cloudron uses "Linux containers" - does that basically just mean Docker? or does Cloudron also use some other form of Linux containerization too? thanks!
-
@jdaviescoates all apps and services use docker for containerization currently. When we started, we had ideas of allow this to maybe change that, as Cloudron acts as an abstraction on top of such lower-level features. In the end so far there was no real reason for supporting other containerization methods. Also it would cause mostly unnecessary extra work for little benefit, still we try to not expose containerization specifics to apps to stay portable as much as possible for the future.
-
@jdaviescoates The linux kernel has various built-in features/system calls like 'cgroups' (provides cpu/ram/resource isolation), namespaces (pid/ipc/mounts), overlay filesystem etc. These things apply to 'process'es.
'Container' is a term and not some feature of the kernel as such. It brings all the above system calls together along with bundling/packaging aspect to help create containerized "apps". Apps can be desktop UI, web apps, daemons, anything.
Docker is one implementation of the 'container' concept. When creating a implementation (just like how you design a language), you have to decide style/structure/format. We have this Dockerfile that explains how to put deps together, how to configure things, how to push the final build image to the cloud and pull down this image and deploy it on another server etc.
Other implementations exist which are in various states - rocket, OpenVZ(?), LXC, snap, containerd, cri-o off my head.
When we started, Docker was the de-facto implementation. These days there are more options and in theory we can switch to another one without affecting end users (though it's a lot of work). Also, when we started, we had no 'custom apps'. Changing the run time will break custom apps, so I think we are married to Docker until that project lives.