Codeberg documentation content
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2.9 KiB

[{key PushingOutput} {title Pushing output from SSGs into Codeberg Pages} {parent CodebergPages} {author Fayçal Alami Hassani -} {date January 2022} {order 101}]

In case you are using a static site generator (SSG) and that you are satisfied with the result of your project on the local development environment, you can push the files to your Codeberg repository.

To begin with, we will make sure to have two separate repositories, both locally and on Codeberg:

  • A main repository for the source files, i.e. where the source files related to your main project will be located. We will refer to this repository as the source repository. This repository is the one associated with your mydocs folder.

  • A second repository for Codeberg pages, that we will call the pages repository. This repository will only contain the files available in the html folder located under:

(.venv) $ cd docs/build/html

For the purpose of this guide, we have chosen to use two separate folders/repositories. However, you may want to have a different setup that involves creating a submodule instead of having folders and repositories on separate locations. With a submodule, your configuration should look as follows:

├── sources --> This is a git repo
│   ├── build
│   │   └── html
│   │       └── pages --> This is a separate git repo
│   └── content

To copy the content of the html folder to your new pages folder, run the command:

(.venv) $ cp -R docs/build/html/ pages 

We will now initialize an empty repository inside the pages folder. To do so, type the command:

$ git init

To check the status of your project’s files, type the command:

$ git status

To add all the files that are available in your directory to Git, run the command:

$ git add -A

We will then perform a commit with the command:

$ git commit -m "Example message for your commit"

Repeat these steps also in your source folder, then push your local commits to the remote repo with the command:

$ git push origin HEAD:your-remote-branch-name

Replace your-remote-branch-name by the actual name of your remote branch. It is recommended to initially push your commits to a different branch than the master or main branch. Once you have made sure everything went smoothly, you can then make a pull request to merge contents. To learn more about pull requests, read the article Pull requests and Git flow.

You should now be able to visit your content under the following link: https://{user-name} You can find more information in the Codeberg Pages section.