xaizek / rocketgit (License: AGPLv3+) (since 2018-12-09)
Light and fast Git hosting solution suitable to serve both as a hub or as a personal code storage with its tickets, pull requests, API and much more.
Commit 8d9766033596179b235d6756a0af551a503278f2

Invalid repo path used
Author: Catalin(ux) M. BOIE
Author date (UTC): 2016-09-21 16:54
Committer name: Catalin(ux) M. BOIE
Committer date (UTC): 2016-09-21 16:54
Parent(s): b0b945bb27ce33e5065de0e59aca757b92852c60
Signing key:
Tree: 9a3a7cc06d147fce24c736506d8d2974c8dac2de
File Lines added Lines deleted
scripts/remote.php 2 2
File scripts/remote.php changed (mode: 100644) (index 7267125..5ac629c)
... ... $r = rg_repo_fetch_push_helper($db, $host, $ip, $login_ui, $prefix, $user,
202 202 if ($r['ok'] != 1) if ($r['ok'] != 1)
203 203 fatal($r['error']); fatal($r['error']);
204 204
205 $run = "git-shell -c \"" . $cmd . " " . escapeshellarg($repo_path) . "\"";
206 $run = $cmd . ' ' . escapeshellarg($repo_path);
205 $run = "git-shell -c \"" . $cmd . " " . escapeshellarg($r['repo_path']) . "\"";
206 //$run = $cmd . ' ' . escapeshellarg($r['repo_path']);
207 207 rg_log("Running [$run]..."); rg_log("Running [$run]...");
208 208 rg_prof_start($cmd); rg_prof_start($cmd);
209 209 // TODO: shouldn't we use rg_exec to capture stderr? // TODO: shouldn't we use rg_exec to capture stderr?
Hints

Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://code.reversed.top/user/xaizek/rocketgit

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@code.reversed.top/user/xaizek/rocketgit

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a pull request:
... clone the repository ...
... make some changes and some commits ...
git push origin master