SOGo base image
-
-
@yusf It's not old - nano is not a default package for a small base image in docker, some apps include it, others do not. If you have Linux as your main OS, you can remotely mount the filesystem of an app using SFTP and use nano that way:
http://blog.damontimm.com/how-to-mount-a-sftp-folder-ssh-ftp-on-ubuntu-linux-using-sshfs-fuse/
-
Why should you edit files in the container? Which use case do you have? If you do not have enough experience to use vim, I do not think you are editing things for development reasons (where sometimes you do that to save time if you use your own container images). Docker containers should remain unchanged.
-
@subven said in SOGo base image:
If you do not have enough experience to use vim
Lack of experience with vim ≠ lack of linux and/or development experience. Though I do agree, one should not be messing with a container if one does not have the knowledge to do so. That said, it sounds like OP got the job done that he wanted done.
-
The next base image will include a lot more such helper tools like nano. The current selection is purely based on the taste of tools for Girish and Me, which obviously does not cover a large range of equally useful tools. Only issue is, that we do not update the base image for apps often, since that results in a temporary higher disk usage until all apps have updated, which is just a bit of a risk. Good news is, that we are working on improved disk space tools to be able to stop actions which would result in downtime due to lack of free disk space, once those are done, I guess we can bring the base image up-to-speed as well without the current risk.
-
It's on our roadmap to make a general app file system browser so you can just edit files from the browser itself. @nebulon is working on it already.
-
@girish I have a project I've been working on, and although it doesn't do exactly that, it can modify files in a single containers filesystem:
https://github.com/mitchellurgero/cloudron-codiad
And the code for the webapp:
