You can have a jobs with pages: true or name a jobs as pages.
The second part is you need use
pages:
artifacts:
paths:
- public/
If your bundle exec jekyll build -d public is working correctly and the folder/directory is been created, you just are missing the artifacts part. Of course… Answer from gbschenkel on forum.gitlab.com
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages
GitLab Pages | GitLab Docs
Pages also supports websites written directly in plain HTML, CSS, JavaScript, and Wasm. Dynamic server-side processing (like .php and .asp) is not supported. For more information, see Static vs dynamic websites. ... To use GitLab Pages, you must create a project in GitLab to upload your website’s files to.
GitLab Docs
Learn how to use and administer GitLab, the most scalable Git-based fully integrated platform for software development.
Release notes
GitLab release announcements and feature highlights.
Environments
Environments, variables, dashboards, and review apps.
Releases
Releases, versioning, assets, tags, milestones, and evidence.
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › tutorial: create website from scratch
Tutorial: Create a GitLab Pages website from scratch | GitLab Docs
Jekyll uses a destination flag (-d) to specify an output directory for the built website. Add the destination to your .gitlab-ci.yml file: create-pages: script: - gem install bundler - bundle install - bundle exec jekyll build -d public pages: true # specifies that this is a Pages job
How to setup gitlab pages
I’m very new to the gitlab pipeline and I am trying to setup gitlab pages in my repository I followed the gitlab tutorial, plus some google searching Here is my .gitlab-ci.yml default: image: ruby:3.2 before_script: - bundle init - bundle install - gem install bundler - bundle config set ... More on forum.gitlab.com
3
0
March 30, 2025Configuring GitLab Pages Help!
DISCLAIMER: The environment we operated in to get GitLab pages to work may be different than yours in ways I don't know yet so please take this guide with a grain of salt. If you have questions later about our environment, I will try and answer them to the best of my ability. My coworker and I had to setup ... More on reddit.com
1
1
January 8, 2025How to activate Gitlab Pages Properly? - Stack Overflow
The thing is I have 'cloned' the gitlab pages vuepress from examples. Then i have setup gitlab runner and setup the DNS. More on stackoverflow.com
Help needed to set up a GitLab page
The build image is a docker image, and most common images will have access to a shell. You can use a lightweight alpine image, for example. For the second piece, it will publish whatever is in a root directory named “public” so you can simply run a mkdir public and cp XXX as your pages job script. More on reddit.com
2
1
February 23, 202305:26
How to Host a Static Website on GitLab Pages (Beginner Tutorial ...
05:30
Create a static website using GitLab Pages & Web IDE. - YouTube
12:39
HOW TO Build and Host a Static Web Page with GitLab Pages - YouTube
03:25
How to Enable GitLab Pages for GitLab CE and EE - YouTube
14:47
Homelab Series - Creating a Static HTML site in Gitlab Pages Self ...
02:25
Deploying Static Sites with GitLab Pages (it just got a whole lot ...
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › settings
GitLab Pages settings | GitLab Docs
Then the .gitlab-ci.yml example below moves all files from the root directory of the project to the public/ directory. The .public workaround is so cp doesn’t also copy public/ to itself in an infinite loop: create-pages: script: - mkdir .public - cp -r * .public - mv .public public pages: true # specifies that this is a Pages job and publishes the default public directory rules: - if: $CI_COMMIT_BRANCH == "main"
GitLab
docs.gitlab.com › gitlab docs › administer › update your settings › gitlab pages
GitLab Pages administration | GitLab Docs
This setup includes a TLS-terminating classic load balancer that listens for HTTPS connections, manages TLS certificates, and forwards HTTP traffic to the instance. ... Configured wildcard DNS. A TLS-terminating load balancer. To configure wildcard domains with a TLS-terminating load balancer: In /etc/gitlab/gitlab.rb, specify the following configuration: external_url "https://example.com" # external_url here is only for reference pages_external_url 'https://example.io' # Important: not a subdomain of external_url, so cannot be https://pages.example.com pages_nginx['enable'] = true pages_nginx['listen_port'] = 80 pages_nginx['listen_https'] = false pages_nginx['redirect_http_to_https'] = true
GitLab
docs.gitlab.com › gitlab docs › administer › update your settings › gitlab pages › gitlab pages for source installations
GitLab Pages administration for self-compiled installations | GitLab Docs
It is the base for all other setups as described below. NGINX proxies all requests to the daemon. The Pages daemon does not listen to the outside world. ... cd /home/git sudo -u git -H git clone https://gitlab.com/gitlab-org/gitlab-pages.git cd gitlab-pages sudo -u git -H git checkout v$(</home/git/gitlab/GITLAB_PAGES_VERSION) sudo -u git -H make
Gitlab
how-to-stuff.gitlab.io › gitlab-pages-how-to
How To: GitLab Pages - HTML Hosted Page
To do that, we need to add another few lines to our .yml file, telling the Runner to only perform that job called pages (everything in the public directory) on the master branch only - resulting in this: That's all you need to get started! If you're building a more complex example take a look at this article that lists all of the build variables. These variables have already gone through some changes, so it's good to bookmark. ;) Now that we have everything composed, we're ready to push all of the assets we have to our GitLab project.
Medium
medium.com › nerd-for-tech › lets-create-a-website-with-gitlab-pages-4ed9d5860446
Let’s Create a Website with GitLab Pages | by Danielle C. Wormley | Medium
August 4, 2021 - We can simply copy and paste the contents from the “Step 2: Add the configuration file: .gitlab-ci.yml” page. ... Contents needed to create the .yml file for our website project. On the left side of the GitLab project window, you’ll see the options regarding CI/CD.
GitLab
about.gitlab.com › blog › engineering › hosting on gitlab.com with gitlab pages
Hosting on GitLab.com with GitLab Pages
April 7, 2016 - To build our Hexo site, we can start with this .gitlab-ci.yml: ... image: node:4.2.2 pages: cache: paths: - node_modules/ script: - npm install hexo-cli -g - npm install - hexo deploy artifacts: paths: - public only: - main
GitLab
forum.gitlab.com › gitlab ci/cd
How to setup gitlab pages - GitLab CI/CD - GitLab Forum
March 30, 2025 - I’m very new to the gitlab pipeline and I am trying to setup gitlab pages in my repository I followed the gitlab tutorial, plus some google searching Here is my .gitlab-ci.yml default: image: ruby:3.2 before_script: - bundle init - bundle install - gem install bundler - bundle config set path 'vendor' cache: paths: - vendor/ workflow: rules: - if: $CI_COMMIT_BRANCH create-pages: stage: deploy script: - bundle exec jekyll build -d public pages...
Reddit
reddit.com › r/gitlab › configuring gitlab pages help!
r/gitlab on Reddit: Configuring GitLab Pages Help!
January 8, 2025 - - Navigate to where GitLab pages setup is and then edit/add these lines:
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › create deployment for static site
Create a GitLab Pages deployment for a static site | GitLab Docs
Create a GitLab Pages deployment to convert your static site or framework into a website hosted on GitLab. Through a step-by-step form, GitLab: Generates a custom CI/CD configuration based on your project setup.
Nira
nira.com › home › the ultimate manual to gitlab pages
The Ultimate Manual To GitLab Pages - Nira
May 3, 2022 - To use GitLab Pages, you have to first create a project, regardless of whether it’s public, private, or internal, in GitLab to upload your website files. GitLab Pages will always deploy your website from a specific folder called public in your repository.
Publii
getpublii.com › docs › host-static-website-gitlab-pages.html
How to create a static website using GitLab Pages (Full Guide)
August 8, 2024 - The Branch field should contain the name of the branch which will be used to publish your website - you can double-check your repository on Gitlab Pages if you're not sure. In the Token field, enter the access token value that was saved in the first part of this guide. With this done you can click the Save settings button to complete setup, then click the Sync my website button in the left sidebar to initiate the first upload of your website content to the Gitlab repository.
Creoline
help.creoline.com › en › doc › gitlab-pages-ZZtvphZJyN
GitLab Pages
To set up GitLab Pages, log in to the creoline Customer Center and navigate to the GitLab server for which you want to set up GitLab Pages.
Embl-community
grp-bio-it-workshops.embl-community.io › building-websites-with-gitlab › 03-gitlab-pages › index.html
Hosting Pages on GitLab – Building Websites with GitLab
August 2, 2023 - Go to Deploy > Pages. The URL of your website is reported there. It should be: https://<your user name>.embl-community.io/group-website. The screenshot below also contains an interesting alert. Always read this type of messages prompted by the GitLab interface, these are usually relevant to you.
Reddit
reddit.com › r/gitlab › help needed to set up a gitlab page
r/gitlab on Reddit: Help needed to set up a GitLab page
February 23, 2023 -
I'm using GitLab to publish my webdev course projects and I've been using GitLab pages in the past, but the workflow seems to have changed and I need help with the current options.
At Setting > Pages, I am asked to 'Select your build image'. I'm not sure what to check here for a project relying on html, css, and js files. I can't go further with the steps on the page without selecting one.
Afterwards there's the checkbox saying 'The app's built output files are in a folder named "public"'. This sounds ambiguous, as I'm not sure whether leaving the files in the root folder of the project suffices. The project and all its files are public.
Can someone please guide me through the new workflow?