https://wiki.alpinelinux.org/w/api.php?action=feedcontributions&feedformat=atom&user=Nicolaus 2026-04-27T15:26:33Z User contributions MediaWiki 1.40.0 https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16512 2019-10-13T21:58:52Z

<p>Nicolaus: /* Installation */</p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Mumble is an open source, cross platform, low-latency, high quality voice over IP (VoIP) client. Mumble uses a client/server architecture and is primarily used by gamers, but can be used for any VoIP purpose.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}<br /> <br /> === Setting up SSL certificates ===<br /> If you already have used Certbot to set up certificates in your web server, then you can easily make a new certificate for a subdomain 'mumble' and add the cert paths to the mumble.ini configuration file. You can use vim and edit the file manually.<br /> {{Cmd|vim /etc/murmur.ini}}<br /> It should look something like this.<br /> {{Cat|/etc/murmur.ini|&lt;nowiki&gt;<br /> sslCert=/etc/letsencrypt/live/your_domain.com/fullchain.pem<br /> sslKey=/etc/letsencrypt/live/your_domain.com/privkey.pem<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Starting up the service ===<br /> Start the Murmur service.<br /> {{Cmd|rc-service murmur start}}<br /> You can add the Murmur service to the default runlevel.<br /> {{Cmd|rc-service add murmur default}}<br /> In case you don't want Murmur to be default on runlevel, rollback with this command<br /> {{Cmd|rc-service delete murmur default}}<br /> <br /> <br /> [[category: telephony]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16493 2019-10-09T06:33:05Z

<p>Nicolaus: </p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Mumble is an open source, cross platform, low-latency, high quality voice over IP (VoIP) client. Mumble uses a client/server architecture and is primarily used by gamers, but can be used for any VoIP purpose.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}<br /> Open the murmur.ini configuration file and edit it so murmur can be run by the 'murmur' user created by the package.<br /> {{Cmd|vim /var/lib/murmur/murmur.sqlite}}<br /> {{Cat|/var/lib/murmur/murmur.sqlite|&lt;nowiki&gt;<br /> uname=murmur<br /> &lt;/nowiki&gt;<br /> }}<br /> Now give permissions to the murmur database, so the user 'murmur' can read it.<br /> {{Cmd|chown murmur /var/lib/murmur/murmur.sqlite}}<br /> <br /> === Setting up SSL certificates ===<br /> If you already have used Certbot to set up certificates in your web server, then you can easily make a new certificate for a subdomain 'mumble' and add the cert paths to the mumble.ini configuration file. You can use vim and edit the file manually.<br /> {{Cmd|vim /etc/murmur.ini}}<br /> It should look something like this.<br /> {{Cat|/etc/murmur.ini|&lt;nowiki&gt;<br /> sslCert=/etc/letsencrypt/live/your_domain.com/fullchain.pem<br /> sslKey=/etc/letsencrypt/live/your_domain.com/privkey.pem<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Starting up the service ===<br /> Start the Murmur service.<br /> {{Cmd|rc-service murmur start}}<br /> You can add the Murmur service to the default runlevel.<br /> {{Cmd|rc-service add murmur default}}<br /> In case you don't want Murmur to be default on runlevel, rollback with this command<br /> {{Cmd|rc-service delete murmur default}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16492 2019-10-09T06:07:17Z

<p>Nicolaus: /* Starting up the service */</p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}<br /> Open the murmur.ini configuration file and edit it so murmur can be run by the 'murmur' user created by the package.<br /> {{Cmd|vim /var/lib/murmur/murmur.sqlite}}<br /> {{Cat|/var/lib/murmur/murmur.sqlite|&lt;nowiki&gt;<br /> uname=murmur<br /> &lt;/nowiki&gt;<br /> }}<br /> Now give permissions to the murmur database, so the user 'murmur' can read it.<br /> {{Cmd|chown murmur /var/lib/murmur/murmur.sqlite}}<br /> <br /> === Setting up SSL certificates ===<br /> If you already have used Certbot to set up certificates in your web server, then you can easily make a new certificate for a subdomain 'mumble' and add the cert paths to the mumble.ini configuration file. You can use vim and edit the file manually.<br /> {{Cmd|vim /etc/murmur.ini}}<br /> It should look something like this.<br /> {{Cat|/etc/murmur.ini|&lt;nowiki&gt;<br /> sslCert=/etc/letsencrypt/live/your_domain.com/fullchain.pem<br /> sslKey=/etc/letsencrypt/live/your_domain.com/privkey.pem<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Starting up the service ===<br /> Start the murmur service.<br /> {{Cmd|rc-service murmur start}}<br /> You can add the murmur service to the default runlevel.<br /> {{Cmd|rc-service add murmur default}}<br /> In case you don't want murmur to be default on runlevel, rollback with this command<br /> {{Cmd|rc-service delete murmur default}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16491 2019-10-09T06:07:09Z

<p>Nicolaus: /* Setting up SSL certificates */</p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}<br /> Open the murmur.ini configuration file and edit it so murmur can be run by the 'murmur' user created by the package.<br /> {{Cmd|vim /var/lib/murmur/murmur.sqlite}}<br /> {{Cat|/var/lib/murmur/murmur.sqlite|&lt;nowiki&gt;<br /> uname=murmur<br /> &lt;/nowiki&gt;<br /> }}<br /> Now give permissions to the murmur database, so the user 'murmur' can read it.<br /> {{Cmd|chown murmur /var/lib/murmur/murmur.sqlite}}<br /> <br /> === Setting up SSL certificates ===<br /> If you already have used Certbot to set up certificates in your web server, then you can easily make a new certificate for a subdomain 'mumble' and add the cert paths to the mumble.ini configuration file. You can use vim and edit the file manually.<br /> {{Cmd|vim /etc/murmur.ini}}<br /> It should look something like this.<br /> {{Cat|/etc/murmur.ini|&lt;nowiki&gt;<br /> sslCert=/etc/letsencrypt/live/your_domain.com/fullchain.pem<br /> sslKey=/etc/letsencrypt/live/your_domain.com/privkey.pem<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Starting up the service ===<br /> Start the murmur service.<br /> {{Cmd|rc-service murmur start}}<br /> {{Note|Optional steps.}}<br /> You can add the murmur service to the default runlevel.<br /> {{Cmd|rc-service add murmur default}}<br /> In case you don't want murmur to be default on runlevel, rollback with this command<br /> {{Cmd|rc-service delete murmur default}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16490 2019-10-09T06:05:13Z

<p>Nicolaus: Added simple SSL guide for Murmur</p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}<br /> Open the murmur.ini configuration file and edit it so murmur can be run by the 'murmur' user created by the package.<br /> {{Cmd|vim /var/lib/murmur/murmur.sqlite}}<br /> {{Cat|/var/lib/murmur/murmur.sqlite|&lt;nowiki&gt;<br /> uname=murmur<br /> &lt;/nowiki&gt;<br /> }}<br /> Now give permissions to the murmur database, so the user 'murmur' can read it.<br /> {{Cmd|chown murmur /var/lib/murmur/murmur.sqlite}}<br /> <br /> === Setting up SSL certificates ===<br /> {{Note|Optional steps.}}<br /> If you already have used Certbot to set up certificates in your web server, then you can easily make a new certificate for a subdomain 'mumble' and add the cert paths to the mumble.ini configuration file. You can do it simple and slick with a single sed command. Or you can also use vim and do it manually.<br /> {{Cmd|sed -i -e 's/;sslCert=/sslCert=\/etc\/letsencrypt\/live\/your_domain.com\/fullchain.pem/ ; s/;sslKey=/sslKey=\/etc\/letsencrypt\/live\/your_domain.com\/privkey.pem/' /etc/murmur.ini}}<br /> It should look something like this.<br /> {{Cat|/etc/murmur.ini|&lt;nowiki&gt;<br /> sslCert=/etc/letsencrypt/live/your_domain.com/fullchain.pem<br /> sslKey=/etc/letsencrypt/live/your_domain.com/privkey.pem<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Starting up the service ===<br /> Start the murmur service.<br /> {{Cmd|rc-service murmur start}}<br /> {{Note|Optional steps.}}<br /> You can add the murmur service to the default runlevel.<br /> {{Cmd|rc-service add murmur default}}<br /> In case you don't want murmur to be default on runlevel, rollback with this command<br /> {{Cmd|rc-service delete murmur default}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16489 2019-10-09T04:58:16Z

<p>Nicolaus: /* Installation */</p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}<br /> Open the murmur.ini configuration file and edit it so murmur can be run by the 'murmur' user created by the package.<br /> {{Cmd|vim /var/lib/murmur/murmur.sqlite}}<br /> {{Cat|/var/lib/murmur/murmur.sqlite|&lt;nowiki&gt;<br /> uname=murmur<br /> &lt;/nowiki&gt;<br /> }}<br /> Now give permissions to the murmur database, so the user 'murmur' can read it.<br /> {{Cmd|chown murmur /var/lib/murmur/murmur.sqlite}}<br /> <br /> === Starting up the service ===<br /> Start the murmur service.<br /> {{Cmd|rc-service murmur start}}<br /> {{Note|Optional steps}}<br /> You can add the murmur service to the default runlevel.<br /> {{Cmd|rc-service add murmur default}}<br /> In case you don't want murmur to be default on runlevel, rollback with this command<br /> {{Cmd|rc-service delete murmur default}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16488 2019-10-09T04:57:04Z

<p>Nicolaus: /* Installation */ More stuff to the wiki.</p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}<br /> Open the murmur.ini configuration file and edit it so murmur can be run by the 'murmur' user.<br /> {{Cmd|vim /var/lib/murmur/murmur.sqlite}}<br /> {{Cat|/var/lib/murmur/murmur.sqlite|&lt;nowiki&gt;<br /> uname=murmur<br /> &lt;/nowiki&gt;<br /> }}<br /> Now give permissions to the murmur database, so the user 'murmur' can read it.<br /> {{Cmd|chown murmur /var/lib/murmur/murmur.sqlite}}<br /> <br /> === Starting up the service ===<br /> Start the murmur service.<br /> {{Cmd|rc-service murmur start}}<br /> {{Note|Optional steps}}<br /> You can add the murmur service to the default runlevel.<br /> {{Cmd|rc-service add murmur default}}<br /> In case you don't want murmur to be default on runlevel, rollback with this command<br /> {{Cmd|rc-service delete murmur default}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16487 2019-10-09T00:29:15Z

<p>Nicolaus: </p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16486 2019-10-09T00:28:53Z

<p>Nicolaus: </p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur [https://wiki.alpinelinux.org/wiki/Mumble Mumble] (also called Mumble-Server) is the server component for Mumble. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Murmur&diff=16485 2019-10-09T00:27:31Z

<p>Nicolaus: first</p> <hr /> <div>[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for Mumble. Murmur allows you to run your own private or public voice chat server for the Mumble client.<br /> <br /> == Installation ==<br /> First of all we need Murmur in our server.<br /> {{Cmd|apk add murmur}}</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16350 2019-09-10T08:05:35Z

<p>Nicolaus: /* In your workstation set up new public keys */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N &quot;&quot; -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/${YOUR_USERNAME}.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/${YOUR_USERNAME}.pub root@${YOUR_SERVER_DOMAIN_OR_IP}:/var/lib/git/${YOUR_USERNAME}.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/${YOUR_USERNAME}.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@${YOUR_SERVER_DOMAIN_OR_IP}:${YOUR_GIT_REPO} }}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16349 2019-09-10T08:05:21Z

<p>Nicolaus: /* In your workstation, if you don&#039;t have a git repository, create one */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N &quot;&quot; -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/${YOUR_USERNAME}.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@${YOUR_SERVER_DOMAIN_OR_IP}:/var/lib/git/${YOUR_USERNAME}.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/${YOUR_USERNAME}.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@${YOUR_SERVER_DOMAIN_OR_IP}:${YOUR_GIT_REPO} }}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16348 2019-09-10T08:05:09Z

<p>Nicolaus: /* In your workstation, if you don&#039;t have a git repository, create one */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N &quot;&quot; -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/${YOUR_USERNAME}.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@${YOUR_SERVER_DOMAIN_OR_IP}:/var/lib/git/${YOUR_USERNAME}.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/${YOUR_USERNAME}.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@{YOUR_SERVER_DOMAIN_OR_IP}:${YOUR_GIT_REPO} }}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16347 2019-09-10T08:05:00Z

<p>Nicolaus: /* In your workstation, if you don&#039;t have a git repository, create one */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N &quot;&quot; -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/${YOUR_USERNAME}.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@${YOUR_SERVER_DOMAIN_OR_IP}:/var/lib/git/${YOUR_USERNAME}.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/${YOUR_USERNAME}.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@{YOUR_SERVER_DOMAIN_OR_IP}:${YOUR_GIT_REPO}}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16346 2019-09-10T08:04:49Z

<p>Nicolaus: /* In your server set up Gitolite */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N &quot;&quot; -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/${YOUR_USERNAME}.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@${YOUR_SERVER_DOMAIN_OR_IP}:/var/lib/git/${YOUR_USERNAME}.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/${YOUR_USERNAME}.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@{YOUR_SERVER_DOMAIN_OR_IP}:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16345 2019-09-10T08:02:46Z

<p>Nicolaus: /* In your workstation set up new public keys */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N &quot;&quot; -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/${YOUR_USERNAME}.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@${YOUR_SERVER_DOMAIN_OR_IP}:/var/lib/git/${YOUR_USERNAME}.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@{YOUR_SERVER_DOMAIN_OR_IP}:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16344 2019-09-10T08:02:03Z

<p>Nicolaus: /* In your workstation set up new public keys */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/${YOUR_USERNAME}.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@${YOUR_SERVER_DOMAIN_OR_IP}:/var/lib/git/${YOUR_USERNAME}.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@{YOUR_SERVER_DOMAIN_OR_IP}:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16343 2019-09-10T07:57:49Z

<p>Nicolaus: /* In your workstation, if you don&#039;t have a git repository, create one */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@{YOUR_SERVER_DOMAIN_OR_IP}:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ~/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ~/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16342 2019-09-10T07:55:46Z

<p>Nicolaus: /* In your workstation, if you don&#039;t have a git repository, create one */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ~/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ~/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ~/dotfiles/ remote add origin git@YOUR_SERVER_DOMAIN_OR_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ${HOME}/dotfiles/testfile}}<br /> {{Cmd|git -C ~/dotfiles/ add ${HOME}/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ~/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ~/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16341 2019-09-10T07:53:58Z

<p>Nicolaus: /* In your workstation set up Gitolite */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ~/gitolite-admin}}<br /> Use your favorite text editor and open the file ~/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ~/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|~/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ~/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ~/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ${HOME}/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ${HOME}/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME}/dotfiles/ remote add origin git@YOUR_SERVER_DOMAIN_OR_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ${HOME}/dotfiles/testfile}}<br /> {{Cmd|git -C ${HOME}/dotfiles/ add ${HOME}/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME}/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME}/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16340 2019-09-10T07:51:25Z

<p>Nicolaus: /* In your workstation set up new public keys */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f ~/.ssh/id_rsa}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ~/.ssh/id_rsa.pub ~/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ~/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ${HOME}/gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ${HOME}/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ${HOME}/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME}/dotfiles/ remote add origin git@YOUR_SERVER_DOMAIN_OR_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ${HOME}/dotfiles/testfile}}<br /> {{Cmd|git -C ${HOME}/dotfiles/ add ${HOME}/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME}/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME}/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16338 2019-09-10T04:43:30Z

<p>Nicolaus: /* In your workstation, if you don&#039;t have a .git, create one */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ${HOME}/gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a git repository, create one ===<br /> Create a dotfiles directory.<br /> {{Cmd|mkdir ${HOME}/dotfiles/}}<br /> Initialize a git repository in the dotfiles directory.<br /> {{Cmd|git -C ${HOME}/dotfiles/ init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME}/dotfiles/ remote add origin git@YOUR_SERVER_DOMAIN_OR_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|echo &quot;hello world&quot; &gt; ${HOME}/dotfiles/testfile}}<br /> {{Cmd|git -C ${HOME}/dotfiles/ add ${HOME}/dotfiles/testfile}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME}/dotfiles/ commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME}/dotfiles/ push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16337 2019-09-10T04:32:05Z

<p>Nicolaus: /* In your workstation set up Gitolite */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin ${HOME}/gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16336 2019-09-10T04:31:45Z

<p>Nicolaus: /* In your workstation set up Gitolite */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${YOUR_SERVER_DOMAIN_OR_IP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16335 2019-09-10T04:31:18Z

<p>Nicolaus: /* In your workstation set up new public keys */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_DOMAIN_OR_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16334 2019-09-10T04:30:39Z

<p>Nicolaus: /* In your workstation set up Gitolite */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> In your workstation clone the .git directory anywhere you want (preferably your home directory) to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16333 2019-09-10T04:29:33Z

<p>Nicolaus: /* In your server set up Gitolite */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> <br /> === In your workstation set up Gitolite ===<br /> Clone the .git directory to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16305 2019-09-04T05:48:41Z

<p>Nicolaus: /* Set up SSL certificates */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Installation ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 1025<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:1025&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 1025). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 1025<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:1025;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/your_domain.com/privkey.pem /etc/letsencrypt/live/your_domain.com/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16304 2019-09-04T05:47:19Z

<p>Nicolaus: changed port</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Installation ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 1025<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:1025&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 1025). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 1025<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:1025;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16303 2019-09-04T05:46:13Z

<p>Nicolaus: /* Configure the ZNC webadmin page */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Installation ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:1025&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 1025<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Cgit&diff=16302 2019-09-04T03:48:43Z

<p>Nicolaus: /* Run cgit using spawn-fcgi and fcgiwrap */</p> <hr /> <div>[https://git.zx2c4.com/cgit/ cgit] is a fast web-interface (CGI) for git written in the C programming language. It makes it possible for potential contributors to track and view project source code from the web instead of through a git client.<br /> <br /> == Installation ==<br /> {{Note|It is very recommendable that you already have a directory with an active .git working in your server. If you don't have one, install [[gitolite]] or a similar program before going further.}}<br /> Install the package that contains cgit and git.<br /> {{Cmd|apk add cgit git}}<br /> <br /> Open up /etc/cgitrc with your favorite editor, in this case is vim.<br /> {{Cmd|vim /etc/cgitrc}}<br /> <br /> If you want to show an specific repository your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> repo.path=/var/lib/git/repositories/YOUR_GIT_REPO.git/<br /> repo.url=CUSTOM_GIT_URL<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> If you want to scan and show all the repositories you have, your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> scan-path=/var/lib/git/repositories/<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Run cgit using spawn-fcgi and fcgiwrap ===<br /> Create a new service by doing a symbolic link.<br /> {{Cmd|ln -s /etc/init.d/spawn-fcgi /etc/init.d/spawn-fcgi.cgit}}<br /> Create a configuration file called spawn-fcgi.cgit in /etc/conf.d/ ; the service will run fcgiwrap automatically everytime is called. It should look exactly like this:<br /> {{Cat|/etc/conf.d/spawn-fcgi.cgit|&lt;nowiki&gt;<br /> FCGI_PORT=1234<br /> FCGI_PROGRAM=/usr/bin/fcgiwrap<br /> &lt;/nowiki&gt;<br /> }}<br /> Start the newly created service.<br /> {{Cmd|rc-service spawn-fcgi.cgit start}}<br /> <br /> == Run cgit with a web service ==<br /> <br /> === Configure Lighttpd to work with cgit ===<br /> Install the package that contains lighttpd if you haven't already.<br /> {{Cmd|apk add lighttpd}}<br /> <br /> Create a cgit.conf file into the lighttpd directory with the following content:<br /> {{Cat|/etc/lighttpd/cgit.conf|&lt;nowiki&gt;<br /> server.modules += (&quot;mod_redirect&quot;,<br /> &quot;mod_alias&quot;,<br /> &quot;mod_cgi&quot;,<br /> &quot;mod_fastcgi&quot;,<br /> &quot;mod_rewrite&quot; )<br /> <br /> var.webapps = &quot;/usr/share/webapps/&quot;<br /> $HTTP[&quot;url&quot;] =~ &quot;^/cgit&quot; {<br /> server.document-root = webapps<br /> server.indexfiles = (&quot;cgit.cgi&quot;)<br /> cgi.assign = (&quot;cgit.cgi&quot; =&gt; &quot;&quot;)<br /> mimetype.assign = ( &quot;.css&quot; =&gt; &quot;text/css&quot; )<br /> }<br /> url.redirect = (<br /> &quot;^/git/(.*)$&quot; =&gt; &quot;/cgit/cgit.cgi/$1&quot;,<br /> )<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Finally, add the following line to the lighttpd.conf file:<br /> {{Cat|/etc/lighttpd/lighttpd.conf|&lt;nowiki&gt;include &quot;cgit.conf&quot;<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Restart the lighttpd service.<br /> {{Cmd|rc-service lighttpd restart}}<br /> <br /> === Configure NGINX to work with cgit pointing to a subdomain ===<br /> <br /> Install the package that contains NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> <br /> Create a custom configuration in the NGINX's conf.d directory.<br /> {{Cmd|vim /etc/nginx/conf.d/git.your_domain.com.conf}}<br /> <br /> The file should look something like this:<br /> <br /> {{Cat|/etc/nginx/conf.d/git.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name git.your_domain.com;<br /> root /usr/share/webapps/cgit;<br /> try_files $uri @cgit;<br /> location @cgit {<br /> include fastcgi_params;<br /> fastcgi_pass localhost:1234;<br /> fastcgi_param SCRIPT_FILE $document_root/cgit.cgi;<br /> fastcgi_param PATH_INFO $uri;<br /> fastcgi_param QUERY_STRING $args;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Cgit&diff=16301 2019-09-04T03:48:06Z

<p>Nicolaus: /* Run cgit using spawn-fcgi and fcgiwrap */</p> <hr /> <div>[https://git.zx2c4.com/cgit/ cgit] is a fast web-interface (CGI) for git written in the C programming language. It makes it possible for potential contributors to track and view project source code from the web instead of through a git client.<br /> <br /> == Installation ==<br /> {{Note|It is very recommendable that you already have a directory with an active .git working in your server. If you don't have one, install [[gitolite]] or a similar program before going further.}}<br /> Install the package that contains cgit and git.<br /> {{Cmd|apk add cgit git}}<br /> <br /> Open up /etc/cgitrc with your favorite editor, in this case is vim.<br /> {{Cmd|vim /etc/cgitrc}}<br /> <br /> If you want to show an specific repository your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> repo.path=/var/lib/git/repositories/YOUR_GIT_REPO.git/<br /> repo.url=CUSTOM_GIT_URL<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> If you want to scan and show all the repositories you have, your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> scan-path=/var/lib/git/repositories/<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Run cgit using spawn-fcgi and fcgiwrap ===<br /> Create a new service by doing a symbolic link.<br /> {{Cmd|ln -s /etc/init.d/spawn-fcgi /etc/init.d/spawn-fcgi.cgit}}<br /> Create a configuration file called spawn-fcgi.cgit in /etc/conf.d/ ; the service will run fcgiwrap automatically everytime is called. It should look exactly like this:<br /> {{Cat|/etc/conf.d/spawn-fcgi.cgit|&lt;nowiki&gt;<br /> FCGI_PROGRAM=/usr/bin/fcgiwrap<br /> FCGI_PORT=1234<br /> &lt;/nowiki&gt;<br /> }}<br /> Start the newly created service.<br /> {{Cmd|rc-service spawn-fcgi.cgit start}}<br /> <br /> == Run cgit with a web service ==<br /> <br /> === Configure Lighttpd to work with cgit ===<br /> Install the package that contains lighttpd if you haven't already.<br /> {{Cmd|apk add lighttpd}}<br /> <br /> Create a cgit.conf file into the lighttpd directory with the following content:<br /> {{Cat|/etc/lighttpd/cgit.conf|&lt;nowiki&gt;<br /> server.modules += (&quot;mod_redirect&quot;,<br /> &quot;mod_alias&quot;,<br /> &quot;mod_cgi&quot;,<br /> &quot;mod_fastcgi&quot;,<br /> &quot;mod_rewrite&quot; )<br /> <br /> var.webapps = &quot;/usr/share/webapps/&quot;<br /> $HTTP[&quot;url&quot;] =~ &quot;^/cgit&quot; {<br /> server.document-root = webapps<br /> server.indexfiles = (&quot;cgit.cgi&quot;)<br /> cgi.assign = (&quot;cgit.cgi&quot; =&gt; &quot;&quot;)<br /> mimetype.assign = ( &quot;.css&quot; =&gt; &quot;text/css&quot; )<br /> }<br /> url.redirect = (<br /> &quot;^/git/(.*)$&quot; =&gt; &quot;/cgit/cgit.cgi/$1&quot;,<br /> )<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Finally, add the following line to the lighttpd.conf file:<br /> {{Cat|/etc/lighttpd/lighttpd.conf|&lt;nowiki&gt;include &quot;cgit.conf&quot;<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Restart the lighttpd service.<br /> {{Cmd|rc-service lighttpd restart}}<br /> <br /> === Configure NGINX to work with cgit pointing to a subdomain ===<br /> <br /> Install the package that contains NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> <br /> Create a custom configuration in the NGINX's conf.d directory.<br /> {{Cmd|vim /etc/nginx/conf.d/git.your_domain.com.conf}}<br /> <br /> The file should look something like this:<br /> <br /> {{Cat|/etc/nginx/conf.d/git.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name git.your_domain.com;<br /> root /usr/share/webapps/cgit;<br /> try_files $uri @cgit;<br /> location @cgit {<br /> include fastcgi_params;<br /> fastcgi_pass localhost:1234;<br /> fastcgi_param SCRIPT_FILE $document_root/cgit.cgi;<br /> fastcgi_param PATH_INFO $uri;<br /> fastcgi_param QUERY_STRING $args;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16300 2019-09-04T01:17:45Z

<p>Nicolaus: /* Setting up Gitolite */</p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Installation ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> <br /> === In your workstation set up Gitolite ===<br /> Clone the .git directory to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16299 2019-09-04T01:16:36Z

<p>Nicolaus: /* Install ZNC */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Installation ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Cgit&diff=16298 2019-09-04T01:16:18Z

<p>Nicolaus: /* Setting up cgit */</p> <hr /> <div>[https://git.zx2c4.com/cgit/ cgit] is a fast web-interface (CGI) for git written in the C programming language. It makes it possible for potential contributors to track and view project source code from the web instead of through a git client.<br /> <br /> == Installation ==<br /> {{Note|It is very recommendable that you already have a directory with an active .git working in your server. If you don't have one, install [[gitolite]] or a similar program before going further.}}<br /> Install the package that contains cgit and git.<br /> {{Cmd|apk add cgit git}}<br /> <br /> Open up /etc/cgitrc with your favorite editor, in this case is vim.<br /> {{Cmd|vim /etc/cgitrc}}<br /> <br /> If you want to show an specific repository your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> repo.path=/var/lib/git/repositories/YOUR_GIT_REPO.git/<br /> repo.url=CUSTOM_GIT_URL<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> If you want to scan and show all the repositories you have, your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> scan-path=/var/lib/git/repositories/<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Run cgit using spawn-fcgi and fcgiwrap ===<br /> Create a new service by doing a symbolic link.<br /> {{Cmd|ln -s /etc/init.d/spawn-fcgi /etc/init.d/spawn-fcgi.cgit}}<br /> Create a configuration file called spawn-fcgi.cgit in /etc/conf.d/ ; the service will run fcgiwrap automatically everytime is called. It should look exactly like this:<br /> {{Cat|/etc/conf.d/spawn-fcgi.cgit|&lt;nowiki&gt;<br /> FCGI_PROGRAM=/usr/bin/fcgiwrap<br /> &lt;/nowiki&gt;<br /> }}<br /> Start the newly created service.<br /> {{Cmd|rc-service spawn-fcgi.cgit start}}<br /> <br /> == Run cgit with a web service ==<br /> <br /> === Configure Lighttpd to work with cgit ===<br /> Install the package that contains lighttpd if you haven't already.<br /> {{Cmd|apk add lighttpd}}<br /> <br /> Create a cgit.conf file into the lighttpd directory with the following content:<br /> {{Cat|/etc/lighttpd/cgit.conf|&lt;nowiki&gt;<br /> server.modules += (&quot;mod_redirect&quot;,<br /> &quot;mod_alias&quot;,<br /> &quot;mod_cgi&quot;,<br /> &quot;mod_fastcgi&quot;,<br /> &quot;mod_rewrite&quot; )<br /> <br /> var.webapps = &quot;/usr/share/webapps/&quot;<br /> $HTTP[&quot;url&quot;] =~ &quot;^/cgit&quot; {<br /> server.document-root = webapps<br /> server.indexfiles = (&quot;cgit.cgi&quot;)<br /> cgi.assign = (&quot;cgit.cgi&quot; =&gt; &quot;&quot;)<br /> mimetype.assign = ( &quot;.css&quot; =&gt; &quot;text/css&quot; )<br /> }<br /> url.redirect = (<br /> &quot;^/git/(.*)$&quot; =&gt; &quot;/cgit/cgit.cgi/$1&quot;,<br /> )<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Finally, add the following line to the lighttpd.conf file:<br /> {{Cat|/etc/lighttpd/lighttpd.conf|&lt;nowiki&gt;include &quot;cgit.conf&quot;<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Restart the lighttpd service.<br /> {{Cmd|rc-service lighttpd restart}}<br /> <br /> === Configure NGINX to work with cgit pointing to a subdomain ===<br /> <br /> Install the package that contains NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> <br /> Create a custom configuration in the NGINX's conf.d directory.<br /> {{Cmd|vim /etc/nginx/conf.d/git.your_domain.com.conf}}<br /> <br /> The file should look something like this:<br /> <br /> {{Cat|/etc/nginx/conf.d/git.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name git.your_domain.com;<br /> root /usr/share/webapps/cgit;<br /> try_files $uri @cgit;<br /> location @cgit {<br /> include fastcgi_params;<br /> fastcgi_pass localhost:1234;<br /> fastcgi_param SCRIPT_FILE $document_root/cgit.cgi;<br /> fastcgi_param PATH_INFO $uri;<br /> fastcgi_param QUERY_STRING $args;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16297 2019-09-04T01:15:00Z

<p>Nicolaus: /* Installation */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Install ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16296 2019-09-04T01:13:42Z

<p>Nicolaus: /* Install ZNC */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Installation ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16295 2019-09-04T01:13:17Z

<p>Nicolaus: /* Setting up ZNC */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Install ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16294 2019-09-04T00:41:44Z

<p>Nicolaus: /* Configure NGINX */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Setting up ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16293 2019-09-03T19:54:03Z

<p>Nicolaus: /* Set up SSL certificates */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Setting up ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> proxy_max_temp_file_size 0;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that comes with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16292 2019-09-03T18:20:30Z

<p>Nicolaus: typo</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Setting up ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> proxy_max_temp_file_size 0;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that come with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{Cmd|cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16291 2019-09-03T18:20:11Z

<p>Nicolaus: More info about SSL certificates</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Setting up ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> proxy_max_temp_file_size 0;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificate that come with the program.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done. Your webadmin page will be automatically running the SSL certificate made by Let's Encrypt.<br /> {{Cmd|rc-service nginx restart}}<br /> Now we will replace the znc.pem certificate with the Let's Encrypt certificates for any person who wants to connect to our IRC bouncer. For this we need to concatenate two important files into znc.pem<br /> {{cat /etc/letsencrypt/live/YOUR_DOMAIN.COM/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN.COM/fullchain.pem &gt; /var/lib/znc/znc.pem}}<br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16290 2019-09-03T08:07:06Z

<p>Nicolaus: /* Configure the ZNC webadmin page */</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Setting up ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the IRC port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> proxy_max_temp_file_size 0;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificates that come with the program. If you didn't turn off SSL in listener0 (webpage), you will probably get a lot of errors.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16289 2019-09-03T06:34:33Z

<p>Nicolaus: Minor edit</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Setting up ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6697<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the webadmin port (it's listening port 6697).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6697<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> proxy_max_temp_file_size 0;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificates that come with the program. If you didn't turn off SSL in listener0 (webpage), you will probably get a lot of errors.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Cgit&diff=16236 2019-08-21T03:51:23Z

<p>Nicolaus: /* Setting up cgit */</p> <hr /> <div>[https://git.zx2c4.com/cgit/ cgit] is a fast web-interface (CGI) for git written in the C programming language. It makes it possible for potential contributors to track and view project source code from the web instead of through a git client.<br /> <br /> == Setting up cgit ==<br /> {{Note|It is very recommendable that you already have a directory with an active .git working in your server. If you don't have one, install [[gitolite]] or a similar program before going further.}}<br /> Install the package that contains cgit and git.<br /> {{Cmd|apk add cgit git}}<br /> <br /> Open up /etc/cgitrc with your favorite editor, in this case is vim.<br /> {{Cmd|vim /etc/cgitrc}}<br /> <br /> If you want to show an specific repository your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> repo.path=/var/lib/git/repositories/YOUR_GIT_REPO.git/<br /> repo.url=CUSTOM_GIT_URL<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> If you want to scan and show all the repositories you have, your configuration should look something like this:<br /> {{Cat|/etc/cgitrc|&lt;nowiki&gt;<br /> virtual-root=/<br /> scan-path=/var/lib/git/repositories/<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> === Run cgit using spawn-fcgi and fcgiwrap ===<br /> Create a new service by doing a symbolic link.<br /> {{Cmd|ln -s /etc/init.d/spawn-fcgi /etc/init.d/spawn-fcgi.cgit}}<br /> Create a configuration file called spawn-fcgi.cgit in /etc/conf.d/ ; the service will run fcgiwrap automatically everytime is called. It should look exactly like this:<br /> {{Cat|/etc/conf.d/spawn-fcgi.cgit|&lt;nowiki&gt;<br /> FCGI_PROGRAM=/usr/bin/fcgiwrap<br /> &lt;/nowiki&gt;<br /> }}<br /> Start the newly created service.<br /> {{Cmd|rc-service spawn-fcgi.cgit start}}<br /> <br /> == Run cgit with a web service ==<br /> <br /> === Configure Lighttpd to work with cgit ===<br /> Install the package that contains lighttpd if you haven't already.<br /> {{Cmd|apk add lighttpd}}<br /> <br /> Create a cgit.conf file into the lighttpd directory with the following content:<br /> {{Cat|/etc/lighttpd/cgit.conf|&lt;nowiki&gt;<br /> server.modules += (&quot;mod_redirect&quot;,<br /> &quot;mod_alias&quot;,<br /> &quot;mod_cgi&quot;,<br /> &quot;mod_fastcgi&quot;,<br /> &quot;mod_rewrite&quot; )<br /> <br /> var.webapps = &quot;/usr/share/webapps/&quot;<br /> $HTTP[&quot;url&quot;] =~ &quot;^/cgit&quot; {<br /> server.document-root = webapps<br /> server.indexfiles = (&quot;cgit.cgi&quot;)<br /> cgi.assign = (&quot;cgit.cgi&quot; =&gt; &quot;&quot;)<br /> mimetype.assign = ( &quot;.css&quot; =&gt; &quot;text/css&quot; )<br /> }<br /> url.redirect = (<br /> &quot;^/git/(.*)$&quot; =&gt; &quot;/cgit/cgit.cgi/$1&quot;,<br /> )<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Finally, add the following line to the lighttpd.conf file:<br /> {{Cat|/etc/lighttpd/lighttpd.conf|&lt;nowiki&gt;include &quot;cgit.conf&quot;<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Restart the lighttpd service.<br /> {{Cmd|rc-service lighttpd restart}}<br /> <br /> === Configure NGINX to work with cgit pointing to a subdomain ===<br /> <br /> Install the package that contains NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> <br /> Create a custom configuration in the NGINX's conf.d directory.<br /> {{Cmd|vim /etc/nginx/conf.d/git.your_domain.com.conf}}<br /> <br /> The file should look something like this:<br /> <br /> {{Cat|/etc/nginx/conf.d/git.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name git.your_domain.com;<br /> root /usr/share/webapps/cgit;<br /> try_files $uri @cgit;<br /> location @cgit {<br /> include fastcgi_params;<br /> fastcgi_pass localhost:1234;<br /> fastcgi_param SCRIPT_FILE $document_root/cgit.cgi;<br /> fastcgi_param PATH_INFO $uri;<br /> fastcgi_param QUERY_STRING $args;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16233 2019-08-20T08:33:45Z

<p>Nicolaus: </p> <hr /> <div>[https://gitolite.com/ Gitolite] is a wrapper around a base git installation which facilitates the secure management of project repositories and of the user privileges governing access to those repositories. <br /> <br /> == Setting up Gitolite ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> <br /> === In your workstation set up Gitolite ===<br /> Clone the .git directory to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16232 2019-08-20T07:15:50Z

<p>Nicolaus: /* In your server set up Gitolite */</p> <hr /> <div>== Setting up Gitolite ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup Gitolite using the public key you just sent to the server.<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> <br /> === In your workstation set up Gitolite ===<br /> Clone the .git directory to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16231 2019-08-20T07:14:49Z

<p>Nicolaus: /* In your workstation set up Gitolite */</p> <hr /> <div>== Setting up Gitolite ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup gitolite using the public key you just sent to the server.<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> <br /> === In your workstation set up Gitolite ===<br /> Clone the .git directory to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=Gitolite&diff=16230 2019-08-20T07:13:29Z

<p>Nicolaus: Overhaul of the Gitolite guide because it was obsolete.</p> <hr /> <div>== Setting up Gitolite ==<br /> Install the package that contains Gitolite.<br /> {{Cmd|apk add gitolite git}}<br /> <br /> === In your workstation set up new public keys ===<br /> Running this command will create a new pair of private and public key.<br /> {{Cmd|ssh-keygen -N '' -f &quot;${HOME}/.ssh/id_rsa&quot;}}<br /> Create a copy of the public key.<br /> {{Cmd|cp ${HOME}/.ssh/id_rsa.pub ${HOME}/.ssh/YOUR_USERNAME.pub}}<br /> Send the public key to your server by running the command shown below.<br /> {{Cmd|scp ${HOME}/.ssh/YOUR_USERNAME.pub root@YOUR_SERVER_IP:/var/lib/git/YOUR_USERNAME.pub}}<br /> <br /> === In your server set up Gitolite ===<br /> This command will setup gitolite using the public key you just sent to the server.<br /> {{Cmd|su git -c &quot;gitolite setup -pk /var/lib/git/YOUR_USERNAME.pub&quot;}}<br /> {{Warning|There is no need to add password to the default git account that was created automatically by the system. We run git via su git.}}<br /> <br /> === In your workstation set up Gitolite ===<br /> Clone the .git directory to administrate Gitolite outside a server.<br /> {{Cmd|git clone git@${SERVERIP}:gitolite-admin}}<br /> Use your favorite text editor and open the file ${HOME}/gitolite-admin/conf/gitolite.conf<br /> {{Cmd|vim ${HOME}/gitolite-admin/conf/gitolite.conf}}<br /> Add to that file the name of a git repository which Gitolite will manage. It should look something like this:<br /> {{Cat|${HOME}/gitolite-admin/conf/gitolite.conf|&lt;nowiki&gt;<br /> repo gitolite-admin<br /> RW+ = YOUR_USERNAME<br /> repo testing<br /> RW+ = @all<br /> repo YOUR_GIT_REPO<br /> RW+ = YOUR_USERNAME<br /> &lt;/nowiki&gt;<br /> }}<br /> Make commit of what you just changed.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/ commit -am &quot;My new custom repository.&quot;}}<br /> Push the changes to the server.<br /> {{Cmd|git -C ${HOME}/gitolite-admin/&quot; push}}<br /> <br /> === In your workstation, if you don't have a .git, create one ===<br /> Initialize a .git<br /> {{Cmd|git -C ${HOME} init}}<br /> We will add the remote for this new .git. In this case we point the server in which Gitolite was installed, and the repository name we sent before by pushing data via gitolite-admin.<br /> {{Cmd|git -C ${HOME} remote add origin git@YOUR_SERVER_IP:YOUR_GIT_REPO}}<br /> Add some files to your new repository.<br /> {{Cmd|git -C ${HOME} add ${HOME}/.bashrc}}<br /> Create a commit.<br /> {{Cmd|git -C ${HOME} commit -am &quot;This is my first commit.&quot;}}<br /> Push the files to the server. In this case it's being pushed to the server in which Gitolite was installed.<br /> {{Cmd|git -C ${HOME} push --set-upstream origin master}}<br /> <br /> [[Category:Server]]<br /> [[Category:Git]]</div>

Nicolaus https://wiki.alpinelinux.org/w/index.php?title=ZNC&diff=16228 2019-08-20T06:18:15Z

<p>Nicolaus: Created ZNC page. Copypasting from the Znc page with lowercase.</p> <hr /> <div>[https://wiki.znc.in/ZNC ZNC] is an advanced IRC bouncer that can establish such a permanent connection to several IRC networks and channels so your IRC client (or multiple clients) can disconnect/reconnect without losing the chat session, while appearing as a single user to other users.<br /> <br /> == Setting up ZNC ==<br /> Install the package that contains ZNC.<br /> {{Cmd|apk add znc}}<br /> Create a ZNC configuration file, this command will automatically create znc.conf in /var/lib/znc/configs/. You will be asked to enter some information.<br /> {{Cmd|rc-service znc setup}}<br /> {{Note|Make sure the information you enter is as it's shown below.}}<br /> Listen on port: 5000<br /> Listen using SSL: yes<br /> Listen using both IPv4 and IPv6: no<br /> Username: your_username<br /> Enter password: your_password<br /> Confirm password: your_password<br /> Nick: nick<br /> Alternate nick: nick_<br /> Real name: optional<br /> Bind host: try to leave empty<br /> Set up a network? no<br /> Launch ZNC now? no<br /> {{Warning|Never edit the configuration file while ZNC is running; always check with &lt;code&gt;htop&lt;/code&gt; or &lt;code&gt;rc-status&lt;/code&gt; if ZNC is running.}}<br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> == Run ZNC in a subdomain using NGINX ==<br /> <br /> === Configure the ZNC webadmin page ===<br /> <br /> Open the ZNC webadmin page &lt;code&gt;https://YOUR_SERVER_IP:5000&lt;/code&gt; in your browser. Accept the insecure certificate and go forward.<br /> Log in with your username and password and go to global settings.<br /> We want to maintain the webadmin connections separate from the IRC connections.<br /> Let's make a listening port for the IRC connections.<br /> <br /> In Listen Port(s) add:<br /> <br /> Port: 6000<br /> BindHost: *<br /> SSL: on<br /> IPv4: on<br /> IPv6: off<br /> IRC: on<br /> HTTP: off<br /> URIPrefix: /<br /> Save the information you entered and stop the service for now.<br /> {{Cmd|rc-service znc stop}}<br /> Edit the configuration file.<br /> {{Cmd|vim /lib/znc/configs/znc.conf}}<br /> <br /> {{Note|Listener0 is the webadmin port (it's listening port 5000). Listener1 is the webadmin port (it's listening port 6000).}}<br /> Your configuration file should look like this:<br /> <br /> {{Cat|/lib/znc/configs/znc.conf|&lt;nowiki&gt;<br /> &lt;Listener listener0&gt;<br /> Allow IRC = false<br /> AllowWeb = true<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 5000<br /> SSL = false<br /> URIPrefix = /<br /> &lt;Listener listener1&gt;<br /> AllowIRC = true<br /> AllowWeb = false<br /> IPv4 = true<br /> IPv6 = false<br /> Port = 6000<br /> SSL = true<br /> URIPrefix = /<br /> &lt;/nowiki&gt;<br /> }}<br /> <br /> Start ZNC as service.<br /> {{Cmd|rc-service znc start}}<br /> <br /> === Configure NGINX ===<br /> Install NGINX if you haven't already.<br /> {{Cmd|apk add nginx}}<br /> Create a configuration file in conf.d separated from the main configuration files. <br /> {{Cmd|vim /etc/nginx/conf.d/znc.your_domain.com.conf}}<br /> The file should look something like below.<br /> {{Cat|/etc/nginx/conf.d/znc.your_domain.com.conf|&lt;nowiki&gt;<br /> server {<br /> server_name znc.yourdomain.com;<br /> location / {<br /> proxy_pass http://localhost:5000;<br /> proxy_max_temp_file_size 0;<br /> }<br /> }<br /> &lt;/nowiki&gt;<br /> }}<br /> Restart the NGINX service.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> === Set up SSL certificates ===<br /> {{Note|We opt to use SSL certificates made by Let's Encrypt, instead of using the znc.pem certificates that come with the program. If you didn't turn off SSL in listener0 (webpage), you will probably get a lot of errors.}}<br /> Install Certbot and its module to work with NGINX.<br /> {{Cmd|apk add certbot cerbot-nginx}}<br /> Run Certbot, this program will create Let's Encrypt SSL certificates for free. You will have to manually or automatically renew them every month.<br /> {{Cmd|certbot}}<br /> Restart NGINX and you're done.<br /> {{Cmd|rc-service nginx restart}}<br /> <br /> [[Category:Server]]<br /> [[Category:IRC]]</div>

Nicolaus