On Wed, Apr 4, 2012 at 6:13 PM, Eric Jain eric.j...@gmail.com wrote:
If I follow the instructions at
https://devcenter.heroku.com/articles/external-services,
any Heroku app will be able to connect to my security group. Correct?
Correct.
Adam
--
You received this message because you are
How about a FIFO? Use mkfifo to create a named pipe inside your
ephemeral filesystem, then launch your two child processes. One can
write to it, the other can read. So using your bash example:
$ heroku run bash
~ $ mkfifo myfifo
~ $ cat myfifo | ./run_listener_process
~ $
On Fri, Nov 25, 2011 at 11:16 AM, anentropic bluesk...@gmail.com wrote:
Is this broadly comparable to Heroku... i.e. the whole 512MB is
available to user processes?
Yes, all 512MB goes to your processes.
Adam
--
You received this message because you are subscribed to the Google Groups
On Fri, Nov 25, 2011 at 12:55 PM, anentropic bluesk...@gmail.com wrote:
I found a place in the FAQs where it says Each application receives
750 free dyno hours per month but would like to confirm that it
really is per app.
Correct, it's per-app.
Adam
--
You received this message because
Slugs don't have git repositories in them. Something in your app is trying
to do a Git operation when it boots -- you should figure out what it is and
remove it.
You can duplicate it locally by moving your .git directory to .git-bak, and
then try running your app.
Adam
--
You received this
What do you run locally to get a console? Whatever it is, prefix it
with `heroku run` and you should be set. e.g. if you normally type:
$ bundle exec rails console
Then to run remotely:
$ heroku run 'bundle exec rails console'
Or if it's a Sinatra app:
$ bundle exec irb -r ./web
You might try putting this at the top of your email:work task:
STDOUT.sync = true
Ruby buffers output by default, which can cause it to delay appearing in the
logs until you have enough output.
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku
On Tue, Oct 11, 2011 at 7:32 PM, Karl threadh...@gmail.com wrote:
2011-10-11T20:53:27+00:00 app[web.1]: cache: [POST /printed.xml]
invalidate, pass
What does the cache: [...] invalidate, pass mean?
Note that the log originates with your app, process name web.1. This is
coming from your
On Mon, Jul 11, 2011 at 9:51 AM, Neil Middleton neil.middle...@gmail.comwrote:
ruby-1.9.2 ~/code/rest_test (master) ➔ heroku run rake db:migrate
Unknown command. Run 'heroku help' for usage information.
You probably need to update to the latest Heroku gem: `gem install heroku`
Adam
--
Cristiano -
Is your app in maintenance mode?
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For
On Thu, Feb 17, 2011 at 7:15 AM, Michael Abner mike.ab...@gmail.com wrote:
In this situation I would think you'd want to upload to s3 directly and the
fire off a background worker to go and do the resizing for you. That would
keep your web dynos available to serve your requests.
Exactly
On Sun, Jan 30, 2011 at 5:06 PM, Jason Preston jasonp...@gmail.com wrote:
as part of my user model (built from scrach) I explicitly called
require 'Digest' in order to do a one-way hash on user passwords,
I'm guessing that was the issue.
The problem here might be that your local filesystem is
We've got some features in mind that should provide a good solution
for this use-case. In the meantime, the best workaround I can suggest
if you really need this would be to install the advanced logging
add-on, direct the logs to your own syslog instance, and set up some
kind of log analysis
Make sure you have the latest Heroku gem:
$ gem install heroku
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to
On Wed, Dec 15, 2010 at 1:46 PM, Jonas jo...@jonasbnielsen.dk wrote:
For people playing around with the daemons gem, this is the equivalent
of setting the :ontop option to true. (http://daemons.rubyforge.org/
classes/Daemons.html#M04)
I suggest not using the Daemons gem at all. Here's a
Thanks for the thoughtful description of your situation, Josal. We
appreciate your trust and are working very hard to continue to deserve
it!
Regarding unexpected timeouts, what we've seen is that they are almost
always a result of what I call a wedged process. I blogged about this
a couple
We've just rolled out a new version of our process manager, with streamlined
handling of crashed processes. A lot of you guys have been frustrated when
your workers crash (libXML segfaults, for example) because the restart
behavior was somewhat unpredictable.
The new version follows a very
Great discussion in this thread. Matthew, your analysis and
monkey-patch are very impressive! I'm just sorry you guys are stuck
reverse-engineering this portion of our stack to get your apps working
the way you want - that's definitely bad on us. We're hoping to be
able to make heroku_rack open
On Sat, Jul 17, 2010 at 10:57 PM, Ben Schwarz ben.schw...@gmail.com wrote:
Can you explain how dynos work across file systems? Can `/tmp` be
relied upon with multiple dynos? (disregarding the fact that `/tmp`
will be cleared at random intervals.)
Your dynos are running on different machines,
On Sun, Jul 18, 2010 at 5:44 PM, Julio Cesar julio...@gmail.com wrote:
The official docs[1] say:
There is no guarantee that this file will be there on subsequent
requests (although it might be), so this should not be used for any
kind of permanent storage.
And you just pointed out:
and
On Thu, Jul 15, 2010 at 6:50 AM, Maximilian Mack maxm...@gmx.de wrote:
Is there a rails wiki software out there who works with heroku?
http://github.com/adamwiggins/bitswiki
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send
I put together a small example of an html5 offline app using cache
manifest and deployed it to Heroku:
http://cachemanifest.heroku.com/
I used the clock example from the html5 draft:
http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html
Source code:
flush_all isn't possible with the current memcache beta. We've got a
major update coming soon that will add support for this.
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To
On Wed, Jan 20, 2010 at 2:58 PM, morgoth w.wnetr...@gmail.com wrote:
Great. It works perfectly. One downside: this increase slug size.
True. Our experience has been that the many dependency hell issues
that can be avoided by explicitly declaring and bundling all your gems
is well worth the few
On Tue, Jan 19, 2010 at 7:24 AM, Karl threadh...@gmail.com wrote:
I am thinking of using a temporary table, most likely sqlite in memory
table.
This will work, but take note it will only work for a single dyno, and
the contents of the table will disappear periodically when the dyno is
cycled.
If you put a config.ru into the root of your project, you can point to
any rack app (including rails) inside of any arbitrary subdirectory.
If you're using rails, this will work:
subdir = File.dirname(__FILE__) + '/my_subdir'
require #{subdir}/config/environment
use Rails::Rack::LogTailer
use
It uses the version installed in your codebase.
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For
Yes, I set this up as a demo of scanty-redis a while back:
http://scanty-redis.heroku.com/
I put the Redis db on slicehost, described in the third paragraph of this post:
http://adam.blog.heroku.com/past/2009/7/13/scanty_on_redis/
Adam
--
You received this message because you are subscribed
On Fri, Dec 18, 2009 at 7:17 AM, iamjediknight iamjedikni...@gmail.com wrote:
I have a rails app that reads liquid templates off the filesystem, as
well as content (i.e. images, html, etc.). So will I need to store
those via Amazon S3? Is there another way to store content?
Assuming these
On Tue, Sep 8, 2009 at 5:33 AM, Jay Godsejgo...@gmail.com wrote:
Is it possible to point
www.d1.com to myapp.heroku.com/a1
www.d2.com to myapp.heroku.com/a2
Yes, although this has more to do with your web framework than Heroku.
Point both domains at your app:
$ heroku domains:add www.d1.com
On Sun, Aug 16, 2009 at 10:39 AM, Alex Chaffeeale...@gmail.com wrote:
During the few seconds the restart is happening, what happens to
incoming HTTP requests? Are they queued or do they fail? If the
latter, where's the error page and can we change it?
And what's the timing like for applying
On Fri, Aug 14, 2009 at 9:24 AM, orlinorlin.mo...@gmail.com wrote:
If one app has a couple of custom domain names set, and has wildcards
enabled, can I have wildcards turned on just for one of those?
Yes. Enabling the add-on only activates the feature for use, you
specify domains starting
On Thu, Aug 6, 2009 at 11:09 AM, Keenankee...@thebrocks.net wrote:
I'm trying to write a rake task that requires additional data
command:
rake USER=user1 lovdbyless:admin
rake file:
namespace :lovdbyless do
task :admin = :environment do
login=ENV['ADMIN']
You need to use
On Mon, Jul 27, 2009 at 6:23 PM, Nevilleneville.burn...@gmail.com wrote:
Do you have a guide, or blog post perhaps detailing best practice for
deploying Solr on Heroku or is EC2 the only way?
Solr is a Java program, Heroku only runs Ruby programs. So yes, you
need to run it on another server,
On Thu, Jul 9, 2009 at 12:46 PM, Sarah Allensa...@ultrasaurus.com wrote:
$ heroku db:push
Invalid database url
development:
: *defaults
database: mightyverse_dev
I think the issue here is that taps turns the database credentials
into a URL/URI, and URI.parse considers underscore an
On Tue, Jul 7, 2009 at 7:25 AM, Ed Jonesed.jo...@gmail.com wrote:
C:\Users\Ed\webappshost whendidji.com
whendidji.com has address 216.39.57.104
This is your problem. It should read something like this:
C:\ host whendidji.com
whendidji.com is an alias pointing to proxy.heroku.com
Adam
On Mon, Jul 6, 2009 at 7:08 AM, Ed Jonesed.jo...@gmail.com wrote:
Alas, for myapp.com, heroku just gives Heroku | No such app. There is
no app configured at that hostname.
Try:
heroku domains:add myapp.com
Adam
--~--~-~--~~~---~--~~
You received this message
Very nice, Trevor. I wonder if you could write this up into a blog
post somewhere that summarizes the technique? That way we can provide
the link to others that prefer not to use environment variables in
their local setup.
Adam
--~--~-~--~~~---~--~~
You
You're correct Jason, 100 varnish servers would mean that fetching a
single static asset or cached page could produce up to 100 dyno hits.
In practice, I don't think we'd run more than 4 or 5 varnishes in
front of a single application - if it became necessary to do that at
some point, we'd
Interesting discussion in that thread, thanks for the link Sean.
At the moment we're not putting any development effort into allowing
user code into the server-side receive hooks, as this has a lot of
deep design and security ramifications that make it a pretty massive
project. I think it's an
On Wed, May 27, 2009 at 1:27 PM, Harry Vangberg ha...@vangberg.name wrote:
I didn't realize the heroku console was on GitHub, will take a look
at it.
http://github.com/heroku/heroku/blob/85693066c72f86595f03ebeae338134b162639d8/lib/heroku/commands/app.rb#L115-128
This doc is in the works right now, thanks for giving us a friendly
nudge on getting it finished. :)
In the meantime, here's a rough cut of the explanation:
The backlog is the number of requests waiting to be processed. If
you're using the default (one dyno), it can only process one request
at
In the case where you've edited the commits or reset the HEAD to
rewind to an earlier commit, you can force the push like this:
$ git push -f heroku
Note that if you have other people pulling from the Heroku app, they
should probably destroy their master branch and fetch it fresh, to
avoid
Hey folks, we'd been having elevated error rates today (the http 503 /
ouchie guy page). They were very intermittent (just reload and the
next request would usually work) but still very annoying. We tracked
down and resolved the problem, so things should be back to normal now.
Adam
Another fix for this is to alias your domain to point to
proxy.heroku.com instead of heroku.com. i.e.:
$ host mydomain.com
mydomain.com is an alias for proxy.heroku.com.
proxy.heroku.com has address 75.101.145.87
proxy.heroku.com has address 75.101.163.44
Although it reads a little less
On Fri, Apr 24, 2009 at 7:51 AM, Damien MATHIEU kaz...@gmail.com wrote:
When I work on a new feature for my application, I do it in a specific
branch; I commit in that branch.
[...]
For example, have xxx.heroku.com on the branch master of the
application xxx.
And yyy.xxx.heroku.com on the
Try this:
git remote rm heroku
git remote add heroku g...@heroku.com:followme.git
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To
We're working on providing a lot of information about exactly what
resources your app is using. The first small step toward this is that
heroku info will now show some stats about your code and data size:
$ heroku info --app adamblog
=== adamblog
Web URL:http://adamblog.heroku.com/
Git
Guys -
We had some system-wide downtime today, as described in this thread.
We know that downtime is definitely in the not awesome, not at all
category.
Heroku is hitting some serious growth right now. Up until now we've
been focusing all our efforts on making a really seamless deployment
You've stumbled upon a beta feature that is not yet publicly
available. Drop me a private email if you'd like access to this.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this
Tony, can you run sudo gem install taps to get the latest version (Ricardo
has been hard at work fixing numerous edge-case bugs), and then try again?
If you still get an error, post the exact output here.
Adam
--~--~-~--~~~---~--~~
You received this message
Should be fixed now.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to
Timeouts are tricky to debug. One option could be an infinite loop, or
hitting a remote service on startup that is slow or taking a long time.
Another possibility would be something like building a big index, which may
not run infinitely, but if it takes more than 20 seconds we assume a
timeout.
Yes, db:push is a preferred method, if you have the database loaded locally.
Make sure you have the latest version of the heroku and taps gems
installed:
sudo gem install heroku taps
...and then read details here:
http://docs.heroku.com/taps
Adam
One reason this can happen is that the DNS info was cached on the local
nameserver prior to it propagating from your provider (Slicehost, in this
case). In that case you have to wait about 20 minutes for the cache to
clear. Can you try it again right now and let me know if it works?
We've got
You can do multiple domains on Heroku via the command-line tool:
heroku domains:add mydomain1.com
heroku domains:add mydomain2.com
See: http://docs.heroku.com/custom-domains#heroku-setup
Adam
--~--~-~--~~~---~--~~
You received this message because you are
We had a brief issue with one git server this morning. It's fixed now - try
your push again.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to
That's very odd. Github downtime shouldn't affect the Heroku gem, since
it's in Rubyforge.
Can you type gem sources and see if it lists http://gems.rubyforge.org?
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
In addition to Ricardo's solution, I think another thing you can do is just
leave off the database url. You mentioned that you have a
config/database.yml, without specifying a URL it will read from that
automatically. i.e.
$ heroku db:pull
Auto-detected local database:
You can use curl, via the backticks you suggested. However, it would be
more portable to do it with pure Ruby, using a library such as RestClient,
HTTParty, or good ol' fashioned Net::HTTP.
Adam
--~--~-~--~~~---~--~~
You received this message because you are
Heroku doesn't provide a test database, so heroku rake test won't work.
This might be an interesting feature to provide at some point, although
automated CI systems like runcoderun.com may be a better approach than
trying to run tests on a production system.
If you're just tinkering with a new
I ran a manual db:data:dump for saps.herokugarden.com. You should be able
to download the file now.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to
On Sun, Mar 22, 2009 at 3:21 PM, pabloa pablo.flo...@gmail.com wrote:
hi, i am using the rest client gem to connect to a public dictionary
web service via a HTTP GET, but it seems that Heroku does not allow
this connection .
All Heroku apps can send traffic on the web ports (80 and 443), so
Post the contents of your .git/config - maybe your git remote is wrong.
Note that the host portion should be g...@heroku.com, not heroku.com.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To
On Mon, Mar 23, 2009 at 2:40 PM, ptorrsmith ptorrsm...@gmail.com wrote:
$ sudo apt-get install git
This should be:
sudo apt-get install git-core
It's definitely confusing that there is a package named git on Debian
which is not the Git revision control system.
Adam
One catch here - make sure you're running on heroku.com.
herokugarden.comdoes not have Rails 2.3 installed.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to
I get this same error running locally. I was able to fix it by changing
this line:
On Sun, Mar 15, 2009 at 12:00 PM, Nick Dimiduk ndimi...@gmail.com wrote:
config.gem 'mislav-will_paginate', :version = '~ 2.2.3', :lib =
'will_paginate', :source = 'http://gems.github.com'
...to read like
We disabled yamldb output on export because it was causing http
timeouts. I installed the yaml_db plugin in your app and manually ran
rake db:data:dump, so now db/data.yml should be the latest version.
If you have any trouble downloading it, email me privately and I'll
email it to you.
If
Great question David:
On Thu, Mar 12, 2009 at 9:33 AM, David Rogers david.t.rog...@gmail.com wrote:
- gems are at home at rubyforge.
- apps are at home in heroku.
- open collaboration's home is github.
Does establishing and updating git repos at all three make sense?
Yes, absolutely.
The
On Thu, Mar 12, 2009 at 1:08 PM, Kris S forward.f...@gmail.com wrote:
Is it possible to use sprockets with in an app on heroku? It writes
out a js file, and for this reason I am not sure if its permitted or
not.
You'll need to compile the sprockets and commit the file to the
repository for
On Thu, Mar 12, 2009 at 8:42 AM, K2 ke...@coderow.com wrote:
1. What will the eventual cost structure be? I know you don't want
to release exact pricing, but will it be more inline with EngineYard's
Solo or Mor.ph's AppSpace? ~$50-$250 month for most apps. Or more of
the Mor.ph App Cloud
Don't store things on the filesystem - because your app is spread
across the dyno grid, there's no guarantee that something written to
the tmp directory will be there on the next request.
The place for permanent data storage is the database. If you wish to
do a curl-style cookiejar to keep a
On Thu, Mar 5, 2009 at 11:21 PM, DAZ daz4...@gmail.com wrote:
Here is my development.rb file, I can't see any reference to
cache_template_loading, is the line I need to remove here?
Oops, sorry - it's actually config/environments/production.rb, line
13. As someone else pointed out, Heroku
Felix -
We don't support background processes run this way, as it's not
compatible with a cloud architecture. See
http://heroku.com/how/dyno_grid for some background on this.
We're currently working on a feature to support background jobs in a
cloud-friendly way. It would be helpful if you
This is the page that serves the crashlog, but for some reason there
was no log. Definitely would like to find out what happened there,
but it seems like it came back on its own. In any case, a heroku
restart will probably always fix something like this.
Adam
On Sat, Nov 29, 2008 at 3:46 PM, Corey Haines [EMAIL PROTECTED] wrote:
The server for feedmyworms failed to start. Details:
/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:530:in `send':
undefined method `cache_template_loading=' for ActionView::Base:Class
(NoMethodError) from
Good catch. This should be fixed soon; in the meantime, you can
always run migrations manually at the command line, i.e.
$ heroku rake db:migrate
Adam
On Thu, Nov 27, 2008 at 10:45 AM, Matthew Moore [EMAIL PROTECTED] wrote:
When I run through these steps on my new 2.2.2 app I'm deploying,
As promised, the Rails 2.2 is now available for use for all apps on Heroku:
http://blog.heroku.com/archives/2008/11/26/25_rails_2_2_on_heroku/
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To
Although 2.1.0 will work, I highly suggest leaving off the minor version number:
RAILS_GEM_VERSION = '2.1'
This will allow your app to work with whatever minor version is
installed wherever you a running it.
Adam
--~--~-~--~~~---~--~~
You received this message
Is this still happening now?
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to [EMAIL
Fixed.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options,
This is a sweet app Nathan, nice job! We can definitely crank your
bandwidth limits and do some other things to make sure you're fully
available on election day. I'll reply to you off-list about the details.
Adam
--~--~-~--~~~---~--~~
You received this message
I've cleared the overlimit flag, so you're back up.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send
You can run git's garbage collector like so:
git gc
This often reduces a repository size significantly. Another option is to
rebase and remove commits of large binary files that have since been
removed, but are still stored in the history. Run git gc afterward to clean
it out.
There's also
timesonline is fixed.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
Your app went overlimit on bandwidth, although this reset at midnight so
you're already back. I blessed the app which will give you plenty of
headroom so you shouldn't hit this again.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Fixed, there were both the same issue.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to
My guess is that some of your plugins were installed via git clone,
and so contain a .git directory inside them on your local machine.
This will cause git to skip over them when adding to the top-level
repository, and thus they won't be pushed to Heroku.
You can test this theory with a command
I've blessed your app, which will give you plenty of headroom on
bandwidth, and cleared the overlimit flag for the day.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send
Thanks for the heads-up. Better yet, how about sending a pull request
with your patch? - http://github.com/adamwiggins/yaml_db
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this
I highly recommend switching to cookie store sessions, i.e. put
something like this in your environment.rb:
config.action_controller.session = {
:session_key = '_myapp_session',
:secret =
One workaround you could use would be to make a rake task or shell
script which creates a temporary git repo for the purpose of
deploying. Something like this:
cd subproj
git init
git add .
git commit -m 'bundle for heroku deploy'
git remote add heroku [EMAIL PROTECTED]:myapp.git
git push -f
These seem to have corrected themselves, with the exception of
jactwedding - I restarted the Thin and that brought it back.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group,
Fixed.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more
Fixed.
Adam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more
Just fixed one other thing that was affecting some apps (different
issue from the first one).
If you're still having trouble, reply, and please remember to include
the name of your app.
Adam
--~--~-~--~~~---~--~~
You received this message because you are
New client gem / API released today, now in Rubyforge (gem install
heroku to update). New features:
- 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
Thanks Paul, we're glad you like Heroku so much.
I totally agree that the possibilities for broader collaboration are
really exciting - we have tons of ideas for this, some of which are
already in the works. At the moment we're mostly focused on
stabilizing the platform, but we're really
Small apps will always be free, and medium apps will be affordable to
individuals and small companies. So don't worry on that front.
As to running Merb or other frameworks besides Rails, you can't do it
today, but it is something we've considered. Quick straw poll: who
else is interested in
Connecting to external databases is probably not a good idea. It may
or may not work now, but I suspect it will definitely not work in the
future after we make some other architectural changes we have in mind
to facilitate scaling.
I'd recommend rethinking your application architecture to
1 - 100 of 180 matches
Mail list logo
