newfeatures
- News
- Last Updated: May 02, 2024
- James Lindenbaum
Since launching Ruby support in 2007, we’ve been constantly expanding the platform to accommodate more application types and to make the platform more accessible to a broader audience of developers. We are very pleased today to announce full support for applications written in the Logo programming language. Going back to our roots with an in-browser editor, we believe that interactive programming and getting started quickly lend well to learning. Ruby is an excellent language for learning, and Logo is even better. Logo is a fully-featured and beautifully designed functional Lisp-style programming language. It shares many properties with (and is an…
- News
- Last Updated: April 29, 2024
- Adam Wiggins
Our goal for the Heroku platform has been to create a totally smooth and seamless experience for getting your Ruby web application online. Web apps revolve around one or more dynamic web processes: what Rubyists often call a mongrel, and what we call a dyno. When it comes to dynos, we think we’ve really nailed it, and nothing makes that more tangible than the ease of scaling your app with the dyno slider. But most serious web apps have a second aspect: one that gets less attention, but one that is often just as important as the web process. Like…
- News
- Last Updated: June 03, 2024
- Morten Bagai
Since we returned from a fun and successful Railsconf in Vegas, we have been in full swing completing the rollout of our paid services. The response has been enormous so far, and paid services are now available to all users. If you’ve checked out the pricing page, you’ve undoubtedly noticed our line-up of a la carte add-ons. We’re really excited about add-ons becoming a key part of our platform, allowing us to seamlessly deliver popular application services and components with the built-in scalability and ease of use you’ve come to expect from Heroku. We’ve had a solid first batch of…
- News
- Last Updated: May 06, 2024
- Adam Wiggins
Say you’re working on a [Rails app](https://www.heroku.com/ruby), and you want to publish your code on Github. Most apps have some deploy-specific private config values – for example, if you’re using the S3 storage back-end for Paperclip, and your S3 keys are saved in config/amazon_keys.yml. You certainly don’t want to push those up to Github – what to do? You could maintain a separate deploy branch, and commit your deploy config only to that. You can then work on the main branch, and rebase the deploy branch whenever you go for a deploy. That’s a bit of extra work you could…
- News
- Last Updated: September 03, 2008
- Adam Wiggins
The Heroku API gets a major update today; you can now view and manage all of your application’s settings straight from the command line. New in this version: Manage sharing (add/remove/list collaborators) Manage multiple ssh keys for your user (add/remove/list keys) Update settings (public true/false, mode production/development) Rename an app Run rake tasks remotely A taste of the new command-line goodness: adam@kvasir:~$ heroku create gagetron Created http://gagetron.heroku.com/ | git@heroku.com:gagetron.git adam@kvasir:~$ heroku info gagetron === gagetron Web URL: http://gagetron.heroku.com/ Git Repo: git@heroku.com:gagetron.git Mode: development Public: false Collaborators: adam@example.com (edit) adam@kvasir:~$ heroku sharing gagetron –add joe@example.com joe@example.com added as a view-only collaborator…
- News
- Last Updated: June 03, 2024
- Adam Wiggins
Heroku now has an API (accessible from the command line, a Ruby library, or REST calls), revision control on all apps with Git, and remote access to the Git repository. The combination of these new features means that you can now work on your apps using the local tools you love – like TextMate, vi, or emacs – and still get the benefit of zero-configuration deployment to Heroku. How does it work? Grab the Heroku gem with “gem install heroku”. A sample work session looks like this: heroku clone myapp cd myapp ruby script/server …edit locally… git add . git…
- News
- Last Updated: March 26, 2024
- Adam Wiggins
Backstory: A Fiery Debate Writing a user model and the standard login authentication code seems like busywork to a lot of coders. In fact, many people expected a next-generation app framework such as Rails to handle this for you. After all, Django does. Initially the login engine for Rails seemed to fill this slot, but following a fair amount of controversy over best practices, the login engine was killed by its creator. With our BDfL having forever cursed prebuilt login systems, the Rails community mostly stopped trying to make them. Yet, this puts us back at square one: developers are…
- News
- Last Updated: January 03, 2008
- Adam Wiggins
RSpec 1.1 is now a part of the default plugin kit for Heroku apps. We’ve been fans of RSpec for a while now, and feel that it represents the future of TDD/BDD for the Rails world. If you’re not familiar with RSpec, read up and then give it a try. You don’t need to install anything to use RSpec in your Heroku app, but you do need to initialize the spec/ and stories/ directories by running the rspec generator. Just open the Generate dialog, type in rspec, and click Run. Once you’ve written some specs, you can run them the…
- News
- Last Updated: January 03, 2008
- Adam Wiggins
There are now two access levels for collaborators on Heroku apps: Full edit access, which allows access to everything: editing code, importing or exporting the database, changing the settings, etc. View-only access, which allows the user to view the app only. That is, they can visit the app url (myapp.heroku.com) but not any of the settings pages or the edit url (edit.myapp.heroku.com). For example, a client who wants to use the app but neither needs nor wants access to the code could be set as a view-only user. If your app sharing is set to public, the view-only access level…
- News
- Last Updated: May 30, 2024
- Adam Wiggins
Behold: the Heroku gems/plugins manager. This has been one of our most requested features to date, and we’re glad to finally get this released. Although you could manually upload plugins previously, this will make the process a lot smoother. (You can still manually manipulate the files in your vendor directory if you prefer.) To get to the manager, open your vendor directory in the lefthand filenav, and click the link that appears at the top: You can search by name, or browse the list of 2500+ gems and 1000+ plugins. Once you find what you’re looking for, click on Install…
Subscribe to the full-text RSS feed for James Lindenbaum.