Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The part which is complex is the <a href="https://help.github.com/articles/post-receive-hooks" rel="nofollow noreferrer">webhook on GitHub</a></p> <blockquote> <p>Every GitHub repository has the option to communicate with a web server whenever the repository is pushed to.</p> </blockquote> <p>That means your web site must have a process listening to those JSON messages sent by GitHub upon reception of a commit.</p> <p>You can see multiple examples of those listeners, like this <a href="https://github.com/CodeWithGrid/webhook-deployer" rel="nofollow noreferrer">webhook-deployer</a>, with an auto.php (for a php server):</p> <pre class="lang-php prettyprint-override"><code>&lt;?php // Prevent accidental XSS header("Content-type: text/plain"); // Run the script if ( $_POST['payload'] ) { shell_exec("./pull.sh"); } </code></pre> <p>That GitHub project recommends an SSH key with no passphrase, which I agree <em>at first</em> (to test it out).<br> However, especially for private projects, it is best to run an ssh-agent and manage an ssh key passphrase protected.<br> As janos <a href="https://stackoverflow.com/questions/17367247/pushing-from-github-to-a-web-server/17367501?noredirect=1#comment30049450_17367501">comments</a>:</p> <blockquote> <ul> <li>If the GitHub repository is public, then he doesn't even need one. </li> <li>If the repo is private, then he needs it, but this should not be taken so lightly. If possible he should use a key agent.<br> If that's too complicated then he could use a dedicated SSH key without passphrase just for this deployment, and that key should never leave the deployment PC.</li> </ul> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POPushing from GitHub to a Web Server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy do you encourage SSH keys without a passphrase? If the GitHub repository is public, then he doesn't even need one. If the repo is private, then he needs it, but this should not be taken so lightly. If possible he should use a key agent. If that's too complicated then he could use a dedicated SSH key without passphrase just for this deployment, and that key should never leave the deployment PC.
      singulars
      1. PO
      1. USjanos
    2. CO@janos very good points. I have amended the answer and included your points in it, for more visibility.
      singulars
      1. PO
      1. USVonC
 

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