Portal

forking

The start your own document compliance portal, based on paxpar, you need to fork our pp-front0 project.

forking

The start your own document compliance portal, based on paxpar, you need to fork our pp-front0 project.

It containes everything you need to start in a minute.

Steps:

  • fork pp-front0 project, choose a project name like pp-front0-sample
  • initial setup
  • first commit
  • set public pages

initial setup

Launch web IDE, edit

  • app.config.ts and adapt the content
  • content/fr/index.yml and adapt the content

TODO: find a way to remove this variable !!

Set a Settings/CI/CD variables SSH_PRIVATE_KEY in the project with a given value

Commit in branch main and wait for the deployment to be done.

Ensure you have access to instance runners to execute the deployment pipeline. (Check Enable instance runners for this project on the Settings/CI/CD page)

To let anyone access your portal, go to Settings/General/Visibility, set Pages to Everyone and click Save.

The deployed URL should appear in the deploy/pages section.

Congratulations, you should be able to browse your site on the URL gitlab assigned to you !

custom domain

How to set up a custom domain ?

Set gitlab pages ... got to deploy/pages, click New domain.

Add your custom domain and modify your DNS entries.

pull from upstream

Describe how to get changes from new version of pp-front0.

git fetch upstream
git switch main
git merge upstream/main
git push

pp-widgets version

Describre how you can easily upgrade/downgrade to a different version of pp-widgets.

Update fork in gitlab