ihorman
commented
3 years ago Hi @xdrew ,
- If you want to bind new domain or replace existing one there is an option in addon's manager that allows to configure extra domains via Let's Encrypt addon.
- The version installed via Marketplace is based on docker-compose so updates should be installed via following way: SSH/WEBSSH: root@node0000 ~/gitlab $ cd /root/gitlab/ root@node0000 ~/gitlab $ docker-compose pull Pulling redis ... done Pulling postgresql ... done Pulling registry ... done Pulling gitlab ... done root@node310004-test-issue11 ~/gitlab $ docker-compose up -d
If you have a specific case when standard flows are not able to cover - please let us know in more details, we will brainstorm together on it.
Cheers,
Hi guys!
Could you please guide me how to customize settings after installation. I want to assing custom domain to my gitlab instance, so I enabled ssl, uploaded certificates, bound domain to load balancer ip and adjusted nginx config to listen to 443 port and use those certificates. Then I changed env variables of Gitlab Server to desired hostname and https_port to 443. But container restart didn't do anything. The best result I managed to get is changing upstream port on nginx to map 443 to 4848. It worked but all internal gitlab links where generated with jelastic domain and port 4848. I suppose its because there's another docker in this container and it's been configured while installation only. Then I tried to redeploy entire Gitlab Server instance with preserve volumes option checked. It made things even worse - internal docker did not start at all. So I have two questions:
Thanks!