manager

Linode | Software Developer | Python, Perl | ONSITE: Philadelphia | Full-time | https://www.linode.com/careers Linode | Front-end Developer | Javascript | ONSITE: Philadelphia | Full-time | https://www.linode.com/careers Obligatory marketing copy: Linode was launched in June of 2003 by founder Christopher S. Aker. Initial development took about 6 months. Linode was ahead of its time and helped define the cloud hosting industry, and continues to be a leader in virtualization hosting. Check out the (open source) work we're doing on the replacement for our classic frontend [0] and get a glimpse at the work we're doing on spicing up our API [1]. Contact info is in my profile if you'd like to chat! [0] https://github.com/linode/manager [1] https://developers.linode.com/v4/introduction

Linode | Software Developer | Python, Perl | ONSITE: Philadelphia | Full-time | https://www.linode.com/careers Linode | Front-end Developer | Javascript | ONSITE: Philadelphia | Full-time | https://www.linode.com/careers Obligatory marketing copy: Linode was launched in June of 2003 by founder Christopher S. Aker. Initial development took about 6 months. Linode was ahead of its time and helped define the cloud hosting industry, and continues to be a leader in virtualization hosting. Check out the (open source) work we're doing on the replacement for our classic frontend [0] and get a glimpse at the work we're doing on spicing up our API [1]. Contact info is in my profile if you'd like to chat! [0] https://github.com/linode/manager [1] https://developers.linode.com/v4/introduction

Linode | Software Developer | Python, Perl | ONSITE: Philadelphia | Full-time | https://www.linode.com/careers Linode | Front-end Developer | Javascript | ONSITE: Philadelphia | Full-time | https://www.linode.com/careers Obligatory marketing copy: Linode was launched in June of 2003 by founder Christopher S. Aker. Initial development took about 6 months. Linode was ahead of its time and helped define the cloud hosting industry, and continues to be a leader in virtualization hosting. Check out the (open source) work we're doing on the replacement for our classic frontend [0] and get a glimpse at the work we're doing on spicing up our API [1]. Contact info is in my profile if you'd like to chat! [0] https://github.com/linode/manager [1] https://developers.linode.com/v4/introduction

They are rewriting it, and it's underlying api. https://github.com/linode/manager https://developers.linode.com/v4/introduction

Yes, we do have plans to replace the current web UI. :) It is an open source app you can follow along with the development on github [0]. And I can't say much myself, but I believe TechCrunch has us quoted as planning to release this in beta in a few months. :) And actually, we have considered both being able to mass-provision Linodes through the web UI and use SSH keys instead of passwords. But the mass-provision part sort of got swept under the rug for beta. Then fwiw the API is also being redone with more features and written completely in Python. You can finds docs for that here [1]. You can also sign up for alpha access today and play around with the new API (and free [temporary] Linodes!), as well as set up the manager locally [2]. Work email's in the bio if you need anything else! [0] https://github.com/linode/manager [1] https://d

We do think our dashboard is important, and we are investing in it. As a matter of fact, you can even watch the development take place yourself because the new manager is an open-source app. :) https://github.com/linode/manager

>but I believe they still use their old coldfusion applications. For now, yeah. But the new Manager mentioned in the blog post is just a client for our new API, which is written in Python.[1] You can even check out the new Manager now if you want: https://github.com/linode/manager It's still in alpha (and separate from our regular service), but we're hoping to have it out in beta soon! [1] https://engineering.linode.com/2016/04/12/Announcing-APIv4.h...

Yeah, definitely! Another cool example is the pre-alpha for Linode's new management UI: https://github.com/linode/manager

I helped out a lot with this codebase, it's well on its way to becoming a production React SPA: https://github.com/Linode/manager

Linode | https://linode.com | Philadelphia, PA | FULL-TIME, ONSITE Linode primarly sells virtual private servers, among other products. We're hoping to hire some new software developers. My team works on an entirely open source product - the Linode manager https://github.com/Linode/manager, an ES6+7 React frontend application. We also need help working on our Python+Flask API: https://developers.linode.com Check out our engineering blog: https://engineering.linode.com Apply at the careers page: https://linode.com/careers. Feel free to reach out on HN or via email (see profile) if you have questions. Relocation assistance is provided.

> I see a few people^W^Weveryone here talking about security. If you didn't read the whole blog post, you might not have noticed the new Linode manager that we're working on being mentioned. Check it out, it's open source: https://github.com/Linode/manager Open sourcing the UI while keeping the actual portion that manipulates the data + handles authentication ( the API ) doesn't have substantial security benefits since its largely available to the end user already. While I am sure you are correct that the rewrite in Python is easier to reason about and more secure, I feel the way you've presented it might imply it is secure because the source is available which is not the case.

[Disclaimer: Linode dev here] I see a few people^W^Weveryone here talking about security. If you didn't read the whole blog post, you might not have noticed the new Linode manager that we're working on being mentioned. Check it out, it's open source: https://github.com/Linode/manager If you haven't been present in other discussions about Linode security, one of the major factors (in my opinion) is the current manager. It's a large and old ColdFusion codebase, and it's hard to maintain. The new manager is backed by the new Python API and the whole system is significantly easier to reason about with respect to security. I think that the new manager should help ease some concerns, and it's going to be pretty great in other respects too. Hit me up with any questions you have, I'll do my best. In other news, I run a bunch of Linodes myself and

I just pushed an effort at Linode to open source our new manager website: https://github.com/Linode/manager I think it will avoid these pitfalls. It is a learning resource because I hope that someone will read it instead of spending the weeks we had to spend figuring out how to set up the ideal frontend web project in 2016. I also hope that it'll get some exposure among those millions of open source JavaScript projects by simply inheriting our customerbase. Unfortunately, though, I don't realistically see many external contributions coming into the manager. It hits all of the points that make it easy to contribute (it's not my first open source project by a wide margin), but I would be surprised to see many contributions despite that.