We move robots.txt to custom/ instead of custom/public/ as
custom/public/ is now served at /assets/ via the gitea webserver and we
need robots.txt at the root. Related to this we update image urls to be
prefixed with AssetUrlPrefix in their paths so that if this path changes
against in the future we should automatically accomodate that.
Change-Id: I8ce5fe8ff342617ff156a401be8418d593fd35c4
This has a number of bugfixes and seems like a good intermediate step
before we upgrade to 1.15.x.
Change-Id: If30693a849e34a4eed6fdec09b75c438f815621d
I can not find anywhere we use the logo-*.png files currently in the
gitea public directory. Remove these as they're all trivially
re-created via the SVG if we find we want them.
Similarly I don't see anywhere we use "opendev-icon.svg"; it is the
same as "logo.svg". This is removed.
Move the logo with text "opendev.svg" into the assets bundle (only
user of this I can find is paste.opendev.org).
Also move in the favicon.<png/svg> files
Note all these are copied back into the gitea container at the same
location so nothing will break. However we wish to have the
identified external users not rely on files served as gitea assets as
the new version of gitea will move them.
Change-Id: I4f6c64b4042a3f0a17ce4ee59ee8bd0d61648bcc
To do this we also update jinja-init to bullseye and gitea seems to be
the only user of this image. The impact of this should be fairly self
contained to gitea.
Note this update isn't urgent, but good hygiene. We should coordinate
this update with the 1.15.x gitea upgrade and do them in such a sequence
that we can identify problems easily if they pop up.
Change-Id: Ia0075416a1d8a067cfecd26c03f8db9641cbcb89
This uses the opendev assets bundle image created with
I3166679bde6d771276289b9d32e7e4407957b2f8.
The mount options require using BuildKit, hence the Dockerfile update.
Otherwise conceptually it's fairly simple; copy in the files from the
opendevorg/assets image rather than the file-system.
Change-Id: I36bdc76471eec5380a676ebcdd885a88d3985976
There are no diffs in the template files between v1.14.5 and v1.14.6.
This should be a safe update.
Upstream indicates bugfixes around cancelling batched file catting as
well as security updates around jwt and auth.
Change-Id: I2799c62bb3f1fb5e62fc6e3773ec8b9a38ceddfa
According to upstream gitea nodejs 16 has broken them and there isn't
much they can do other than using nodejs 14 for the moment. Use 14 in
our image builds to keep our dockerfile buildable.
See https://github.com/go-gitea/gitea/issues/16604 for more info.
Change-Id: I143c3e67f354d220614136905e8b598cd6d2ad61
This is a small update to gitea after the previous update. This is
relatively recent and since we had tested the prior upgrade I figured we
can do this as a followup. None of the template files seem to have
deltas between 1.14.4 and 1.14.5 which means if 1.14.4 deploys sanely
then I expect this one will too.
Change-Id: I4472d5973d8104a63f16092a2804fabd3e9fa954
This makes a number of changes and in depth testing is probably
warranted.
* Bump the golang version to 1.16 to match upstream's dockerfile
golang version.
* Bump the nodejs version to latest stable which is v16.x and
consume it from the buster repo since our image is based on buster.
* Bump the gitea version to 1.14.4.
* Rename all of the opendev-.*.png logo files to logo-.*.png as the
names of these files are no longer customizable. The reason for this
is the user settable json manifest has been removed.
* We keep opendev-sm.png because Gerrit apparently loads this?
* Update html templates to be in line with 1.14.4's templates.
* Use the gitea `admin user create` command instead of `admin
create-user`. While I can't find removal or deprecation notices for
the previous command the current docs note you should use the new
version and the old one is failing in CI.
Change-Id: I0a05ebb963cca5be88aeb2f859bfbeefa0f9c8e0
This appears to be a small update of bugfixes. The templates we have
modified in our images have not changed between v1.13.6 and v1.13.7
according to git diff in the go-gitea/gitea repo.
Change-Id: I28a2411e107786c7ff96bd7240f3d15190a88f9e
This picks up a variety of bug fixes and ensures we're keeping up.
The diff of the template files we modify between gitea v1.13.1, v1.13.4,
and v1.13.6 is empty. The diff between our modifications at v1.13.4
looks about how I would expect (implying that v1.13.6 is also fine).
Reviews should double check though.
We also add in setup for the system-config repo on the test gitea as
this will give us something to look at for verification purposes.
Change-Id: Idb3568a9d287a2d46d568ab7d8d3a7108739d23e
This is a private list to contact administrators that is suitable
for raising security concerns. I've stolen the wording from Ian's
similar I886f67d875abd09753511f6c33312cfc5eb62933 docs change.
Change-Id: I7eb094d9fc75494ab33e0b9133fb451724f96dad
Co-Authored-By: Ian Wienand <iwienand@redhat.com>
This change represents a number of edits originally suggested in
review comments on Idaefb41590df24e649a4fd5225cc1078f2903696 as well
as a general re-edit of some of the sections for improved accuracy
and flow.
Change-Id: I2806e8099f44c43c161cac51872a712e8ee128e8
This bumps our golang image up to buster-1.15 from buster-1.14 as gitea
bumps their minimum to 1.13 and I figure we should keep up to date.
The templates are updated to accomodate the new gitea templates. Primary
changes here are removal of icon sizes when specified and using imported
templates to simplify bits of code we weren't changing anyway.
We install openssh-server from buster-backports on our gitea-ssh image.
The reason for this is we pull in gitea's sshd_config from gitea itself
and the updated gitea wants to set options that older openssh in buster
proper doesn't support. Accomodate this with the newer openssh found in
backports.
We add a new favicon.svg to override the new default gitea svg favicon
which is served otherwise.
One other thing to call out is that gitea 1.13.0 added support for
kanban and similar project management tooling. We have explicitly
disabled this along with the wiki, issues and pull requests via
app.ini's repository.DISABLE_REPO_UNITS setting. You can find out more
about this setting here:
https://docs.gitea.io/en-us/config-cheat-sheet/#repository-repository
Change-Id: I4c483f90c7495ee1f80eacd2c79c38836aa6f483
Update the contents for https://opendev.org/ default index page,
to be less of a transition explanation for existing OpenStack
infrastructure users, and more of an introduction for new users.
In particular:
- prominently display links to main opendev services
- explain what Opendev is and why we do it
- detail differences to expect from other development platforms
Change-Id: Idaefb41590df24e649a4fd5225cc1078f2903696
This is an incredibly minor update and the templates don't seem to
change at all. But its still a good idea to keep up as much as possible.
Change-Id: I7afcd741bfea056f34dacca65512c86949539340
This includes a number of bugfixes. The most important for us likely
being one that allows you to create a repo with a HEAD set to something
other than master, https://github.com/go-gitea/gitea/pull/12182.
I didn't see any template deltas.
Change-Id: I45fdbf22fb1749d966fc5f6f457e89d40efe5949
This improves the comments around why we've cleaned up some repo
functionality and also removes the activity button. The activity data
gitea is aware of is not a complete picture and is likely to be
misleading. Avoid misleading people by removing that button.
Change-Id: If7546f95421efdd897f2949e4f89a08d53289ce8
Gitea 1.12.0 brings much improved git repo performance. Specifically it
caches the most recent commits helping the web views render much more
quickly.
This bumps our golang base image to 1.14-buster as gitea has changed
their default golang verison to 1.14. We also add gnupg to the package
install list as the upstream images did this.
In the templates I've tried to comment out rather than remove content
that we don't want exposed. The reason for this is it makes resolving
future template updates simpler.
For v1.12.0 release notes see:
https://github.com/go-gitea/gitea/blob/v1.12.0/CHANGELOG.md
Change-Id: I8fd6587c8962554023d878266055a2bd9d2499f9
In the 'Join Us' section of the OpenDev home page, OpenDev is
spelt with a lower case 'd'. This commit correctly capitalizes it.
Change-Id: I8d10cdbc89d9e509fa0c688345f5f462ccb539e6
We can link to etherpad.opendev.org now. This is the second to last
mention of openstack.org on opendev.org.
Change-Id: Ie50cf692c5a5cec2f6a6b19d026913d61e0b95e8
Folks looking at the contact section of our Web site may want to
subscribe to the mailing lists we mention there, so provide handy
hyerlinks enabling them to do that. Also add a link to the IRC
channel logs (partly to balance out the bullet list).
Change-Id: Ib3a1ca47b794f84029b3aff43c7a284fc470b7f1
The OpenDev community is moving its discussions off the old
openstack-infra mailing list, so make sure to refer to the correct
new address(es).
Change-Id: I558b60ea0aa3421285d46be449f04198441cf285
We recently added a "Get started" link to Gitea, pointing to the
generic Developer's Guide. Now that the content is split between
"Getting started" and the reference "Developer's Guide", point
to Getting started content instead.
This should be a lot less intimidating for our new users.
Depends-On: https://review.opendev.org/715961
Change-Id: Ifa496bc8de1a6a39d7b52363db3ab49b8175ed9a
These render as "help" links in the UI and for most of our users will
just be an attractive nuisance since we don't manage accounts and repos
and such directly in gitea.
Change-Id: Iea4bd262dd6304bc1d423f1bf23dacc4333f506b
Currently if you end up at opendev.org it isn't clear how to start
contributing code. Add a "Get Started" link to the nav bar header to
will send you to the opendev developer docs.
Note we may want to consider updating the developer docs to be a better
landing page or even create a new doc for that, but this is a start.
Change-Id: Iee43e2552c1be2e4cd46f43f050e476f140530ad
We seem to semi regularly get questions about why we don't use features
like Gitea's issue tracker and wiki. Add that to the opendev.org front
page FAQ.
Change-Id: Ie5c4602741dcdb9cc4e87b9286a8f6b8b7ed7934
Upstream stopped running make generate in order to fix their static file
builds [0]. Our static file builds have stopped working with our bump to
1.11.3. Apply the corresponding fix to our dockerfile.
Note that we also use clean-all instead of clean to be sure we clean all
the js and css files first.
[0] 48be1889cd (diff-3254677a7917c6c01f55212f86c57fbf)
Change-Id: I40f0449ae29e185ba7082f2f5a27dc96acf58e31
With the move from OpenStack governance to our own OpenDev team, we
should also move to use the #opendev IRC channel in preference to
the #openstack-infra channel which will remain in use for OpenStack
specific discussions.
Update the references in our docs accordingly.
Change-Id: I448704f5d2664fd233a69a2ad12578ca24d9878a
