gitlab

!gitlab

@lemmy.world
Create post
www subdomain returns 401 despite using documented DNS settings [Gitlab Pages]

www subdomain returns 401 despite using documented DNS settings [Gitlab Pages]

My Gitlab Pages site works well under domain.com but not under www.domain.com. The www subdomain leads to a 401 message: "You don't have permission to access the resource."

My DNS has a CNAME entry for www pointing to domain.com. When I asked the DNS provider what the problem might be they said "Please contact your hosting provider and provide us with the record needed to be set for www in the DNS zone. The changes should have worked already."

The reason I need this is that some old-school people visiting our website still type www. into the URL bar.

Introducing CI/CD Steps, a programming language for DevSecOps automation

Introducing CI/CD Steps, a programming language for DevSecOps automation

Open link in next tab

Introducing CI/CD Steps, a programming language for DevSecOps automation

https://about.gitlab.com/blog/2024/08/06/introducing-ci-cd-steps-a-programming-language-for-devsecops-automation/

Inside GitLab’s vision for CI/CD programmability and a look at how we simplified workflow automation.

Introducing CI/CD Steps, a programming language for DevSecOps automation
Next-generation GitLab container registry goes GA with 17.3

Next-generation GitLab container registry goes GA with 17.3

Open link in next tab

Next-generation GitLab container registry goes GA

https://about.gitlab.com/blog/2024/07/23/next-generation-gitlab-container-registry-goes-ga/

Starting in GitLab 17.3, GitLab self-managed instances can access the generally available container registry, which features efficient zero-downtime garbage collection and other benefits.

Next-generation GitLab container registry goes GA
GitLab 17.0 has been release

GitLab 17.0 has been release

Open link in next tab

GitLab 17.0 released with generally available CI/CD Catalog and AI Impact analytics dashboard

https://about.gitlab.com/releases/2024/05/16/gitlab-17-0-released/

GitLab 17.0 released with generally available CI/CD Catalog, AI Impact analytics dashboard, hosted runners on Linux Arm, deployment detail pages, and much more!

GitLab 17.0 released with generally available CI/CD Catalog and AI Impact analytics dashboard
A guide to the high-impact breaking changes in GitLab 17.0

A guide to the high-impact breaking changes in GitLab 17.0

Open link in next tab

A guide to the high-impact breaking changes in GitLab 17.0

https://about.gitlab.com/blog/2024/04/10/a-guide-to-the-high-impact-breaking-changes-in-gitlab-17-0/

Find, assess, and mitigate the impact of deprecations and breaking changes in this year’s major release.

A guide to the high-impact breaking changes in GitLab 17.0
run github actions from gitlab

run github actions from gitlab

Open link in next tab

CI/CD Steps | GitLab

https://docs.gitlab.com/ee/ci/steps/index.html#actions

GitLab product documentation.

opentofu component has been published

opentofu component has been published

Open link in next tab

GitLab components / OpenTofu · GitLab

https://gitlab.com/components/opentofu

This project is home to the OpenTofu CI/CD component and it's related assets, like the gitlab-tofu wrapper script and OCI images containing that script together with an OpenTofu...

GitLab components / OpenTofu · GitLab
Introducing the GitLab CI/CD Catalog Beta

Introducing the GitLab CI/CD Catalog Beta

Open link in next tab

Introducing the GitLab CI/CD Catalog Beta

https://about.gitlab.com/blog/2023/12/21/introducing-the-gitlab-ci-cd-catalog-beta/

Discover, reuse, and contribute CI/CD components effortlessly, enhancing collaboration and efficiency when creating pipeline configurations.

Introducing the GitLab CI/CD Catalog Beta
Clarity on environments

Clarity on environments

Hi everyone

I have read through the documentation now several times, and I just want to soundboard something with someone. Regarding the environments we can set up. Is this meant for example as a production cluster and a dev cluster? And if so, is it possible to put a docker swarm cluster in there? I don't see how gitlab will 'know' how to deploy an application to docker swarm? What am I missing? Or am I better off just deploying "manually" via the CI/CD pipeline like I am doing now?

TIA

SOLVED: Using CI/CD Variables in project files

SOLVED: Using CI/CD Variables in project files

Hi community

I have a pipeline where a stack (service) is deployed to my docker swarm. I want to use $CI_PROJECT_NAME in my docker service definition file to define the docker service name. But it seems the variable is not being expanded, or something else is wrong. I need to have a generic yml so I can distribute this to all devs and they don't have to change anything.

Example of what I am trying to achieve:

version: '3.9'
services:
  $CI_PROJECT_NAME:
    image: myregistry/devops1/$CI_PROJECT_NAME/$CI_PROJECT_NAME:latest
    deploy:
      replicas: 3
      endpoint_mode: dnsrr
      update_config:
        parallelism: 1
        delay: 3s
        order: start-first
        failure_action: rollback
        monitor: 1m
      restart_policy:
        max_attempts: 3
      placement:
        max_replicas_per_node: 1
    networks:
      - microservices
    volumes:
      - apache-logs:/var/log/

networks:
  microservices:
    external: true


volumes:
  apache-logs:
    driver: local
    driver_opts:
      o: bind
      device: /mnt/swarm_shared/services/$CI_PROJECT_NAME
      type: none

I know this is not a docker forum, but was thinking the issue is with my pipeline rather than my docker compose file. I would appreciate any help I can get. TIA

EDIT: As per this community post I used a sed replacement command to solve my problem. Ugly, but functional.

Thanks for the input!