2021-06-29 19:42:47 +00:00
|
|
|
---
|
|
|
|
|
date: "2016-12-01T16:00:00+02:00"
|
|
|
|
|
title: "Install on Cloud Provider"
|
|
|
|
|
slug: "install-on-cloud-provider"
|
2023-04-04 13:47:31 +00:00
|
|
|
weight: 90
|
2021-06-29 19:42:47 +00:00
|
|
|
toc: false
|
|
|
|
|
draft: false
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 03:33:41 +00:00
|
|
|
aliases:
|
|
|
|
|
- /en-us/install-on-cloud-provider
|
2021-06-29 19:42:47 +00:00
|
|
|
menu:
|
|
|
|
|
sidebar:
|
|
|
|
|
parent: "installation"
|
|
|
|
|
name: "On cloud provider"
|
2023-04-04 13:47:31 +00:00
|
|
|
weight: 90
|
2021-06-29 19:42:47 +00:00
|
|
|
identifier: "install-on-cloud-provider"
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Installation on Cloud Provider
|
|
|
|
|
|
|
|
|
|
**Table of Contents**
|
|
|
|
|
|
|
|
|
|
{{< toc >}}
|
|
|
|
|
|
|
|
|
|
## Cloudron
|
|
|
|
|
|
|
|
|
|
Gitea is available as a 1-click install on [Cloudron](https://cloudron.io).
|
|
|
|
|
Cloudron makes it easy to run apps like Gitea on your server and keep them up-to-date and secure.
|
|
|
|
|
|
|
|
|
|
[](https://cloudron.io/button.html?app=io.gitea.cloudronapp)
|
|
|
|
|
|
|
|
|
|
The Gitea package is maintained [here](https://git.cloudron.io/cloudron/gitea-app).
|
|
|
|
|
|
|
|
|
|
There is a [demo instance](https://my.demo.cloudron.io) (username: cloudron password: cloudron) where
|
|
|
|
|
you can experiment with running Gitea.
|
|
|
|
|
|
|
|
|
|
## Vultr
|
|
|
|
|
|
2021-11-28 23:43:18 +00:00
|
|
|
Gitea can be found in [Vultr](https://www.vultr.com)'s marketplace.
|
2021-06-29 19:42:47 +00:00
|
|
|
|
2021-07-24 14:08:23 +00:00
|
|
|
To deploy Gitea to Vultr, have a look at the [Vultr Marketplace](https://www.vultr.com/marketplace/apps/gitea).
|
2021-06-29 19:42:47 +00:00
|
|
|
|
|
|
|
|
## DigitalOcean
|
|
|
|
|
|
2021-07-24 14:08:23 +00:00
|
|
|
[DigitalOcean](https://www.digitalocean.com) has Gitea as droplet in their marketplace.
|
2021-06-29 19:42:47 +00:00
|
|
|
|
2021-07-24 14:08:23 +00:00
|
|
|
To deploy Gitea to DigitalOcean, have a look at the [DigitalOcean Marketplace](https://marketplace.digitalocean.com/apps/gitea).
|
|
|
|
|
|
|
|
|
|
## Linode
|
|
|
|
|
|
|
|
|
|
[Linode](https://www.linode.com/) has Gitea as an app in their marketplace.
|
|
|
|
|
|
|
|
|
|
To deploy Gitea to Linode, have a look at the [Linode Marketplace](https://www.linode.com/marketplace/apps/linode/gitea/).
|
2022-02-18 15:26:00 +00:00
|
|
|
|
|
|
|
|
## alwaysdata
|
|
|
|
|
|
|
|
|
|
[alwaysdata](https://www.alwaysdata.com/) has Gitea as an app in their marketplace.
|
|
|
|
|
|
|
|
|
|
To deploy Gitea to alwaysdata, have a look at the [alwaysdata Marketplace](https://www.alwaysdata.com/en/marketplace/gitea/).
|
