Update from-gogs.en-us.md #42
Conversation
| * cd ~ | ||
| * wget https://github.com/go-gitea/gitea/archive/v1.0.0.zip |
There was a problem hiding this comment.
Please use https://dl.gitea.io as source
| * unzip v1.0.0.zip | ||
| * cp -r gogs gitea | ||
| * If you have custom content migrated from gogs/custom/ folder, like templates or localization files, you should manually merge these because these files changed on Gitea. |
There was a problem hiding this comment.
The custom folder still applies for Gitea, just move gogs/custom/conf (not gogs/custom/conf/app.ini) to gitea/custom/options, this is used to override gitignores, labels, licenses, locales or readmes.
| * cd ~ | ||
| * wget https://github.com/go-gitea/gitea/archive/v1.0.0.zip | ||
| * unzip v1.0.0.zip |
There was a problem hiding this comment.
Not required for the binary from https://dl.gitea.io
| * cp -r gogs gitea | ||
| * If you have custom content migrated from gogs/custom/ folder, like templates or localization files, you should manually merge these because these files changed on Gitea. | ||
| * cp -r gitea-v1.0.0/options gitea/options |
There was a problem hiding this comment.
Not required for the binary from https://dl.gitea.io
| Change gogs specific information: | ||
|
|
||
| FROM: |
There was a problem hiding this comment.
This doesn't format well. Just provide 2 code blocks.
| Verify working by running gitea | ||
|
|
||
| * ~/gitea/gitea web |
| * Enter Gitea admin panel on the UI, run `Rewrite '.ssh/authorized_keys' file` (caution: non-Gitea keys will be lost) and `Rewrite all update hook of repositories` (needed when custom config path is changed). | ||
|
|
||
| Update the gitea-v1.0.0/scripts file for your specific distro and environment then copy. |
There was a problem hiding this comment.
Just refer to https://github.com/go-gitea/gitea/tree/master/scripts because these files are not part of the file on https://dl.gitea.io.
|
Made the changes requested by tboerger, apologies again for the lengthy delay. |
|
conflict |
|
Depricated in favour of #61 ? |
|
Why? 61 is the same thing with less detail from what I can see. Up to you
guys. Let me know.
…On Jan 9, 2017 11:44 AM, "bkcsoft" ***@***.***> wrote:
Depricated in favour of #61 <#61> ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#42 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEklXs5-HfHD_QvdufNvpCOpBwYIe1Dxks5rQo46gaJpZM4LXDQy>
.
|
| @@ -15,12 +15,37 @@ menu: | |||
|
|
|||
| # Upgrade from Gogs | |||
|
|
|||
| If you are running Gogs which version is below 0.9.99, you can upgrade Gogs to Gitea smoothly. There are some steps to do below: | |||
| If you are running Gogs version 0.9.113 or older, you can upgrade Gogs to Gitea smoothly. There are some steps to do below. Make sure to complete as the gitea user in ~: | |||
There was a problem hiding this comment.
I like use git user to complete it. I think We should say non-root user.
There was a problem hiding this comment.
Sounds good, made the change to reflect non-root user, that is more logical
There was a problem hiding this comment.
I added recommendation from pull request #57 as I tested this and upgraded without issue to Gitea v1.0.0. Consensus seems to be this is supported.
| * Copy Gogs `custom/conf/app.ini` to Gitea. | ||
| * Copy Gogs `conf/` to `options/` for Gitea. | ||
| * If you have more custom content on `custom/` folder, like templates or localization files, you should carrefully merge manually because these files changed on Gitea. | ||
| * Copy `data/` folder from Gogs to Gitea. It contains issue attachments and avatars. |
There was a problem hiding this comment.
lunny, I had cp -r gogs gitea that should copy the data/ folder from gogs to gitea. Do you want me to break that out as a separate line?
|
seems conflict with #61 |
|
Looks like #61 has been merged, o well I will try again in the future. Thanks for helping guys! |
|
#61 have been merged to master, this PR targets the release/v1.0 branch. These branches should be properly in sync. |
|
#68 was merged into v1.0 is this dead, should I close? |
|
Please close this one. @termlimit Thanks! |
|
No problem on the close. Good call, between this being first contribution as well as my move and work. Just was unable to provide a resolution in a timely manner. I did learn a lot and I appreciate all the feedback. |
Updated upgrade from gogs instructions. This is for binary, however should work for others as well.