Hello, On Tracim app Github page, instructions to install Tracim with docker, are ending up showing following URL to access app login page : https://localhost:8080. However, this URL is extended with same port number 8080 already in use and serving access to ISPConfig login page : *** TRACIM APP *** Github page : https://github.com/tracim/tracim (please go to : Quick start using docker) Usage demo : https://demo.tracim.fr/ui/login I guess that port 8080 should be kept in use for ISPConfig…, but how to properly configure a different port number so to have it opened and serving access to Tracim app login page ? Regards
No, you can use any (free) port for ISPConfig. Just edit the ispconfig vhost file, change all occurrences of 8080 in it, and restart the web server.
If I am right, you can change port of that app by changing 8080 to desired port when installing it (discussed in here): Code: docker run -e DATABASE_TYPE=sqlite -p 8080:80 -v ~/tracim/etc:/etc/tracim -v ~/tracim/var:/var/tracim algoo/tracim Of course changing ISPConfig port is also possible and ensure you opened the desired port on your server as well. On the other hand, you can surely use proxy.
Last year, I was advised here on this forum, to not install app using docker (see comment 24th Feb 2021 on Github) : https://github.com/tracim/tracim/issues/4208 Therefore I can install Tracim app from source code instead, and then, I may access its login page with URL such as https://localhost:7999. Consequently, I do not any more need to change ISPConfig port 8080 to another port. However, I need help about webroot directories ownership (new thread) : https://forum.howtoforge.com/threads/changing-webroot-directories-ownership.89949/ Thanks
That's not the advice you received last year. I actually told you the exact opposite. I'll quote you the text: Regarding your new question: Each website in ISPConfig has its own user for security reasons, this can not be changed. If you want to get access to a site by SSH, just create a shell user for it in ISPConfig. And if you want to get access to a site by FTP, create an FTP user. And of course, you can create sudo users on any Linux distribution, but this is neither related to ISPConfig nor to the user that owns websites on your server as a sudo user is just a normal Linux user that you configured to be able to become root user.
Hi May informations here below serve, so that one may tell me what path my ispconfig vhost file is under ? OPERATING FRAMEWORK Hosting provider : OVH Machine : remote VPS OS distro : Ubuntu 22.04 LTS SSH user : superuser with sudo rights Panel : ISPConfig 3 (last) CLI terminal : MacBook Air
Ok, so the OS is Ubuntu. But this info does not say which web server type you use, and the location of the vhost file depends on the web server type plus OS. So do you use Apache or Nginx web server?
You're right (sorry), but I have questions that remains, based on this other remark you made : “That's actually a non-issue, as ispconfig and containers do not interfere nor do they have to interact with each other.“ /// 4 QUESTIONS /// Do you mean that containers get installed else where than in ISPConfig file tree ? Where do docker container for Tracim app would then get installed after that command lines below get executed ? Has any one already have knowledge and practice to share about this subject ? Are docker containers resources consuming... ? mkdir -p ~/tracim/etc mkdir -p ~/tracim/var docker run -e DATABASE_TYPE=sqlite -p 8080:80 -v ~/tracim/etc:/etc/tracim -v ~/tracim/var:/var/tracim algoo/tracim source : https://github.com/tracim/tracim
A container is basically a virtual machine. It does not interfere with ISPConfig or the ISPConfig file tree. Google: "Where does docker store containers on Ubuntu":
That's what I answered last year in my explanation of why containers are nice but not necessarily a good idea for hosting environments. You can find the answer here: https://forum.howtoforge.com/thread...ith-container-technologies.86462/#post-418806
I can hear you ! However, I notice that more and more applications are being developed to be installed using Docker containers. Would your advice be to install an application from the source code, when the alternative is proposed?
These containers are mostly provided for dev systems or standalone systems and not for hosting environments. And they are especially useful for software with complex system requirements. Depends on the app and its requirements and also on the complexity of its requirements. It would not make much sense to e.g. install phpmyadmin, WordPress or any other CMS as Docker container on a hosting system while it makes sense to e.g. install GitLab or similar complex software via Docker. It also heavily depends on how you use your server and how many sites you host or in other words if your server has the free resources to run apps via Docker or not.
