gitea
/
blog
41
20
Fork 28
Code Issues 10 Pull Requests 1 Actions Activity

Troubleshooting Gitea upgrades showcase #194

Closed
dachary wants to merge 3 commits from (deleted):wip-troubleshooting into main
pull from: (deleted):wip-troubleshooting
merge into: gitea:main
Conversation 4 Commits 3 Files Changed 1 +58
dachary commented 2022-05-07 17:01:20 +00:00
Contributor
Copy Link
No description provided.
dachary added 1 commit 2022-05-07 17:01:20 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
e0f70f32c6
Troubleshooting Gitea upgrades showcase
6543 reviewed 2022-05-07 18:33:09 +00:00
content/post/troubleshooting-upgrades.md Outdated
@ -0,0 +1,59 @@
---
date: "2022-05-05T12:00:00+00:00"
6543 commented 2022-05-07 18:33:09 +00:00
Owner
Copy Link
-date: "2022-05-05T12:00:00+00:00" 
+date: "2022-05-07T12:00:00+00:00"
```diff -date: "2022-05-05T12:00:00+00:00" +date: "2022-05-07T12:00:00+00:00" ```
dachary marked this conversation as resolved
dachary added 1 commit 2022-05-07 19:26:25 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
231224a291
fix the date
6543 approved these changes 2022-05-07 19:54:20 +00:00
6543 left a comment
Owner
Copy Link

nothing against this ...

nothing against this ...
Gusted reviewed 2022-05-08 03:13:34 +00:00
Gusted left a comment
First-time contributor
Copy Link

Could be just me, but if I read this post without looking at the URL I would rather think this is a Hostea blog post.

Could be just me, but if I read this post without looking at the URL I would rather think this is a Hostea blog post.
content/post/troubleshooting-upgrades.md Outdated
@ -0,0 +23,4 @@
After [upgrading a Gitea intsance from 1.9.6 to 1.16.5](https://discourse.gitea.io/t/blank-page-after-login/5051) the tests conducted manually did not uncover any problem. However, after going to production, some users saw a blank page after login and had to manually type the URL of the project they wanted to see in the browser. The person in charge of the upgrade never had to diagnose Gitea problem and [reached out in the Gitea forum](https://discourse.gitea.io/t/blank-page-after-login/5051).
> **Tip: explain the problem in a public forum as early as possible to get help fro the community**
Gusted commented 2022-05-08 03:11:55 +00:00
First-time contributor
Copy Link

fro -> from

`fro` -> `from`
dachary commented 2022-05-08 06:22:43 +00:00
Author
Contributor
Copy Link

Could be just me, but if I read this post without looking at the URL I would rather think this is a Hostea blog post.

Yes, it's about both Gitea and Hostea. It is a byproduct of the ongoing User Research about Gitea upgrade experiences announced on the Gitea forum a few weeks ago.

> Could be just me, but if I read this post without looking at the URL I would rather think this is a Hostea blog post. Yes, it's about both Gitea and Hostea. It is a byproduct of the ongoing [User Research](https://discourse.gitea.io/t/user-research-about-gitea-upgrade-experiences-call-for-volunteers/5063) about Gitea upgrade experiences announced on the Gitea forum a few weeks ago.
dachary added 1 commit 2022-05-08 06:23:42 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
6e527fbbff
s/fro /from /
lunny requested changes 2022-05-08 13:07:45 +00:00
lunny left a comment
Owner
Copy Link

I don't find enough value of this article from the technical aspect. So I wouldn't like to approve it in the official Gitea blog.

At the end of the article, that's the difference between community support and commercial support. I couldn't say which one is better. Both of them have different users. And even commercial software may also have many bugs. i.e. Windows .

Noticed that you really want Gitea advertise for Hostea. I think the best way is to contribute in https://opencollective.com/gitea . If you become a Gold Sponsor , we could put your logo in Gitea's official website.

But I think it's still welcome to post more valuable technical articles about Gitea.

I don't find enough value of this article from the technical aspect. So I wouldn't like to approve it in the official Gitea blog. At the end of the article, that's the difference between community support and commercial support. I couldn't say which one is better. Both of them have different users. And even commercial software may also have many bugs. i.e. Windows . Noticed that you really want Gitea advertise for Hostea. I think the best way is to contribute in https://opencollective.com/gitea . If you become a Gold Sponsor , we could put your logo in Gitea's official website. But I think it's still welcome to post more valuable technical articles about Gitea.
dachary commented 2022-05-08 14:33:16 +00:00
Author
Contributor
Copy Link

I respect your decision as a Gitea owner and will close this pull request. I also appreciate how delicate it is for a volunteer based project such as Gitea to position itself when it comes to organizations and people trying to derive an income from it.

I think you are not making the right decision and here is why:

  • The article contains valuable technical insights regarding Gitea upgrades that are difficult to find elsewhere
  • The article on fly.io also advertises the benefits of commercial services for Gitea users
I respect your decision as a Gitea owner and will close this pull request. I also appreciate how delicate it is for a volunteer based project such as Gitea to position itself when it comes to organizations and people trying to derive an income from it. I think you are not making the right decision and here is why: * The article contains valuable technical insights regarding Gitea upgrades that are difficult to find elsewhere * The [article on fly.io](https://blog.gitea.io/2022/04/running-gitea-on-fly.io/) also advertises the benefits of commercial services for Gitea users
lunny commented 2022-05-08 16:00:38 +00:00
Owner
Copy Link

I respect your decision as a Gitea owner and will close this pull request. I also appreciate how delicate it is for a volunteer based project such as Gitea to position itself when it comes to organizations and people trying to derive an income from it.

I think you are not making the right decision and here is why:

  • The article contains valuable technical insights regarding Gitea upgrades that are difficult to find elsewhere
  • The article on fly.io also advertises the benefits of commercial services for Gitea users

All the financial transactions with description are open in opencollective. I think all of them are reasonable and necessary to run the services for Gitea and Community.

For the last two questions:

The first one, pull request to document in Gitea is welcome.
The second, that article is totally introducing how to deploy Gitea in fly.io and given the commands and configuration file of the service.

> I respect your decision as a Gitea owner and will close this pull request. I also appreciate how delicate it is for a volunteer based project such as Gitea to position itself when it comes to organizations and people trying to derive an income from it. > > I think you are not making the right decision and here is why: > > * The article contains valuable technical insights regarding Gitea upgrades that are difficult to find elsewhere > * The [article on fly.io](https://blog.gitea.io/2022/04/running-gitea-on-fly.io/) also advertises the benefits of commercial services for Gitea users > All the financial transactions with description are open in opencollective. I think all of them are reasonable and necessary to run the services for Gitea and Community. For the last two questions: The first one, pull request to document in Gitea is welcome. The second, that article is totally introducing how to deploy Gitea in fly.io and given the commands and configuration file of the service.
dachary closed this pull request 2022-05-08 17:08:19 +00:00
dachary commented 2022-05-18 08:14:09 +00:00
Author
Contributor
Copy Link

For the record:

I followed your advice and Hostea is now a Gitea Gold sponsor.

You also suggested:

...pull request to document in Gitea is welcome.

I'm unable to do that primarily because I do not have a GitHub account (and don't want to, their Terms of Service are unacceptable).

For the record: I followed your advice and Hostea is now a Gitea Gold sponsor. You also suggested: > ...pull request to document in Gitea is welcome. I'm unable to do that primarily because I do not have a GitHub account (and [don't want to](https://blog.dachary.org/2018/07/29/why-i-deleted-my-github-account/), their Terms of Service are unacceptable).
All checks were successful
continuous-integration/drone/pr Build is passing
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
6543
lunny
Labels
Clear labels   
in progress

   
kind/bug

   
kind/deployment

   
kind/docs

   
kind/enhancement

   
kind/feature

   
kind/lint

   
kind/proposal

   
kind/question

   
kind/security

   
kind/testing

   
kind/translation

   
kind/ui

   
lgtm/done

   
lgtm/need 1

   
lgtm/need 2

   
priority/critical

   
priority/low

   
priority/maybe

   
priority/medium

   
reviewed/duplicate

   
reviewed/invalid

   
reviewed/wontfix

   
status/blocked

   
status/needs-feedback

   
status/wip
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/blog#194
No description provided.
Delete Branch "(deleted):wip-troubleshooting"

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?