Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
application.properties [2018/10/08 03:32]
gingerman
application.properties [2019/03/03 02:24] (current)
armchairguru
Line 2: Line 2:
  
 **Changes to this file will require you to restart the bot.** **Changes to this file will require you to restart the bot.**
- 
-[[application.properties1|Click here for Version 1 settings]] 
  
   * [[application.properties#​General Settings]]   * [[application.properties#​General Settings]]
Line 26: Line 24:
 [[application.properties#​trading.exchange]] = BINANCE\\ [[application.properties#​trading.exchange]] = BINANCE\\
 [[application.properties#​trading.log_history]] = 8\\ [[application.properties#​trading.log_history]] = 8\\
 +[[application.properties#​trading.signal_providers]] = \\
  
 [[application.properties#​server.timezone_offset]] = +00:00\\ [[application.properties#​server.timezone_offset]] = +00:00\\
 +[[application.properties#​server.timezone]] = America/​New_York \\
 [[application.properties#​server.language]] = engb\\ [[application.properties#​server.language]] = engb\\
 [[application.properties#​server.skin]] = dark\\ [[application.properties#​server.skin]] = dark\\
Line 41: Line 41:
 [[application.properties#​telegram|telegram.bot_token_1]] = \\ [[application.properties#​telegram|telegram.bot_token_1]] = \\
 [[application.properties#​telegram|telegram.chat_1]] = \\ [[application.properties#​telegram|telegram.chat_1]] = \\
 +[[application.properties#​telegram.new_signal_notification]] = true\\
 [[application.properties#​telegram.disable_notification]] = false\\ [[application.properties#​telegram.disable_notification]] = false\\
  
 [[application.properties#​discord|discord.bot_token_1]] = \\ [[application.properties#​discord|discord.bot_token_1]] = \\
 [[application.properties#​discord|discord.chat_1]] = \\ [[application.properties#​discord|discord.chat_1]] = \\
 +[[application.properties#​discord.new_signal_notification]] = true\\
 +[[application.properties#​discord.new_signal_notification_channel]] = \\
  
 [[application.properties#​api_keys|default_api_key]] ​         = The Exchange API key registered with PT Assistant\\ [[application.properties#​api_keys|default_api_key]] ​         = The Exchange API key registered with PT Assistant\\
Line 60: Line 63:
 #testmode does paper trading so you will see buy and sell activity.\\ #testmode does paper trading so you will see buy and sell activity.\\
 [[application.properties#​server.test_mode]] = true\\ [[application.properties#​server.test_mode]] = true\\
 +[[application.properties#​server.use_testnet]] = false\\
  
 #timeout in seconds\\ #timeout in seconds\\
Line 65: Line 69:
  
 #enabling debug mode\\ #enabling debug mode\\
 +[[application.properties#​logging.live_stoploss_trigger_update]] = true \\
 [[application.properties#​logging.level.nl.komtek]] = DEBUG\\ [[application.properties#​logging.level.nl.komtek]] = DEBUG\\
 [[application.properties#​logging.level.nl.komtek.pt.services]] = TRACE\\ [[application.properties#​logging.level.nl.komtek.pt.services]] = TRACE\\
Line 108: Line 113:
 trading.exchange = BITTREX trading.exchange = BITTREX
 </​file>​ </​file>​
-Use to set the exchange you want the bot to connect to. Possible values (POLONIEX, BITTREX, BINANCE).+Use to set the exchange you want the bot to connect to. Possible values (POLONIEX, BITTREX, BINANCE, KUCOIN, HUOBI, BITMEX).
 Must be in CAPITALS. Must be in CAPITALS.
 ---- ----
Line 117: Line 122:
 </​file>​ </​file>​
 Set the unique text you wish to appear in the browser tab (website title). This it also used in [[application.properties#​Discord]] and [[application.properties#​Telegram]] Notifications Set the unique text you wish to appear in the browser tab (website title). This it also used in [[application.properties#​Discord]] and [[application.properties#​Telegram]] Notifications
 +
 ---- ----
 == trading.log_history == == trading.log_history ==
  
 <file java> <file java>
-trading.log_history = 7+trading.log_history = 8
 </​file>​ </​file>​
 Set how many days of sell log history to show in the GUI. Once the set number of days passes, older history will be **removed** from the bot. Set this for as long as you want to hold the sales history in ProfitTrailer. With [[Pro Features#​PTTracker]] now included with any PRO license ProfitTrailer PRO users will be able to maintain an indefinite history in Tracker regardless of how many days are stored in ProfitTrailer. Set how many days of sell log history to show in the GUI. Once the set number of days passes, older history will be **removed** from the bot. Set this for as long as you want to hold the sales history in ProfitTrailer. With [[Pro Features#​PTTracker]] now included with any PRO license ProfitTrailer PRO users will be able to maintain an indefinite history in Tracker regardless of how many days are stored in ProfitTrailer.
  
-The bot can easily manage a a couple of months of history. The maximum value is 1826 days (5 years). ​+The bot can easily manage a a couple of months of history. The maximum value is 1826 days (5 years). 
 + 
 +**Note: Database backups are only created when the bot is booted; the DB is locked otherwise. Backups are stored in the /​data/​backups folder.** 
 + 
 +---- 
 +== trading.signal_providers == 
 + 
 +<file java> 
 +trading.signal_providers = SGNLAWESOMESIGNALS,​ SGNLPTTRADINGVIEW 
 +</​file>​ 
 + 
 +Define the Signal providers you wish to receive signal from. This property is **only required** if your bot is receiving signals from **multiple providers**. 
 +If you have signed up for 3 signal providers and you want a certain bot to receive signals from only 2 of those providers. You can define the providers you want to use separated by a comma.  
 + 
 +The valid values are the SKU from the ProfitTrailer shop **without the trailing number**. 
 + 
 +{{::​signal_sku.png?​180&​direct|}} 
 ---- ----
 == server.timezone_offset == == server.timezone_offset ==
Line 134: Line 157:
 Set your desired timezone relative to where you live. Important Correct format +hh:mm or -hh:mm Set your desired timezone relative to where you live. Important Correct format +hh:mm or -hh:mm
 See **[[https://​www.timeanddate.com/​time/​map/​]]** if you have no idea what timezone you live in. See **[[https://​www.timeanddate.com/​time/​map/​]]** if you have no idea what timezone you live in.
 +
 +**Note:**
 +  - ''​[[application.properties#​server.timezone]]''​ will be used instead of the offset if it is entered.
 +
 +----
 +== server.timezone ==
 +
 +<file java>
 +server.timezone = US/Central
 +</​file>​
 +Valid Values: [[https://​garygregory.wordpress.com/​2013/​06/​18/​what-are-the-java-timezone-ids|Java Time Zones]]
 +
 +Set the timezone ID of the location you live. This will take precedence over ''​[[application.properties#​server.timezone_offset]]''​ and will automatically handle daylight saving times.
  
 ---- ----
Line 244: Line 280:
  
 ---- ----
 +== telegram.new_signal_notification ==
  
 +<file java>
 +telegram.new_signal_notification = true
 +</​file>​
 +Set to true to enable a notification to be sent when a new [[Signals|signal]] is received.
 +
 +----
 == telegram.disable_notification == == telegram.disable_notification ==
  
Line 251: Line 294:
 </​file>​ </​file>​
 Set to true disable the sound on telegram notifications. Set to true disable the sound on telegram notifications.
- 
  
 ---- ----
Line 280: Line 322:
 </​file>​ </​file>​
 Your first Discord bot token. ​ Your first Discord bot token. ​
 +
 ---- ----
 == discord.chat_1 == == discord.chat_1 ==
Line 287: Line 330:
 </​file>​ </​file>​
 The channel name that the bot will post notifications in. The channel name that the bot will post notifications in.
 +
 ---- ----
 == discord.bot_token_2 == == discord.bot_token_2 ==
Line 294: Line 338:
 </​file>​ </​file>​
 Your second Discord bot token. ​ Your second Discord bot token. ​
 +
 ---- ----
 == discord.chat_2 == == discord.chat_2 ==
Line 301: Line 346:
 </​file>​ </​file>​
 The channel name that the second bot will post notifications in. The channel name that the second bot will post notifications in.
 +
 +----
 +== discord.new_signal_notification ==
 +
 +<file java>
 +discord.new_signal_notification = true
 +</​file>​
 +Set to true to enable a notification to be sent when a new [[Signals|signal]] is received.
 +
 +----
 +== discord.new_signal_notification_channel ==
 +
 +<file java>
 +discord.new_signal_notification_channel = channel name
 +</​file>​
 +Set a separate channel for new SIGNAL notifications to be sent to. If nothing is set ''​discord.chat_1''​ will be used instead.
 +
 ---- ----
 == discord.startup_notification == == discord.startup_notification ==
Line 308: Line 370:
 </​file>​ </​file>​
 Set to true to add discord notifications on startup. Set to true to add discord notifications on startup.
 +
 ---- ----
 == discord.shutdown_notification == == discord.shutdown_notification ==
Line 357: Line 420:
   - Even if you ran a live bot and a test mode bot side by side the results would sometimes differ. The test mode bot will assume all attempts to buy or sell were successful where as if it were live it might have expired. ​   - Even if you ran a live bot and a test mode bot side by side the results would sometimes differ. The test mode bot will assume all attempts to buy or sell were successful where as if it were live it might have expired. ​
  
 +----
 +== server.use_testnet ==
 +
 +<file java>
 +server.use_testnet = true
 +</​file>​
 +Set to true to use the test net instead of the live net on Bitmex. ​
 +
 +**Notes:**
 +  - Not applicable to any other exchanges.
 +  - unlike ProfitTrailers [[application.properties#​server.test_mode]] the Bitmex testnet is not using the exact same data as the live net.
  
 ---- ----
Line 482: Line 556:
  
 **WARNING:​** The log file will contain sensitive information such as your API Keys. If subsequently providing screenshots to support, be sure to censor such information. **WARNING:​** The log file will contain sensitive information such as your API Keys. If subsequently providing screenshots to support, be sure to censor such information.
 +----
 +
 +\\
 +**[[application.properties|TOP]]**
 +\\
 +
 +----
 +== logging.live_stoploss_trigger_update ==
 +
 +<file java>
 +logging.live_stoploss_trigger_update = true
 +</​file>​
 +
 +Normally we log when trailing stop loss starts and every minute if it moves up we log that too. When this property set to true we will log every time it moves up. No need to wait 1 minute.
 +
 ---- ----
  
  • application.properties.1538969563.txt.gz
  • Last modified: 5 months ago
  • by gingerman