Had some of those earlier, they went away.
Now I get a fail whale when I try to pull my data off heroku though...
and I can't create a new app on it...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
From
http://docs.heroku.com/constraints#git-submodules
Git submodules are not currently supported. We’re evaluating whether
or not to support these; in the meantime you’ll need to include any
submodules into the main project. You can do so like this:
$ cd myapp
$ rm -rf `find . -mindepth 2
Today I pull my git in heroku,
the server show the following error message.
And my app is always going wrong.
my app is http://moneylog.heroku.com
Anyone can help me.
Error Message:
C:/git pull
Internal server error
/usr/local/lib/ruby/gems/1.8/gems/rest-client-0.9.2/lib/restclient/
Just so everyone is clear, those instructions do not show how to use
submodules on heroku. They show how to eliminate submodule dependencies from
your project.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku
Wow, I am just bumping into all of the constraints these days...
Is there any way to get around the read-only filesystem? My app
dynamically loads assets at runtime to public. Is there anyway we can
put them in tmp and link to it? Or create a special area in public
that is like tmp?
May I suggest that you set up a Twitter account or a blog or something
for reporting service disturbances such as the one today that was
reported by multiple users?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
It's interesting that for a service with thousands of deployed apps,
how _little_ fuss there is when it goes down! Wierd really!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group,
Instead of writing them to disk, write them to the cache with a long
expiry. Each time you deploy the app, the cache is cleared.
For me, the easiest way was lazy caching. Have a controller that
responds to the request the first time (passing the asset through and
sending the right cache
I think I'd just set up Google apps to handle email for my domain, and
use one the available POP3 or IMAP libs to check whatever account I
want my Ruby app to process.
/Morten
On May 7, 2009, at 1:37 AM, Thomas Balthazar wrote:
Hello,
I've seen a lot of posts about handling outgoing
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
On Fri, May 8, 2009 at 6:36 PM, Adam Wiggins a...@heroku.com wrote:
Another fix for this is to alias your domain to point to
proxy.heroku.com instead of heroku.com. i.e.:
Although it reads a little less nicely, this avoids having to tinker
with MX records, so perhaps we'll make this the
12 matches
Mail list logo
