Manually Deploying with GitHub Checkout

• Configure your webserver to allow .htaccess files e.g.;

  <VirtualHost *:80>
      ServerAdmin security@packetflagon.is
      DocumentRoot /HighIO/www/domains/YOURSERVERNAME
      ServerName YOURSERVERNAME.TLD
      ServerAlias www.YOURSERVERNAME.TLD
      ErrorLog logs/YOURSERVERNAME-error_log
      CustomLog logs/YOURSERVERNAME-access_log common
      <Directory />
        Options FollowSymLinks
        AllowOverride All
      </Directory>
  </VirtualHost>
  

• Checkout the repo; git clone https://github.com/RoutingPacketsIsNotACrime/PacketFlagon.git /HighIO/www/domains/YOURSERVERNAME/ with your own
• Generate a new API key curl https://packetflagon.is/api/create -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 https://github.com/RoutingPacketsIsNotACrime/Automation
• Generate a new API key curl https://packetflagon.is/api/create -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;

  default_attributes(
      "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!