Project

General

Profile

Actions

tickets #162020

open

revisit doc-o-o index page publishing for Leap 16

Added by lkocman 5 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
(Other) Websites
Target version:
-
Start date:
2024-06-10
Due date:
% Done:

0%

Estimated time:

Description

https://github.com/openSUSE/doc-o-o/pull/32

The make upload no longer works as it's expecting user lxbuch on the system
The user / pubkeys for docs team are no longer present on community2.i.o.o, which replaces the old community server.
Georg mentioned we should use jekyl.i.o.o. for any jekyll based builds/deployments.

As of this time (15.6) I simply built the page locally archived _site.tar scp-ed it, and manually extracted it to community2:/srv/www/vhosts-legacy/doc-htdocs under root.

Actions #1

Updated by lkocman 5 months ago

  • Subject changed from revisit doc-o-o index page publishing for Leap 165 to revisit doc-o-o index page publishing for Leap 16
Actions #2

Updated by crameleon 5 months ago

  • Category set to (Other) Websites
  • Private changed from Yes to No
Actions #3

Updated by lkocman 5 months ago

  • Description updated (diff)
Actions #4

Updated by LKucharczyk 5 months ago

lkocman wrote:

https://github.com/openSUSE/doc-o-o/pull/32

The make upload no longer works as it's expecting user lxbuch on the system
The user / pubkeys for docs team are no longer present on community2.i.o.o, which replaces the old community server.
Georg mentioned we should use jekyl.i.o.o. for any jekyll based builds/deployments.

As of this time (15.6) I simply built the page locally archived _site.tar scp-ed it, and manually extracted it to community2:/srv/www/vhosts-legacy/doc-htdocs under root.

How does jekyl.i.o.o work? Are there any docs that would help me set it up?

Actions #5

Updated by cboltz 5 months ago

LKucharczyk wrote in #note-4:

How does jekyl.i.o.o work? Are there any docs that would help me set it up?

The documentation is our salt code - and this comment ;-)

Simplified summary: jekyll.o.o does

  • a git pull to get the latest jekyll repos from github, and then builds the websites with jekyll
  • if the jekyll build succeeded, rsync the website to /srv/www/
  • and of course, there's a webserver (nginx) that serves the websites

If you are interested in technical details, have a look at our salt repo (especially the jekyll_master and web_jekyll roles). Of course, you can also just ask ;-)

To get doc-o-o added, it needs to be added to pillar/role/jekyll_master.sls and pillar/role/web_jekyll.sls.

FYI: we can configure haproxy to route selected subdirectories to a specific server (and already do this for the release notes). Adding another path-specific rule shouldn't be too hard. The haproxy config is also in our salt repo: pillar/cluster/atlas/

Actions

Also available in: Atom PDF