Select and provision the machine type most closely matches your needs and budget.Ĭheck both "Allow HTTP" and "Allow HTTPS" when you provision the Compute Engine instance. Compute EngineĬhoose a unique project name and ID for the Compute Engine in your GCP account. UPDATE: The following instructions exist for historical purposes only. Instead, use the following one-script install:ĭISCLAIMER: Following the steps below WILL INCUR CHARGES to your Google Cloud Platform account! However, this page has reached End of Support. post-receive.orig) and replace it with a symlink to /srv/.This documentation describes configuration and deployment steps for Nextcloud on Google Cloud Platform (GCP).Īdapted for Google Cloud Computing (GCP) based on blog post by Carsten Rieger:Ĭarsten Rieger updated new instructions that can be adapted for cloud instances. Mailinglist = Move the old post-receive script out of the way (e.g.
#Collabora code github code#
# on your laptop: (for committers only) review and merge someone else's code (e.g. Git merge upstream/master # this should always be a "fast-forward" merge # on your laptop: (for committers only) once your code is reviewed, merge it # on your laptop: do some work on a new branch, and publish it Git config remote.$OTHERUSER.tagopt -no-tags Git remote add smcv git+ssh://.uk/git/user/$OTHERUSER/telepathy-glib.git # if you are interested in unreviewed code published by other users, e.g. Git remote add upstream ssh:///telepathy/$PROJECT Git clone git+ssh://.uk/home/$USERNAME/public_html/git/$PROJECT.git $PROJECT Git clone -bare git:///telepathy/$PROJECT $PROJECT.git # on dhansak: create your personal repository Replace the values of PROJECT, USERNAME and OTHERUSER as appropriate. (This workflow gives you a personal repository to point people towards for code review, and avoids the problem of accidentally pushing unreviewed changes to the central repository.) If you are not familiar with git, these links might be useful.
See "Working on an existing git repository" below. If you are a developer with an ssh account in the telepathy group and would like to be able to push your changes to the central repository, please clone the main repository on the server to your public_html, to have a public repository of your own, then clone that to your development machine. You can commit changes to your local repository but will not be able to push them to the central repository. Of course, you might prefer to use our Source Code Tarballs.Īnybody can checkout the latest source code anonymously with a command such as the following: git clone git:///telepathy/telepathy-glib If you want bleeding-edge code, (or if you want to help out with development of Telepathy), you can check out the source code from git.