Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can look at SCuMD GIT Server. I described it's basic configuration here:</p> <p><a href="https://stackoverflow.com/questions/4033528/best-mac-osx-and-windows-git-clients-servers-and-diff-tools/4775915#4775915">Best Mac OSX and Windows Git Clients, servers and diff tools?</a></p> <p>It supports email-notifications (and a lot of other cool stuff like DB user authorization, independent SSH server, etc...).</p> <p>Here is example config with e-mail notifications:</p> <pre><code>&lt;beans:beans xmlns="http://asolutions.com/schema/spring/scumd" xmlns:beans="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://asolutions.com/schema/spring/scumd http://asolutions.com/schema/spring/scumd/scumd-0.1.0.xsd"&gt; &lt;git-ssh-server port="1122" repositories-base="${gitRepos}"&gt; &lt;default-server-key-pair /&gt; &lt;listeners&gt; &lt;!-- Email listener will send emails to provided email/users/groups(all users in each group) when event is triggered. Each configuration element can be defined either as attribute or inner tag. event attribute can have following values: * authenticationSuccess * authenticationFail * authorizationSucces * authorizationFail * repoCreate * pull * push * commit Note: If you want to use email listeners, you should also define &lt;email-sender /&gt; tag. --&gt; &lt;email event="push" emails="mu@email.com, hello@world.com" subject="My Notification!"&gt; &lt;users&gt;u1, u2&lt;/users&gt; &lt;groups&gt;g1, g2&lt;/groups&gt; &lt;/email&gt; &lt;/listeners&gt; &lt;/git-ssh-server&gt; &lt;!-- If you are using email listeners, you should also define email-sender in order to define SMTP/SMTPS configuration --&gt; &lt;email-sender host="my.host" port="465" protocol="smtps" auth="true" user="mailsUser" password="secret" from="git@admin.com" replay-to="git@admin.com" force-email="test@test.com" /&gt; &lt;acl&gt; &lt;repository path="**/*.git"&gt; &lt;groups allow="ReadWrite, Create" list="g1, g2" /&gt; &lt;/repository&gt; &lt;/acl&gt; &lt;simple-user-dao&gt; &lt;group name="g1"&gt; &lt;user name="u1" email="hello@test.com"&gt; &lt;public-key file="/path/to/the/id_rsa.pub" /&gt; &lt;public-key file="/path/to/the/other/id_rsa.pub" /&gt; &lt;/user&gt; &lt;user name="u2" email="u2@test.com"&gt; &lt;public-key file="/path/to/another/key" /&gt; &lt;/user&gt; &lt;/group&gt; &lt;group name="g2" /&gt; &lt;/simple-user-dao&gt; &lt;/beans:beans&gt; </code></pre> <p>Server is still at beta stage, but it's fully functional and we using it at work (no problems yet).</p>
    singulars
    1. This table or related slice is empty.
    1. POgit remote branch monitoring
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. UStenshi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POgit remote branch monitoring
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload