fix flightplan to new do server

config.js

@@ -1,7 +1,6 @@
 module.exports = {
   telegram_api_key: process.env.TELEGRAM_API_KEY,
   database: process.env.MONGO_DB_URL,
-  staging_url: process.env.ARBEIT_BOT_STAGING_URL,
   production_url: process.env.ARBEIT_BOT_PRODUCTION_URL,
   should_use_webhooks: process.env.USE_WEBHOOKS || false,
   webhook_callback_url: process.env.WEBHOOK_CALLBACK_URL,

flightplan.js

@@ -8,13 +8,6 @@ const username = 'deploy';
 const tmpDir = `${appName}-${new Date().getTime()}`;
 
 /** Configuration */
-plan.target('staging', [{
-  host: config.staging_url,
-  username,
-  privateKey: config.ssh_rsa_path,
-  agent: process.env.SSH_AUTH_SOCK,
-}]);
-
 plan.target('production', [{
   host: config.production_url,
   username,

readme.md

@@ -53,7 +53,6 @@ So, you decided to help us out — good, good. First, ArbeitBot can be launched
 * *(Optional)* `WEBHOOK_CALLBACK_URL` — url that should be used by Telegram servers for webhooks, should be `https`
 * *(Optional)* `SSL_CERTIFICATE_PATH` — path to ssl certificate for webhooks
 * *(Optional)* `SSH_RSA_PATH` — path to ssh private certificate for webhooks (should not be password encrypted)
-* *(Optional)* `ARBEIT_BOT_STAGING_URL` — url of your staging server for flightplan (if you use flightplan)
 * *(Optional)* `ARBEIT_BOT_PRODUCTION_URL` — url of your production server for flightplan (if you use flightplan)
 
 ### How to get ssl certificate and key