Product Features
- 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 …
- News
- Last Updated: December 12, 2007
- Adam Wiggins
Sometimes, it’s the little things. A few niceties deployed recently:
The code editor UI now has a liquid layout. If you’re a life hacking / GTD type like me, you’ll especially enjoy this in combination with Firefox’s fullscreen mode. (FF for OS X doesn’t have fullscreen, unfortunately; try this instead.)
Download files from the context menu. You can use this in conjunction with upload to edit in your local editor, load an image into your photopaint program, etc.
Speaking of images, if you click on an image, it will display it in the editor pane.
There’s a link to update …
- News
- Last Updated: December 02, 2007
- Adam Wiggins
We’ve been working our tails off over the past few weeks to process all the feedback you guys have been sending (or that we’ve gleaned from the system logs). I think that this photo of the trashcan under Orion’s desk tells the story pretty well:
He bought that case of Rockstar at Costco last week, and consumed it all as part of our mad dash to squash bugs exposed by our sudden surge of users. Bad for Orion’s health, but good for Heroku’s backend stability. 🙂
One major area we’ve been dealing with in this past week is the issue …
- News
- Last Updated: November 23, 2007
- Adam Wiggins
One of the many benefits of Rails is database independence. Migrations are particularly nice in this regard; and the easy-to-read / Rubyified display of your schema (via rake db:schema:dump) in schema.rb is icing on the cake.
But what about data? For import and export of the actual data, we’re stuck with mysqldump (or pg_dump, if you’re so inclined). Further, these dump formats are not terribly readable, contain lots of information you may or may not want to copy (like permissions, schema settings, views, triggers…you know, database features that Rails users are supposed to avoid).
Worst of all, ddata dumps are …
Subscribe to the full-text RSS feed for Product Features.