rkst

{
	"always_show_minimap_viewport": true,
	"bold_folder_labels": true,
	"color_scheme": "Packages/Material Theme/schemes/Material-Theme.tmTheme",
	"enable_tab_scrolling": false,
	"font_options":
	[
		"gray_antialias"
	],
	"font_size": 12,

rkst

Goodbye logplex_token, Hello log_input_url

Rather than provide a log token, we’ll now send a full URL, log_input_url. In the future, EU app logs will be serviced by logging infrastructure in the European region, which will be great news for customers concerned about data transit and residency.

The full documentation for this integration is available here. We will be migrating completely to these changes by October 15th, 2014.

Log input is now opt-in

Any add-on that had stored the logplex_token could use it to send log lines to an application. This method is being phased out and replaced by one that requires providers who wish to input logs to opt-in by adding “log_input” to the requires property of their add-on manifest.

Migrating from logplex_token

If you’re already using logplex_token to send us logs, then there are a number of steps you need to take to continue

rkst

Keybase proof

I hereby claim:

• I am rkst on github.
• I am rkst (https://keybase.io/rkst) on keybase.
• I have a public key whose fingerprint is D3DF D8DE A7F9 31D1 7B1F 5FBA CA18 02D6 B51C A183

To claim this, I am signing this object: