{"id":399982,"date":"2024-06-29T14:59:30","date_gmt":"2024-06-29T14:59:30","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=399982"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=399982","title":{"rendered":"Modern Web-UI for SVN repositories<\/span>"},"content":{"rendered":"
<\/div>\n
\n
\n
\n
\n

cSvn<\/b> \u2014 is a web interface for Subversion<\/b> repositories. cSvn<\/b> is based on CGI script written in \u0421<\/b>. <\/p>\n

<\/p>\n

This article covers installing and configuring cSvn<\/b> to work using Nginx<\/b><\/a> + uWsgi<\/b><\/a>. Setting up server components is quite simple and practically does not differ from setting up cGit<\/b><\/a>. <\/p>\n

<\/p>\n

cSvn<\/b> supports Markdown files that are processed on the server side using the md4c<\/a> library, which has proven itself in the KDE Plasma<\/b> project. cSvn<\/b> provides the ability to add site verification codes and scripts from systems such as Google Analytics<\/em><\/b> and Yandex.Metrika<\/em><\/b> for trafic analysis. Users who wonder to receive donations for his projects can create and import custom donation modal dialogs. <\/p>\n

<\/p>\n

Instead of looking at screenshots, it is better to look at the working site<\/a> to decide on installing cSvn<\/b><\/a> on your own server. <\/p>\n

<\/p>\n

It should be noted that you can browse not only your own repositories, but also configure viewing of third-party resources via HTTPS and SVN protocols. <\/p>\n

<\/a> <\/p>\n

Reqired packages<\/h2>\n

<\/p>\n

cSvn<\/b> depends of following libraries: libpcre2<\/b><\/a>, libmd4c<\/b><\/a>, libmd4c-html<\/b><\/a>, libmagic<\/b><\/a>, and libxml2<\/b><\/a>. <\/p>\n

<\/p>\n

To use cSvn<\/b> a web server must be installed and configured on the system. We recommend the Nginx<\/b><\/a> with uWsgi<\/b><\/a> application server. Of course Apache Subversion<\/b><\/a> SCM system should be installed too. <\/p>\n

<\/p>\n

Installation<\/h2>\n

<\/p>\n

The cSvn<\/b> package consists of two parts. First of which is a regular Linux daemon that is responsible for parsing the configuration file, and the second is a CGI script that responds to HTTP requests. Both parts of the package are installed simultaneously but are maintained independently of each other. <\/p>\n

<\/p>\n

Download Sources<\/h3>\n

<\/p>\n

To obtain sources we have to checkout its from SVN repository<\/a>: <\/p>\n

<\/p>\n

svn checkout svn checkout svn:\/\/radix.pro\/csvn\/tags\/csvn-0.1.2 csvn-0.1.2 <\/code><\/pre>\n
  <\/p>\n
and run the bootstrap script:  <\/p>\n
  <\/p>\n
cd csvn-0.1.2 .\/bootstrap <\/code><\/pre>\n
  <\/p>\n
Also cSvn<\/b> source packages are available for download on the Radix.pro FTP-server<\/a>.  <\/p>\n
  <\/p>\n
Bootstrap Script<\/h4>\n
  <\/p>\n
The bootstrap<\/em> script especialy created for Autotools<\/em> install automation. To install Autotools<\/em> into source directory on build machine (i.e. when build<\/b> == host<\/b>) the bootstrap<\/em> script can be run without arguments.  <\/p>\n
  <\/p>\n
.\/bootstrap <\/code><\/pre>\n
  <\/p>\n
In this case Autotools<\/em> will be installed from current root file system.  <\/p>\n
  <\/p>\n
For the cross environment the —target-dest-dir<\/b> option allows to install some stuff from development root file system:  <\/p>\n
  <\/p>\n
TARGET_DEST_DIR=\/home\/developer\/prog\/trunk-672\/dist\/.s9xx-glibc\/enybox-x2 \\     .\/bootstrap --target-dest-dir=${TARGET_DEST_DIR} <\/code><\/pre>\n
  <\/p>\n
For example, in this case the aclocal.m4<\/em> script will be collected from the
  ${TARGET_DEST_DIR}\/usr\/share\/aclocal<\/em> directory.  <\/p>\n
  <\/p>\n
Configuring Sources<\/h3>\n
  <\/p>\n
.\/configure --prefix=\/usr \\             --sysconfdir=\/etc \\             --with-config=\/etc\/csvnrc \\             --with-controldir=\/etc\/rc.d \\             --with-logrotatedir=\/etc\/logrotate.d \\             --with-scriptdir=\/var\/www\/htdocs\/csvn \\             --with-homedir=\/var\/lib\/csvn \\             --with-logdir=\/var\/log \\             --with-piddir=\/var\/run <\/code><\/pre>\n
  <\/p>\n
Install on the Build Machine<\/h4>\n
  <\/p>\n
make make install <\/code><\/pre>\n
  <\/p>\n
Cross Compilation Example<\/h4>\n
  <\/p>\n
#!\/bin\/sh  TARGET_DEST_DIR=\/home\/developer\/prog\/trunk-672\/dist\/.s9xx-glibc\/enybox-x2 TOOLCHAIN_PATH=\/opt\/toolchains\/aarch64-S9XX-linux-glibc\/1.1.4\/bin TARGET=aarch64-s9xx-linux-gnu  .\/bootstrap --target-dest-dir=${TARGET_DEST_DIR}  PKG_CONFIG=\/usr\/bin\/pkg-config \\ PKG_CONFIG_PATH=${TARGET_DEST_DIR}\/usr\/lib${LIBDIRSUFFIX}\/pkgconfig:${TARGET_DEST_DIR}\/usr\/share\/pkgconfig \\ PKG_CONFIG_LIBDIR=${TARGET_DEST_DIR}\/usr\/lib${LIBDIRSUFFIX}\/pkgconfig:${TARGET_DEST_DIR}\/usr\/share\/pkgconfig \\ STRIP=\"${TOOLCHAIN_PATH}\/${TARGET}-strip\" \\ CC=\"${TOOLCHAIN_PATH}\/${TARGET}-gcc --sysroot=${TARGET_DEST_DIR}\" \\ .\/configure --prefix=\/usr   --build=x86_64-pc-linux-gnu \\   --host=${TARGET} \\   --sysconfdir=\/etc \\   --with-config=\/etc\/csvnrc \\   --with-controldir=\/etc\/rc.d \\   --with-logrotatedir=\/etc\/logrotate.d \\   --with-scriptdir=\/var\/www\/htdocs\/csvn \\   --with-homedir=\/var\/lib\/csvn \\   --with-logdir=\/var\/log \\   --with-piddir=\/var\/run  make make install DESTDIR=${TARGET_DEST_DIR} <\/code><\/pre>\n
  <\/p>\n
Also we can make use of additional variables such as CFLAGS<\/b>, LDFLAGS<\/b>:  <\/p>\n
  <\/p>\n
LDFLAGS=\"-L${TARGET_DEST_DIR}\/lib -L${TARGET_DEST_DIR}\/usr\/lib\" TARGET_INCPATH=\"-L${TARGET_DEST_DIR}\/usr\/include\" CFLAGS=\"${TARGET_INCPATH}\" CPPFLAGS=\"${TARGET_INCPATH}\" <\/code><\/pre>\n
  <\/p>\n
Post Install<\/h3>\n
  <\/p>\n
The system user, on whose behalf the Nginx<\/b> server is launched, must have permissions to access the directory in which the cSvn<\/b> CGI script was installed:  <\/p>\n
  <\/p>\n
chown -R nginx:nginx \/var\/www\/htdocs\/csvn <\/code><\/pre>\n
  <\/p>\n
If you configured access to your repositories on behalf system user named svn<\/b>, then it would be good to grant permissions to svn<\/b> user to acces to the directory \/var\/lib\/csvn\/<\/em> which is a home of csvnd(8)<\/b><\/a> daemon:  <\/p>\n
  <\/p>\n
chown -R svn:svn \/var\/lib\/csvn <\/code><\/pre>\n
  <\/p>\n
and also run the csvnd<\/b> daemon on behalf of that svn<\/b> user.  <\/p>\n
  <\/p>\n
To run the csvnd<\/b> daemon on systems with BSD-like initialization such as Slackware<\/b> we have to add following lines to the \/etc\/rc.d\/rc.M<\/em> and \/etc\/rc.d\/rc.6<\/em> scripts correspondengly:  <\/p>\n
  \/etc\/rc.d\/rc.M:<\/b><\/p>\n
# Start csvnd server: if [ -x \/etc\/rc.d\/rc.csvnd ]; then   \/etc\/rc.d\/rc.csvnd start fi <\/code><\/pre>\n
  \/etc\/rc.d\/rc.6:<\/b><\/p>\n
# Stop csvnd server: if [ -x \/etc\/rc.d\/rc.csvnd ]; then   \/etc\/rc.d\/rc.csvnd stop fi <\/code><\/pre>\n
For systems which uses systemd initialization you have to setup your own systemd unit like follow:  <\/p>\n
  \/etc\/systemd\/system\/csvnd.service:<\/b><\/p>\n
[Unit] Description=The cSvn daemon After=network.target  [Service] PIDFile=\/var\/run\/csvnd.pid ExecStart=\/usr\/sbin\/csvnd --daemonize --inotify --config=\/etc\/csvnrc ExecReload=\/bin\/kill -s HUP $MAINPID ExecStop=\/bin\/kill -s TERM $MAINPID  [Install] WantedBy=multi-user.target <\/code><\/pre>\n
uWsgi<\/h2>\n
  <\/p>\n
Since we used the —with-scriptdir=\/var\/www\/htdocs\/csvn<\/em> option on configuring stage, the cSvn<\/b> CGI script installed in the \/var\/www\/htdocs\/csvn\/<\/em> directory. In this case, the \/etc\/uwsgi\/csvn.ini<\/em> file should look like this:  <\/p>\n
  \/etc\/uwsgi\/csvn.ini:<\/b><\/p>\n
[uwsgi] master          = true plugins         = cgi socket          = \/run\/uwsgi\/%n.sock uid             = nginx gid             = nginx procname-master = uwsgi csvn processes       = 1 threads         = 2 cgi             = \/var\/www\/htdocs\/csvn\/csvn.cgi <\/code><\/pre>\n
Where \/var\/www\/htdocs\/csvn\/csvn.cgi<\/em> is the full name of installed cSvn<\/b> CGI script.  <\/p>\n
  <\/p>\n
To run the uWSGI<\/b> daemon for cSvn<\/b> backend we can make use following start\/stop script:  <\/p>\n
  \/ets\/rc.d\/rc.csvn-uwsgi:<\/b><\/p>\n
#!\/bin\/sh # # uWSGI daemon control script. #  CONF=csvn BIN=\/usr\/bin\/uwsgi CONFDIR=\/etc\/uwsgi PID=\/var\/run\/$CONF-uwsgi.pid  uwsgi_start() {   # Sanity checks.   if [ ! -r $CONFDIR\/csvn.ini ]; then # no config files, exit:     echo \"There are config files in $CONFDIR directory. Abort.\"     exit 1   fi    if [ -s $PID ]; then     echo \"uWSGI for cSvn appears to already be running?\"     exit 1   fi    echo \"Starting uWSGI for cSvn server daemon...\"   if [ -x $BIN ]; then     \/bin\/mkdir -p \/run\/uwsgi     \/bin\/chown nginx:nginx \/run\/uwsgi     \/bin\/chmod 0755 \/run\/uwsgi     $BIN --thunder-lock --pidfile $PID --daemonize \/var\/log\/csvn-uwsgi.log --ini $CONFDIR\/$CONF.ini   fi }  uwsgi_stop() {   echo \"Shutdown uWSGI for cSvn gracefully...\"   \/bin\/kill -INT $(cat $PID)   \/bin\/rm -f $PID }  uwsgi_reload() {   echo \"Reloading uWSGI for cSvn configuration...\"   kill -HUP $(cat $PID) }  uwsgi_restart() {   uwsgi_stop   sleep 3   uwsgi_start }  case \"$1\" in   start)     uwsgi_start     ;;   stop)     uwsgi_stop     ;;   reload)     uwsgi_reload     ;;   restart)     uwsgi_restart     ;;   *)   echo \"usage: `basename $0` {start|stop|reload|restart}\" esac <\/code><\/pre>\n
To run this daemon on systems with BSD-like initialization such as Slackware<\/b> we have to add following lines to the \/etc\/rc.d\/rc.M<\/em> and \/etc\/rc.d\/rc.6<\/em> scripts correspondingly.  <\/p>\n
  \/etc\/rc.d\/rc.M:<\/b><\/p>\n
# Start uWSGI for cSvn server: if [ -x \/etc\/rc.d\/rc.csvn-uwsgi ]; then   \/etc\/rc.d\/rc.csvn-uwsgi start fi <\/code><\/pre>\n
  \/etc\/rc.d\/rc.6:<\/b><\/p>\n
# Stop uWSGI for cSvn server: if [ -x \/etc\/rc.d\/rc.csvn-uwsgi ]; then   \/etc\/rc.d\/rc.csvn-uwsgi stop fi <\/code><\/pre>\n
Nginx<\/h2>\n
  <\/p>\n
First of all we have to add virtual server to the main Nginx<\/b> config file:  <\/p>\n
  \/etc\/nginx\/nginx.conf:<\/b><\/p>\n
    include \/etc\/nginx\/vhosts\/csvn.example.org.conf; <\/code><\/pre>\n
The following configuration used uWsgi<\/b> and will serve cSvn<\/b> on a subdomain like csvn.example.org<\/b>:  <\/p>\n
  \/etc\/nginx\/vhosts\/csvn.example.org.conf:<\/b><\/p>\n
# # cSvn server: #      server {         listen 80;         server_name csvn.example.org;         return 301 https:\/\/csvn.example.org$request_uri;     }      server {         listen 443 ssl;         server_name csvn.example.org;         root \/var\/www\/htdocs\/csvn;          charset UTF-8;          #         # see:         #   https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/Security\/HTTP_strict_transport_security ,         #   https:\/\/raymii.org\/s\/tutorials\/HTTP_Strict_Transport_Security_for_Apache_NGINX_and_Lighttpd.html         #         # see also: http:\/\/classically.me\/blogs\/how-clear-hsts-settings-major-browsers         # and do not include includeSubdomains; parameter into line:         #         add_header Strict-Transport-Security \"max-age=63072000; preload\";          error_log \/var\/log\/nginx\/csvn.example.org-error.log;         access_log \/var\/log\/nginx\/csvn.example.org-access.log;          keepalive_timeout        60;         ssl_certificate          \/etc\/letsencrypt\/live\/csvn.example.org\/fullchain.pem;         ssl_certificate_key      \/etc\/letsencrypt\/live\/csvn.example.org\/privkey.pem;         ssl_trusted_certificate  \/etc\/letsencrypt\/live\/csvn.example.org\/chain.pem;         ssl_protocols            SSLv3 TLSv1 TLSv1.1 TLSv1.2;         ssl_ciphers              \"RC4:HIGH:!aNULL:!MD5:!kEDH\";          gzip on;         gzip_disable \"msie6\";         gzip_comp_level 6;         gzip_min_length 1100;         gzip_buffers 16 8k;         gzip_proxied any;         gzip_types text\/plain text\/css text\/js text\/xml text\/javascript                    image\/svg+xml image\/gif image\/jpeg image\/png                    application\/json application\/x-javascript application\/xml application\/xml+rss application\/javascript                    font\/truetype font\/opentype application\/font-woff application\/font-woff2                    application\/x-font-ttf application\/x-font-opentype application\/vnd.ms-fontobject application\/font-sfnt;          #         # Serve static content with nginx         #          #         # Rewrite rules for versioning CSS + JS thtouh filemtime directive         #         location ~* ^.+.(css|js)$ {             rewrite ^(.+).(d+).(css|js)$ $1.$3 last;              expires 31536000s;              access_log off;             log_not_found off;              add_header Pragma public;             add_header Cache-Control \"max-age=31536000, public\";         }          #         # Caching of static files         #         location ~* .(eot|gif|gz|gzip|ico|jpg|jpeg|otf|pdf|png|svg|svgz|swf|tar|t?gz|woff|zip)$ {             expires 31536000s;              access_log off;             log_not_found off;              add_header Pragma public;             add_header Cache-Control \"max-age=31536000, public\";         }          location ~ ^\/favicon.ico$ {             root \/u3\/nginx\/vhosts\/csvn;             access_log off;             log_not_found off;             expires 30d;         }          location = \/robots.txt {             allow all;             log_not_found off;             access_log off;         }          location \/ {             try_files $uri @csvn;         }          location @csvn {             gzip off;             include uwsgi_params;             uwsgi_modifier1 9;             uwsgi_pass unix:\/run\/uwsgi\/csvn.sock;         }     } <\/code><\/pre>\n
Configuring SVN Repositories<\/h2>\n
  <\/p>\n
A detailed description of the configuration file format can be found in the csvnrc(5)<\/b><\/a> manual page.  <\/p>\n
  <\/p>\n
Here we will give a working example of a description of the cSvn<\/b> repository which can be used as a template for your configurations.  <\/p>\n
  \/etc\/csvnrc:<\/b><\/p>\n
svn-utc-offset = +0300;  checkout-prefix-readonly = 'svn:\/\/radix.pro'; checkout-prefix          = 'svn+ssh:\/\/svn@radix.pro';  branches = 'branches'; trunk    = 'trunk'; tags     = 'tags';  snapshots = 'tar.xz';  css = '\/.csvn\/css\/csvn.css'; logo = '\/.csvn\/pixmaps\/csvn-banner-280x280.png'; logo-alt = \"Radix.pro\"; logo-link = \"https:\/\/radix.pro\"; main-menu-logo = '\/.csvn\/pixmaps\/logo\/SVN-logo-white-744x744.svg'; favicon-path = '\/.csvn\/pixmaps\/favicon'; syntax-highlight-css = '_csvn.css'; header = '\/.csvn\/html\/header.html'; footer = '\/.csvn\/html\/footer.html'; page-size = 200;  owner = \"Andrey V.Kosteltsev\"; author = \"Andrey V.Kosteltsev\"; title = \"Radix.pro SVN Repositories\"; description = \"Subversion repositories hosted at radix.pro (St.-Petersburg)\"; keywords = \"cSvn repositories\"; copyright = \"\u00a9 Andrey V. Kosteltsev, 2019 \u2013 2020.\"; copyright-notice = \"Where any material of this site is being reproduced, published or issued to others the reference to the source is obligatory.\";  home-page = \"https:\/\/radix.pro\/\";  section \"Tools\" {   repo 'csvn' {     owner = \"Andrey V.Kosteltsev\";     title = \"cSvn CGI Script\";     description = \"cSvn CGI Script \u2013 is a web frontend for Subversion\u2122 Repositories\";     home-page = \"https:\/\/radix.pro\/\";   } } <\/code><\/pre>\n
  <\/p>\n
To access your own repositories, we recommend the svn+ssh<\/b> protocol.  <\/p>\n
  <\/p>\n
Final Settings<\/h2>\n
  <\/p>\n
Files needed to work on web-client side are placed in the \/var\/www\/htdocs\/csvn\/.csvn\/<\/em> directory. By editing the HTML header file \/.csvn\/html\/header.html<\/em> and cSvn<\/b> config file \/etc\/csvnrc<\/em> user can change favicon.ico<\/em>, change the theme of syntax highlighting, choose images for his repositories, define keywords for search engines such as Google, and also bunch of the other settings.  <\/p>\n
  <\/p>\n
Additional information about support of analysis services and custom donation dialogues you can find on csvnrc(5)<\/b><\/a> page.  <\/p>\n
  <\/p>\n
Enjoy.  <\/p>\n<\/div>\n<\/div>\n<\/div>\n
<\/div>\n

 \u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438  https:\/\/habr.com\/ru\/articles\/529264\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
<\/div>\n
\n
\n
\n
\n
 cSvn<\/b> \u2014 is a web interface for Subversion<\/b> repositories. cSvn<\/b> is based on CGI script written in \u0421<\/b>.  <\/p>\n
  <\/p>\n
This article covers installing and configuring cSvn<\/b> to work using Nginx<\/b><\/a> + uWsgi<\/b><\/a>. Setting up server components is quite simple and practically does not differ from setting up cGit<\/b><\/a>.  <\/p>\n
  <\/p>\n
cSvn<\/b> supports Markdown files that are processed on the server side using the md4c<\/a> library, which has proven itself in the KDE Plasma<\/b> project. cSvn<\/b> provides the ability to add site verification codes and scripts from systems such as Google Analytics<\/em><\/b> and Yandex.Metrika<\/em><\/b> for trafic analysis. Users who wonder to receive donations for his projects can create and import custom donation modal dialogs.  <\/p>\n
  <\/p>\n
Instead of looking at screenshots, it is better to look at the working site<\/a> to decide on installing cSvn<\/b><\/a> on your own server.  <\/p>\n
  <\/p>\n
It should be noted that you can browse not only your own repositories, but also configure viewing of third-party resources via HTTPS and SVN protocols.  <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-399982","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/399982","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=399982"}],"version-history":[{"count":0,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/399982\/revisions"}],"wp:attachment":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=399982"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=399982"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=399982"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}