Skip to content

Cleanup version handling and deployments #134

@mspiekermann

Description

@mspiekermann

Feature Request

Cleanup version handling of Hugo and Docsy and unifying deployments

Which Areas Would Be Affected?

Local and remote deployment of the eclipse-ec-github.io website

Why Is the Feature Desired?

Currently, the steps for local and remote deployments differ. While local deployments use Docker, publishing the website on remote chains multiple Github Actions. This can cause issues due to different versions used for local and remote. For example, the Docker image for local deployment uses an existing Docker image that is regularly updated with new Hugo versions, while remote uses a fixed version (134.1).

Currently, this leads to failed local deployments as the configured Docsy version (0.10.0) is no longer compatible with newer Hugo versions (used by the Docker image).

This also is confusing, as we have different places, where versions can/must be updated to be used in one or the other deployment scenario.

Who will sponsor this feature?

@ndr-brt

Solution Proposal

  • cleanup files (e.g. remove docsy.work, docsy.sum, netlify.toml that come from cp of docsy project)
  • consolidate version handling (shrink package.json to minimum)
  • update docsy version (via go.mod)
  • update publish workflow to use same docker image as local deployments
  • make deployment more flexible (currently base_url is fixed for remote, which is fine for local content tests but not for testing the deployment, e.g. updated hugo/docsy versions)

Metadata

Metadata

Assignees

Labels

dependenciesPull requests that update a dependency fileenhancementNew feature or request

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions