kosmos/gitea.kosmos.org
kosmos/gitea.kosmos.org
Archived
8
1
Fork 0
Code Issues Pull Requests Releases Activity

Add documentation about updating Gitea #13

Merged
raucao merged 2 commits from docs/update into master 2019-01-28 22:42:18 +00:00
Conversation 3 Commits 2 Files Changed 1 +28
greg commented 2019-01-08 11:15:47 +00:00
Owner
Copy Link

TODO:

  • Create an org on Docker Hub (kosmos is already taken and 67p is too short) and use it in the doc

closes #12

TODO: * [x] Create an org on Docker Hub (kosmos is already taken and 67p is too short) and use it in the doc closes #12
raucao reviewed 2019-01-08 23:43:19 +00:00
doc/kubernetes.md
@ -44,0 +52,4 @@
### Unreleased version
This is useful to deploy features that are in master but not yet in a release.
raucao commented 2019-01-08 23:40:25 +00:00
Owner

You mean like gitea/gitea:latest? If we never want to deploy our own code, then we never have to use our own repo afaics. But we do want to be able to deploy our own code.

You mean like `gitea/gitea:latest`? If we never want to deploy our own code, then we never have to use our own repo afaics. But we do want to be able to deploy our own code.
greg commented 2019-01-25 12:22:51 +00:00
Author
Owner

Yes, but a copy of gitea/gitea:latest at the revision we want, instead of always keeping up with their latest. Creating our own images should be a separate issue

Yes, but a copy of `gitea/gitea:latest` at the revision we want, instead of always keeping up with their latest. Creating our own images should be a separate issue
doc/kubernetes.md
@ -44,0 +54,4 @@
This is useful to deploy features that are in master but not yet in a release.
TODO: Create an org on Docker Hub (kosmos is already taken and 67p is too short)
raucao commented 2019-01-08 23:36:25 +00:00
Owner

Pretty sure creating orgs is not part of the update process. This should be done before documenting how to update anything imo.

Pretty sure creating orgs is not part of the update process. This should be done before documenting how to update anything imo.
raucao commented 2019-01-09 07:02:54 +00:00
Owner

Obsolete comment. Already explained in PR description as TODO.

Obsolete comment. Already explained in PR description as TODO.
doc/kubernetes.md Outdated
@ -44,0 +56,4 @@
TODO: Create an org on Docker Hub (kosmos is already taken and 67p is too short)
$ docker pull gitea/gitea
raucao commented 2019-01-08 23:41:55 +00:00
Owner

This is missing the build step for our own image. But also, we should build on Drone CI anyway, as discussed.

This is missing the build step for our own image. But also, we should build on Drone CI anyway, as discussed.
doc/kubernetes.md
@ -44,0 +61,4 @@
$ docker push $ORG/gitea
Set the image for the gitea-server container to `$ORG/gitea:latest`, or run
this command to force a deployment if it is already set to it
raucao commented 2019-01-08 23:42:47 +00:00
Owner

Set the image where? And also why wouldn't we always use the same tag to be deployed; isn't that what they're for? So that we only have to tag an image, not change Kubernetes config?

Set the image where? And also why wouldn't we always use the same tag to be deployed; isn't that what they're for? So that we only have to tag an image, not change Kubernetes config?
raucao commented 2019-01-09 07:03:53 +00:00
Owner

I'd propose a tag like production, similar to the Git tags/branches we're using elsewhere.

I'd propose a tag like `production`, similar to the Git tags/branches we're using elsewhere.
greg commented 2019-01-25 12:29:13 +00:00
Author
Owner

It depends, I think sometimes we'll want to use releases, so official images, and sometimes we'll want an unreleased feature. production tag sounds good

It depends, I think sometimes we'll want to use releases, so official images, and sometimes we'll want an unreleased feature. `production` tag sounds good
raucao commented 2019-01-26 02:20:25 +00:00
Owner

The question about how/where to "set the image to x" is still unanswered by the doc.

The question about how/where to "set the image to x" is still unanswered by the doc.
greg commented 2019-01-28 16:29:33 +00:00
Author
Owner

This is still the old commit because we're commenting on it, new content is:

Change the image for the gitea-server container
(`kubernetes/gitea-server.yaml`) to `gitea/gitea:TAG`, for example:
`gitea/gitea:1.7.0-rc2`
This is still the old commit because we're commenting on it, new content is: ``` Change the image for the gitea-server container (`kubernetes/gitea-server.yaml`) to `gitea/gitea:TAG`, for example: `gitea/gitea:1.7.0-rc2` ```
raucao commented 2019-01-28 22:40:47 +00:00
Owner

Oh, looks like Gitea's "show outdated" thing is not applied correctly then. Thanks.

Oh, looks like Gitea's "show outdated" thing is not applied correctly then. Thanks.
raucao commented 2019-01-09 06:59:11 +00:00
Owner
Copy Link

I just checked again, and contrary to their announcements, Drone 1.0.0 is still RC and the install instructions aren't great yet. But in order to build ourselves, I think we first need to set up a Kosmos Drone CI that all repos/users on this Gitea can use.

So until we have that, I guess local building of images is required.

I just checked again, and contrary to their announcements, Drone 1.0.0 is still RC and the install instructions aren't great yet. But in order to build ourselves, I think we first need to set up a Kosmos Drone CI that all repos/users on this Gitea can use. So until we have that, I guess local building of images is required.
greg commented 2019-01-25 15:23:22 +00:00
Author
Owner
Copy Link

Local building of images is really easy. Clone https://github.com/go-gitea/gitea and run make docker and you get a image tagged gitea/gitea:latest that you can then push. I'm updating the docs

Local building of images is really easy. Clone https://github.com/go-gitea/gitea and run `make docker` and you get a image tagged `gitea/gitea:latest` that you can then push. I'm updating the docs
greg changed title from WIP: Add documentation about updating Gitea to Add documentation about updating Gitea 2019-01-25 15:52:39 +00:00
raucao closed this pull request 2019-01-28 22:42:18 +00:00
raucao deleted branch docs/update 2019-01-28 22:42:26 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
dev environment
Config, builds, CI, deployment, etc.
docs
Documentation
duplicate
This issue or pull request already exists
enhancement
Improving existing functionality
feature
New functionality
idea
Something to consider
invalid
Not a bug
kredits-1
Small contribution
kredits-2
Medium contribution
kredits-3
Large contribution
ops
question
Looking for an answer
security
All your base are belong to us
ui/ux
User interface, process design, etc.
wontfix
This won't be fixed
bug
Something is not working
design
Graphic/visual design
dev environment
Config, builds, CI, deployment, etc.
docs
Documentation
duplicate
This issue or pull request already exists
enhancement
Improving existing functionality
feature
New functionality
good first issue
Dive in, and start contributing
idea
Something to consider
invalid
Not a bug
kredits-1
Small contribution
kredits-2
Medium contribution
kredits-3
Large contribution
on hold
Currently not actionable
ops
Manual IT ops activities
question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
ui/ux
User interface, process design, etc.
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
bkero bumi fsmanuel galfert greg hueso raucao slvrbckt
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/gitea.kosmos.org#13
No description provided.
Delete Branch "docs/update"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?