Re: RMagick Issues
same issue here :/ On Dec 14 2010, 10:44 pm, chadoh wrote: > I am having the same problem. 'twould be great to resolve it. > > On Dec 7, 2:43 am, clubdivot wrote: > > > Hey. > > I am killing myself over here trying to solve an image rending issue. > > I am using simple_captcha to render a captacha image on our > > registration page. The requires RMagick. This is what I have in the > > Gemfile: > > > gem 'rmagick', :require => "RMagick" > > > Specs: > > Rails 3 > > bamboo-ree-1.8.7 > > > I don't get any errors in the server logs, just doesn't render the > > image. Here is the server log for simple_captcha: > > > 2010-12-06T23:36:46-08:00 heroku[router]: GET > > stage.clubdivott.com/simple_captcha/d74065472a73dd54dff31bb73099058327e5a251 > > dyno=web.1 > > queue=0 wait=0ms service=100ms bytes=673 > > 2010-12-06T23:36:46-08:00 heroku[nginx]: GET /simple_captcha/ > > d74065472a73dd54dff31bb73099058327e5a251 HTTP/1.1 | 68.6.52.34 | 703 | > > http | 200 > > > Any ideas? > > Cheers. > > -- 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 more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: simple_captcha on bamboo-ree-1.8.7 with Rails 3 (ImageMagick-/RMagick-related?)
did you ever get this resolved? I'm running into the same problem today (simple_captcha and imageMagick on heroku, ruby 1.8.7) On Dec 15 2010, 8:42 am, chadoh wrote: > I believe this is probably related to ImageMagick or RMagick. Mycaptchaworks > locally, but the image is not generated on heroku. I > don't get an error, just no image. > > From what I've found around the web, people mainly seem to have > RMagick issues with Paperclip, but I've had Paperclip installed and > working on heroku for months now. I didn't even need to include > RMagick in my Gemfile. > > Now in my Gemfile, I have > > gem 'rmagick', "2.12.0", :require => 'RMagick' > > I changed the version due to [this post](http://groups.google.com/ > group/heroku/browse_thread/thread/6a617f9549b45e0f/032f5f89aae07c55), > though the newer one installed just fine for me. -- 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 more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Smaller fonts in production?
I agree that the site based zoom that others have mentioned is
probably at fault.
If not, have you tried to narrow it down with some random
troubleshooting, like:
- Does this happen in any browser, on any system?
- Does the source look identical?
- Have you inspected the affected elements with Firebug and compared
the computed CSS?
That's all I can think of, for now. There should be a clue in there
somewhere.
Good luck,
Tom
On Jan 5, 1:01 am, Carson Cole wrote:
> My fonts appear 25% smaller in production on Heroku vs in development
> locally. Have only one style sheet 'main.css' that I load '<%=
> stylesheet_link_tag 'main' %>' that shows correctly in source code in
> production. What gives?
>
> Here's my stylesheet:
>
> /* DEFAULTS */
> * {
> margin: 0;
> padding: 0;
> border: 0;
>
> }
>
> body {
> background-color: #fff;
> height: 100%;
> width: 100%;
> font: 13px "Lucida Sans", Tahoma, Verdana, sans-serif;}
>
> a {
> margin-left: 7px;
> margin-top: 4px;
> float: left;}
>
> h1 { font-size: 2.5em; }
> h2 { font-size: 1.8em;}
> h3 { font-size: 1.6em; }
> h4 { font-size: 1.5em; }
> h5 { font-size: 1.4em;}
> p { font-size: 1.2em; }
> .clear { clear:both; }
> .right { float: right; }
> .left { float: left; }
> .email {
> margin-top: 5px;}
>
> .header { width: 100%;}
> .facebook_icon { margin-top: -1px;}
> .follow {
> background-color: #5f9e52;
> text-align: center;
> width: 100%;
> margin: 0 auto 0 auto;}
>
> .follow .frame {width: 350px;}
> .follow_text {
> font-size: 1.8em;
> color: #fff;
> float: left;
> margin-top: 3px;
> margin-left:8px;
> margin-right: 20px;}
>
> form {float: left;}
> form input {
> border: thin #fff solid;
> padding: .2em;
> font-size: .8em;}
>
> #footer {
> clear: both;
> text-align: center;
> margin-top: 1em;
> margin-bottom: 1em;
> font-size: .8em;
> color: #5f9ef2;}
>
> .frame {
> width: 650px;
> margin: 0 auto;}
>
> .marketing {
> font-size: 13px;
> background-color: #D0EBCA;}
>
> .marketing .frame {
> padding-top: 1em;
> padding-bottom: 1em;}
>
> .marketing h1 {
> margin-top: 0.5em;
> margin-bottom: .5em;
> font-weight: 500;
> color: #18649b;}
>
> .marketing h2 {
> font-weight: 500;
> margin-top: 1em;
> margin-bottom: .4em;
> color: #18649b;}
>
> .marketing p {
> font-size: 1.1em;
> line-height: 1.5em;}
>
> .logo {
> margin: 1em 0;
> width: 12em;}
>
> .notice {
> float: right;
> text-align: center;
> margin-top: 1em;
> width: 300px;
> color: #fff;}
>
> .notice .regular {
> padding: 10px;
> background-color: #18649b;}
> .notice .error {
> padding: 10px 20px;
> background-color: #f02311;}
> p.special_message {
> width: 300px;
> background-color: #18649b;
> text-align: center;
> color: #fff;
> padding: 10px;
> margin: 1.2em auto 1.3em auto;}
--
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 more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: Smaller fonts in production?
> My fonts appear 25% smaller in production on Heroku vs in development Heroku compresses data for improved performance. :-) -- 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 more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: how to use Heroku in development with view designers?
Keenan, Thanks for your comments: they somewhat repeat suggestions I've received from others. As a newcomer to web app development, I keep hoping there's a way to get collaborators working together but where valuable models don't need to be guaranteed by NDA's. In other words, yes, trusting the ability of my collaborators, but, no, nothing else. The only firm way I can see of doing this is to mock the models, but I wanted to avoid that work in my present case, as I've already built them. WRT Liquid, it would appear that I can simply make available model objects (and maybe some associated 'filters' or functions) that designers then manipulate in the context of their html. I guess in this way development can proceed without direct access to the app structure, and maybe just to blank or otherwise preliminary app pages that designers access only as clients. In any case, it seems from the comments here and Heroku docs that Heroku has no special way of accomplishing what I've been seeking, so, unless anyone sees a silver bullet, I'll consider this matter closed. On Jan 6, 7:04 am, Keenan Brock wrote: > It may be hard for the dev to develop haml/erb without the models to populate > it. > > 1. Have them dev in pure html using a scratch directory in public. Create a > separate git repo that only has your public in it > > You can go have public as a submodule route or you can just have 2 different > projects and do duffs. Since you are going to need to translate back into > haml/erb at some point anyway. > > Second idea is to keep models innocuous and put truely proprietary logic in > external modules. Have them as a gem or plugin and don't include it in your > main repo. > > One thought: > > Many designers I know are quite comfortable with haml/sass or erb/css. Or > atleast they can tweak and improve it if not author it. > > Why work with people you don't trust? > > Why handicap them just to make more work for yourself? > > Rhetorical questions for you only. But I wanted to put out there. > > Keenan > On Jan 5, 2011, at 9:10 AM, Lille wrote: > > > Hi, > > > I developed a Rails app, now hosted on Heroku, and I would like to > > make it available to HTML and javascript contractors for further > > development in sort of a Rails-agnostic way, while keeping private > > certain parts of the app directory structure, viz., my models, which I > > consider proprietary. > > > By 'Rails-agnostic', I hoped someone out there could confirm that > > development can proceed with front-end collaborators on Heroku relying > > solely on the collaborators' knowledge of Git, not the app platform, > > which is Rails. > > > With regard to keeping certain parts of my app structure private, I > > understand this is possible on some source control systems. What about > > in the case of collaborating via Heroku? > > > Thanks, > > > Lille > > > -- > > 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 more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. > > -- 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 more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: how to use Heroku in development with view designers?
How about http://www.liquidmarkup.org/ On Jan 6, 6:04 am, Keenan Brock wrote: > It may be hard for the dev to develop haml/erb without the models to populate > it. > > 1. Have them dev in pure html using a scratch directory in public. Create a > separate git repo that only has your public in it > > You can go have public as a submodule route or you can just have 2 different > projects and do duffs. Since you are going to need to translate back into > haml/erb at some point anyway. > > Second idea is to keep models innocuous and put truely proprietary logic in > external modules. Have them as a gem or plugin and don't include it in your > main repo. > > One thought: > > Many designers I know are quite comfortable with haml/sass or erb/css. Or > atleast they can tweak and improve it if not author it. > > Why work with people you don't trust? > > Why handicap them just to make more work for yourself? > > Rhetorical questions for you only. But I wanted to put out there. > > Keenan > On Jan 5, 2011, at 9:10 AM, Lille wrote: > > > > > Hi, > > > I developed a Rails app, now hosted on Heroku, and I would like to > > make it available to HTML and javascript contractors for further > > development in sort of a Rails-agnostic way, while keeping private > > certain parts of the app directory structure, viz., my models, which I > > consider proprietary. > > > By 'Rails-agnostic', I hoped someone out there could confirm that > > development can proceed with front-end collaborators on Heroku relying > > solely on the collaborators' knowledge of Git, not the app platform, > > which is Rails. > > > With regard to keeping certain parts of my app structure private, I > > understand this is possible on some source control systems. What about > > in the case of collaborating via Heroku? > > > Thanks, > > > Lille > > > -- > > 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 more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. -- 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 more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: how to use Heroku in development with view designers?
It may be hard for the dev to develop haml/erb without the models to populate it. 1. Have them dev in pure html using a scratch directory in public. Create a separate git repo that only has your public in it You can go have public as a submodule route or you can just have 2 different projects and do duffs. Since you are going to need to translate back into haml/erb at some point anyway. Second idea is to keep models innocuous and put truely proprietary logic in external modules. Have them as a gem or plugin and don't include it in your main repo. One thought: Many designers I know are quite comfortable with haml/sass or erb/css. Or atleast they can tweak and improve it if not author it. Why work with people you don't trust? Why handicap them just to make more work for yourself? Rhetorical questions for you only. But I wanted to put out there. Keenan On Jan 5, 2011, at 9:10 AM, Lille wrote: > Hi, > > I developed a Rails app, now hosted on Heroku, and I would like to > make it available to HTML and javascript contractors for further > development in sort of a Rails-agnostic way, while keeping private > certain parts of the app directory structure, viz., my models, which I > consider proprietary. > > By 'Rails-agnostic', I hoped someone out there could confirm that > development can proceed with front-end collaborators on Heroku relying > solely on the collaborators' knowledge of Git, not the app platform, > which is Rails. > > With regard to keeping certain parts of my app structure private, I > understand this is possible on some source control systems. What about > in the case of collaborating via Heroku? > > Thanks, > > Lille > > -- > 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 more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- 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 more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Smaller fonts in production?
Hi Carson
You probably already tried this, but
In your browser, for local dev, could you check your zoom level?
You may have enlarged your font with command plus.
There is a menu option for resetting it to normal view. (exact verbiage escapes
me but should be near increase font size in view or window)
Hope that helps
--Keenan
On Jan 4, 2011, at 7:01 PM, Carson Cole wrote:
> My fonts appear 25% smaller in production on Heroku vs in development
> locally. Have only one style sheet 'main.css' that I load '<%=
> stylesheet_link_tag 'main' %>' that shows correctly in source code in
> production. What gives?
>
> Here's my stylesheet:
>
> /* DEFAULTS */
> * {
>margin: 0;
>padding: 0;
>border: 0;
> }
>
> body {
>background-color: #fff;
>height: 100%;
>width: 100%;
>font: 13px "Lucida Sans", Tahoma, Verdana, sans-serif;
> }
> a {
>margin-left: 7px;
>margin-top: 4px;
>float: left;
> }
> h1 { font-size: 2.5em; }
> h2 { font-size: 1.8em;}
> h3 { font-size: 1.6em; }
> h4 { font-size: 1.5em; }
> h5 { font-size: 1.4em;}
> p { font-size: 1.2em; }
> .clear { clear:both; }
> .right { float: right; }
> .left { float: left; }
> .email {
>margin-top: 5px;
> }
> .header { width: 100%;}
> .facebook_icon { margin-top: -1px;}
> .follow {
>background-color: #5f9e52;
>text-align: center;
>width: 100%;
>margin: 0 auto 0 auto;
> }
> .follow .frame {width: 350px;}
> .follow_text {
>font-size: 1.8em;
>color: #fff;
>float: left;
>margin-top: 3px;
>margin-left:8px;
>margin-right: 20px;
> }
> form {float: left;}
> form input {
>border: thin #fff solid;
>padding: .2em;
>font-size: .8em;
> }
> #footer {
>clear: both;
>text-align: center;
>margin-top: 1em;
>margin-bottom: 1em;
>font-size: .8em;
>color: #5f9ef2;
> }
> .frame {
>width: 650px;
>margin: 0 auto;
> }
> .marketing {
>font-size: 13px;
>background-color: #D0EBCA;
> }
> .marketing .frame {
> padding-top: 1em;
> padding-bottom: 1em;
> }
> .marketing h1 {
>margin-top: 0.5em;
>margin-bottom: .5em;
>font-weight: 500;
>color: #18649b;
> }
> .marketing h2 {
>font-weight: 500;
>margin-top: 1em;
>margin-bottom: .4em;
>color: #18649b;
> }
> .marketing p {
>font-size: 1.1em;
>line-height: 1.5em;
> }
> .logo {
>margin: 1em 0;
>width: 12em;
> }
> .notice {
>float: right;
>text-align: center;
>margin-top: 1em;
>width: 300px;
>color: #fff;
> }
> .notice .regular {
>padding: 10px;
>background-color: #18649b;}
> .notice .error {
>padding: 10px 20px;
>background-color: #f02311;}
> p.special_message {
>width: 300px;
>background-color: #18649b;
>text-align: center;
>color: #fff;
>padding: 10px;
>margin: 1.2em auto 1.3em auto;}
>
> --
> 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 more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
>
--
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 more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: Smaller fonts in production?
Hi Carson,
I submitted this *exact* same question about a month ago after banging
my head against a brick wall for a few hours.
Press Cmd+0 (Mac) or Ctrl+0 (Win) to reset the zoom on your browser.
I have to admit, I was a little embarrassed at the time. But now I'm
glad I'm not the only one (presuming this works for you!)
Chris
On Jan 5, 12:01 am, Carson Cole wrote:
> My fonts appear 25% smaller in production on Heroku vs in development
> locally. Have only one style sheet 'main.css' that I load '<%=
> stylesheet_link_tag 'main' %>' that shows correctly in source code in
> production. What gives?
>
> Here's my stylesheet:
>
> /* DEFAULTS */
> * {
> margin: 0;
> padding: 0;
> border: 0;
>
> }
>
> body {
> background-color: #fff;
> height: 100%;
> width: 100%;
> font: 13px "Lucida Sans", Tahoma, Verdana, sans-serif;}
>
> a {
> margin-left: 7px;
> margin-top: 4px;
> float: left;}
>
> h1 { font-size: 2.5em; }
> h2 { font-size: 1.8em;}
> h3 { font-size: 1.6em; }
> h4 { font-size: 1.5em; }
> h5 { font-size: 1.4em;}
> p { font-size: 1.2em; }
> .clear { clear:both; }
> .right { float: right; }
> .left { float: left; }
> .email {
> margin-top: 5px;}
>
> .header { width: 100%;}
> .facebook_icon { margin-top: -1px;}
> .follow {
> background-color: #5f9e52;
> text-align: center;
> width: 100%;
> margin: 0 auto 0 auto;}
>
> .follow .frame {width: 350px;}
> .follow_text {
> font-size: 1.8em;
> color: #fff;
> float: left;
> margin-top: 3px;
> margin-left:8px;
> margin-right: 20px;}
>
> form {float: left;}
> form input {
> border: thin #fff solid;
> padding: .2em;
> font-size: .8em;}
>
> #footer {
> clear: both;
> text-align: center;
> margin-top: 1em;
> margin-bottom: 1em;
> font-size: .8em;
> color: #5f9ef2;}
>
> .frame {
> width: 650px;
> margin: 0 auto;}
>
> .marketing {
> font-size: 13px;
> background-color: #D0EBCA;}
>
> .marketing .frame {
> padding-top: 1em;
> padding-bottom: 1em;}
>
> .marketing h1 {
> margin-top: 0.5em;
> margin-bottom: .5em;
> font-weight: 500;
> color: #18649b;}
>
> .marketing h2 {
> font-weight: 500;
> margin-top: 1em;
> margin-bottom: .4em;
> color: #18649b;}
>
> .marketing p {
> font-size: 1.1em;
> line-height: 1.5em;}
>
> .logo {
> margin: 1em 0;
> width: 12em;}
>
> .notice {
> float: right;
> text-align: center;
> margin-top: 1em;
> width: 300px;
> color: #fff;}
>
> .notice .regular {
> padding: 10px;
> background-color: #18649b;}
> .notice .error {
> padding: 10px 20px;
> background-color: #f02311;}
> p.special_message {
> width: 300px;
> background-color: #18649b;
> text-align: center;
> color: #fff;
> padding: 10px;
> margin: 1.2em auto 1.3em auto;}
--
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 more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
