computer servers

Manually Deploying with GitHub Checkout

  • Configure your webserver to allow .htaccess files e.g.;
    <VirtualHost *:80>
        DocumentRoot /HighIO/www/domains/YOURSERVERNAME
        ServerAlias www.YOURSERVERNAME.TLD
        ErrorLog logs/YOURSERVERNAME-error_log
        CustomLog logs/YOURSERVERNAME-access_log common
        <Directory />
          Options FollowSymLinks
          AllowOverride All
  • Checkout the repo; git clone /HighIO/www/domains/YOURSERVERNAME/ with your own
  • Generate a new API key curl -d "{'domain':'YOURSERVERNAME.TLD','contact':'youremail@YOURSERVERNAME.TLD'}"
  • Edit the libs/config.sample.php and save as libs/config.php
  • Create the directory templates_c and ensure PHP can write to it (chmod 755)
  • Restart your webserver
  • Done!

Automation with Chef

  • Checkout and merge the PacketFlagon automation repository; git clone
  • Generate a new API key curl -d "{'domain':'YOURSERVERNAME.TLD','contact':'youremail@YOURSERVERNAME.TLD'}"
  • Edit the attributes for the node or role that will have the packetflagon_frontend applied to include;
        "packetflagon" => {
            "fqdn" => "YOURSERVERNAME.TLD",
            "shard-name" => "FRIENDLY NAME FOR YOUR SHARD",
            "force-https" => false,
            "credit" => "YOUR NAME",
            "apikey" => "YOUR API KEY FROM CURL"
  • Apply the packetflagon_frontend role to the node in question
  • Run chef client
  • Done!

Other Browsers

Instructions for configuring other browsers are below;

If you need help with any other browsers you can send an email to, or tweet to @PacketFlagon or jump on #RoutingPacketsIsNotACrime on freenode.