Should be fixed with package v1.64.1,

Nice, although I think they missed the mark on the nose color. It should be darker to resemble a nose. [image: GitLab-Logo-Animation-onWhite-500x300.gif] Something more like: [image: 1651083480530-e15770cd-8248-4012-95ae-fe96ff6b1b05-image.png]

@luckow there was a GitLab security update yesterday, this is probably why you got logged out (?). Atleast, I don't see this behavior on git.cloudron.io . In any case, I think the setting you want is in Admin -> Settings -> Account and limit (search for "session") [image: 1646073496947-c9eb5a4d-cde9-49a6-a519-1d6ed8baaa43-image-resized.png]

@roru2k20 I think there is a bug, either in packaging side or GitLab side that the web assets are not cleared on the browser side after an update. This happens on git.cloudron.io as well, so I am keep an eye out.

Thanks @nebulon, I had it configured but it doesn't work. Now for whatever reason it works.

@girish thank you, I'll have a look

Yes, just added the docs section for inbox -https://docs.cloudron.io/apps/#inbox

@brutalbirdie said in migrate gitlab container verion 14.5.1 to an existing gitlab cloudron 14.5.1: so all went well? yes, thank you for answering

@leggias said in Git is not responding: Nov 01 10:57:27 /home/git is not writable. Nov 01 10:57:27 Bundler will use `/tmp/bundler20211101-140-1vd20vb140' as your home directory temporarily. The above is only a warning and not the actual error. Do you see anything more in the logs? You can ignore that warning.

@cloudytech147 you can probably try the GitLab forum - https://forum.gitlab.com/ . This forum is for the Cloudron's GitLab package.

@brutalbirdie thanks! I have merged it but I will move it to a separate Guide doc.

@fbartels Thanks, I read all three article so have a much better understanding now. It seems to me GitLab is a worthy competitor to GitHub and it makes sense I am discovering it now because when I found out Microsoft bought GitHub I knew there would be negative repercussions for developers. If I do hear back from them I would consider doing some technical writer work for them probably. Open source and remote work to me remain key issues to ensure the future of quality software development as it seems GitLab knows this. Thanks again.

@luckow @nebulon Thanks for ur valuable response, I will consider about this...

I noticed someone came along and liked my last post. FYI I am not looking at this as I switched to Gitea + Drone CI

Fix is documented in https://git.cloudron.io/cloudron/gitlab-app/-/issues/13

Someone got autoscaling docker machine working with Gitlab-runner using Sysbox. "The interesting point is that the arguments to use the sysbox runtime are passed in the “--engine-insecure-registry”; this allows additional parameters that docker-machine does not support to be added"

@nj This whole inheritance thing is not ideal I don't like it that you have to copy/paste this whole ldap block. I will rework the package to have the whole gitlab.yml editable via the file manager. That seems more sustainable and puts the onus on us (the packagers) instead of the user (you) to figure out all this yaml complexity.

@girish said in Can we disable the GitLab welcome email or chose a different default address?: @robi That's an innovative solution! Yes, mr. innovation over here I do it professionally.

@girish said in GitLab 1.43.0 Not Responding - key must be 32 bytes or longer: /app/data/secrets.yml Worked thank you