From uzleepito at gmail.com  Sat Nov  5 08:22:48 2011
From: uzleepito at gmail.com (Nokan Emiro)
Date: Sat, 5 Nov 2011 13:22:48 +0100
Subject: Markaby + HTML5
Message-ID: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>

Hi,

this is not really a Camping question, but a Markaby one, so
please don't be angry, please!  :)

How can I use HTML5 tags (for example <footer>) and HTML5
compliant attributes (for example data-content="xxx") in Markaby?
It throws an error when I try this.  I've workarounded it with
text "<footer>"   and  text "<div data-content=\"xxx\">"  but this
isn't the nicest solution.  How would you do these?

u.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111105/93bf8883/attachment.html>

From deveritt at innotts.co.uk  Sat Nov  5 08:55:48 2011
From: deveritt at innotts.co.uk (Dave Everitt)
Date: Sat, 5 Nov 2011 12:55:48 +0000
Subject: Markaby + HTML5
In-Reply-To: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
References: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
Message-ID: <59B595BA-5576-4ECB-9BC4-DFA30021C4CF@innotts.co.uk>

Hi Nokan

for current efforts in this direction, see here:
https://github.com/markaby/markaby/issues/18
and here:
https://github.com/markaby/markaby/pull/26

and note:
https://github.com/igravious/markaby/commit/8be76d138228a32500f96140afca79bf95751e40

Or even:
https://github.com/zimbatm/miniby
but note "Miniby is just a small experiment I did over my trip to  
london. Some ideas I wanted to try-out while implementing a Markaby  
clone. Don?t expect no support of future development :-)"

DaveE

> this is not really a Camping question, but a Markaby one, so
> please don't be angry, please!  :)
>
> How can I use HTML5 tags (for example <footer>) and HTML5
> compliant attributes (for example data-content="xxx") in Markaby?
> It throws an error when I try this.  I've workarounded it with
> text "<footer>"   and  text "<div data-content=\"xxx\">"  but this
> isn't the nicest solution.  How would you do these?


From a at creativepony.com  Sat Nov  5 09:14:38 2011
From: a at creativepony.com (Jenna Fox)
Date: Sun, 6 Nov 2011 00:14:38 +1100
Subject: Markaby + HTML5
In-Reply-To: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
References: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
Message-ID: <41B78AA5-57D5-4A52-917A-FA36A69008B7@creativepony.com>

If you add the line '@auto_validation = false' to the beginning of your layout, markaby aught to stop minding if you use things unspecified in xhtml. I'm not too sure if that will let you use unknown tags, or just unknown attributes.

If you have any trouble getting unknown tags to work, try using the tag! method:

tag! 'footer', arg, arg, arg?

effectively is a more explicit and direct version of:

footer arg, arg, arg?

Hope that helps! Hopefully we'll have a html5-friendly markaby soon. :)

?
Jenna


On 05/11/2011, at 11:22 PM, Nokan Emiro wrote:

> Hi,
> 
> this is not really a Camping question, but a Markaby one, so
> please don't be angry, please!  :)
> 
> How can I use HTML5 tags (for example <footer>) and HTML5
> compliant attributes (for example data-content="xxx") in Markaby?
> It throws an error when I try this.  I've workarounded it with
> text "<footer>"   and  text "<div data-content=\"xxx\">"  but this
> isn't the nicest solution.  How would you do these?
> 
> u.
> 
> 
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list


From matma.rex at gmail.com  Sat Nov  5 12:30:04 2011
From: matma.rex at gmail.com (=?UTF-8?Q?Bartosz_Dziewo=C5=84ski?=)
Date: Sat, 5 Nov 2011 17:30:04 +0100
Subject: Markaby + HTML5
In-Reply-To: <41B78AA5-57D5-4A52-917A-FA36A69008B7@creativepony.com>
References: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
	<41B78AA5-57D5-4A52-917A-FA36A69008B7@creativepony.com>
Message-ID: <CAA-yUx1dDdgxzvwDQ_oNNa=RMJZzvUBQ_JY6wKyjyVqm2cyCyQ@mail.gmail.com>

2011/11/5, Jenna Fox <a at creativepony.com>:
> If you add the line '@auto_validation = false' to the beginning of your
> layout, markaby aught to stop minding if you use things unspecified in
> xhtml. I'm not too sure if that will let you use unknown tags, or just
> unknown attributes.
>
> If you have any trouble getting unknown tags to work, try using the tag!
> method:
>
> tag! 'footer', arg, arg, arg?
>
> effectively is a more explicit and direct version of:
>
> footer arg, arg, arg?
>
> Hope that helps! Hopefully we'll have a html5-friendly markaby soon. :)
>
> ?
> Jenna
>
>
> On 05/11/2011, at 11:22 PM, Nokan Emiro wrote:
>
>> Hi,
>>
>> this is not really a Camping question, but a Markaby one, so
>> please don't be angry, please!  :)
>>
>> How can I use HTML5 tags (for example <footer>) and HTML5
>> compliant attributes (for example data-content="xxx") in Markaby?
>> It throws an error when I try this.  I've workarounded it with
>> text "<footer>"   and  text "<div data-content=\"xxx\">"  but this
>> isn't the nicest solution.  How would you do these?
>>
>> u.
>>
>>
>> _______________________________________________
>> Camping-list mailing list
>> Camping-list at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/camping-list
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>


-- 
-- Matma Rex

From gravious at jollyrotten.org  Wed Nov  9 01:40:01 2011
From: gravious at jollyrotten.org (Anthony Durity)
Date: Wed, 9 Nov 2011 08:40:01 +0200
Subject: Markaby + HTML5
In-Reply-To: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
References: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
Message-ID: <CAOxF-FYdxD0r5Cv7_1g8Gkuyhsd0Czy-if4ELPLsh_6jJenXmw@mail.gmail.com>

Hi there,

I have a Markaby fork that does HTML5

https://github.com/igravious/markaby

Use it like this:

html_five do

.
.
.

end

It recognizes header and footer and all the rest and sets the right
incantations in DOCTYPE and the html and head tags. Patches welcome for
bits I have missed out on. I've even removed tags that are deprecated, and
added attributes that have been added. I've included URLs to a diff file
between the HTML4 and 5 spec so it should be easy to build on what I have
done. Hop you find it useful and hope it does what you need.

Regards,
    Anthony

On Sat, Nov 5, 2011 at 2:22 PM, Nokan Emiro <uzleepito at gmail.com> wrote:

> Hi,
>
> this is not really a Camping question, but a Markaby one, so
> please don't be angry, please!  :)
>
> How can I use HTML5 tags (for example <footer>) and HTML5
> compliant attributes (for example data-content="xxx") in Markaby?
> It throws an error when I try this.  I've workarounded it with
> text "<footer>"   and  text "<div data-content=\"xxx\">"  but this
> isn't the nicest solution.  How would you do these?
>
> u.
>
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111109/934fad79/attachment.html>

From deveritt at innotts.co.uk  Sat Nov 12 05:36:04 2011
From: deveritt at innotts.co.uk (Dave Everitt)
Date: Sat, 12 Nov 2011 10:36:04 +0000
Subject: Markaby + HTML5
In-Reply-To: <CAOxF-FYdxD0r5Cv7_1g8Gkuyhsd0Czy-if4ELPLsh_6jJenXmw@mail.gmail.com>
References: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
	<CAOxF-FYdxD0r5Cv7_1g8Gkuyhsd0Czy-if4ELPLsh_6jJenXmw@mail.gmail.com>
Message-ID: <CFA1B517-E1D1-4F6A-B0FD-81B815A1A7BF@innotts.co.uk>

Anthony - that's great. I think I mentioned your fork in an earlier  
response - have those changes been been pulled into https://github.com/markaby/markaby/ 
  or - if not - are they likely to be? - Dave

> Hi there,
>
> I have a Markaby fork that does HTML5
>
> https://github.com/igravious/markaby
>
> Use it like this:
>
> html_five do
>
> .
> .
> .
>
> end
>
> It recognizes header and footer and all the rest and sets the right  
> incantations in DOCTYPE and the html and head tags. Patches welcome  
> for bits I have missed out on. I've even removed tags that are  
> deprecated, and added attributes that have been added. I've included  
> URLs to a diff file between the HTML4 and 5 spec so it should be  
> easy to build on what I have done. Hop you find it useful and hope  
> it does what you need.
>
> Regards,
> Anthony
>
> On Sat, Nov 5, 2011 at 2:22 PM, Nokan Emiro <uzleepito at gmail.com>  
> wrote:
> Hi,
>
> this is not really a Camping question, but a Markaby one, so please  
> don't be angry, please!  :)
>
> How can I use HTML5 tags (for example <footer>) and HTML5 compliant  
> attributes (for example data-content="xxx") in Markaby?
> It throws an error when I try this.  I've workarounded it with text  
> "<footer>"   and  text "<div data-content=\"xxx\">"  but this isn't  
> the nicest solution.  How would you do these?
>
> u.
>
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111112/12a9dd2b/attachment-0001.html>

From thisredoned at gmail.com  Sun Nov 13 11:05:44 2011
From: thisredoned at gmail.com (Piotr S)
Date: Sun, 13 Nov 2011 17:05:44 +0100
Subject: Camping goes heroku. Hopefully.
Message-ID: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>

I've been struggling with deployment of a camping app on heroku for two
days now and I just can't get it to work. I also tried cloning someone
elses github repo (Camping-base) that supposedly worked on heroku but it
didn't work for me.
Is there a magical way of going about it? Let's assume I have a single file
app with some basic setup and a sqlite database that on heroku would
obviously have to change to postgres.
Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111113/9a31f0ed/attachment.html>

From matma.rex at gmail.com  Sun Nov 13 12:15:41 2011
From: matma.rex at gmail.com (=?UTF-8?Q?Bartosz_Dziewo=C5=84ski?=)
Date: Sun, 13 Nov 2011 18:15:41 +0100
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
Message-ID: <CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>

You just need a .gems file (containing list of gems you use, one per
line) and a config.ru file like this:

require './my_app.rb'
run MyApp

(both in the root of the repo).

Create them both, commit and it should start working. (You'll
obviously also have to do some magic to switch to postgres, as you
noticed.)

-- Matma Rex

From thisredoned at gmail.com  Sun Nov 13 12:27:06 2011
From: thisredoned at gmail.com (Piotr S)
Date: Sun, 13 Nov 2011 18:27:06 +0100
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
Message-ID: <CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>

Well yeah. I know about the gems and configu.ru.
It's the magic part of switching between databases that really gives me the
mental workout.
I'm looking for some working solutions to a problem that I'd imagine most
of the Camping hackers face because where else could we possibly deploy our
apps if not on heroku?

You just need a .gems file (containing list of gems you use, one per
> line) and a config.ru file like this:
>
> require './my_app.rb'
> run MyApp
>
> (both in the root of the repo).
>
> Create them both, commit and it should start working. (You'll
> obviously also have to do some magic to switch to postgres, as you
> noticed.)
>
>  -- Matma Rex
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111113/94ec2ca2/attachment.html>

From ruby at monnet-usa.com  Sun Nov 13 13:20:46 2011
From: ruby at monnet-usa.com (Philippe Monnet)
Date: Sun, 13 Nov 2011 11:20:46 -0700
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
	<CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
Message-ID: <4EC00A7E.5020008@monnet-usa.com>

Here is my recipe:

1. Setup up up your Gems prerequisites: create a .gems file in the root 
folder and list each gem version on a separate line. E.g.:

     rack --version '>= 1.2.1'
     markaby --version '= 0.5'
     camping --version '>= 2.1'

2. Create a RackUp script:  create a config.ru file (still in the root 
folder) for Rack's configuration. In this example myapp.rb has a main 
module named MyApp:

     # config.ru

     %w(rack activerecord camping camping/session camping/reloader 
).each { | r | require r}
     require 'myapp.rb'
     run MyApp

3. Configure routes for your static assets: if you need to serve static 
files from specific directories, add the following statements to config.ru:

     use Rack::Reloader
     use Rack::Static,
     :urls => [ '/css',
                    '/js',
                    '/images' ],
     :root => File.expand_path(File.dirname(__FILE__))

Note: If you need additional Rack modules insert the corresponding 
statements there too.

4. Setup your application configuration: I'd recommend that the various 
configuration files you need get grouped together into a ./config 
folder. Example:

     ./config
         database.yml
         some.yml
         ...

Important: Do not add the database.yml file to Git so that it does NOT 
get pushed to Heroku. When you first deploy to Heroku, the database.yml 
file will automatically be generated to reflect the internal name that 
Heroku will assign. So your main module should connect to the database 
like so:

     dbconfig = YAML.load(File.read('config/database.yml'))
     environment = ENV['DATABASE_URL'] ? 'production' : 'development'
     Camping::Models::Base.establish_connection  dbconfig[environment]

This allows you to use your local (git-unaware) database.yml when 
developing and the official Heroku version when hosted.

5. Tweak your code for PostgreSQL when migrating your SQLite database to 
PostgreSQL: take into account a stricter GROUP BY clause. PostgreSQL 
requires all resulting columns from a SELECT ... GROUP BY to be 
explicitly defined.
In other words if you have the following SQLite query:
     SELECT *
     FROM widgets
     GROUP BY category
You will need to rewrite like so:
     SELECT id, category, description
     FROM widgets
     GROUP BY category, category, description

Hope that helps.

Philippe

On 11/13/2011 10:27 AM, Piotr S wrote:
> Well yeah. I know about the gems and configu.ru <http://configu.ru>.
> It's the magic part of switching between databases that really gives 
> me the mental workout.
> I'm looking for some working solutions to a problem that I'd imagine 
> most of the Camping hackers face because where else could we possibly 
> deploy our apps if not on heroku?
>
>     You just need a .gems file (containing list of gems you use, one per
>     line) and a config.ru <http://config.ru> file like this:
>
>     require './my_app.rb'
>     run MyApp
>
>     (both in the root of the repo).
>
>     Create them both, commit and it should start working. (You'll
>     obviously also have to do some magic to switch to postgres, as you
>     noticed.)
>
>      -- Matma Rex
>
>
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111113/50cd07ce/attachment.html>

From edheil at fastmail.fm  Sun Nov 13 13:33:06 2011
From: edheil at fastmail.fm (Ed Heil)
Date: Sun, 13 Nov 2011 13:33:06 -0500
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <4EC00A7E.5020008@monnet-usa.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
	<CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
	<4EC00A7E.5020008@monnet-usa.com>
Message-ID: <4EC00D62.2070603@fastmail.fm>

THANK YOU.  I got a Camping app working on Heroku last year, and it was 
great, but when I tried it again a few weeks ago with a new app, the way 
I'd done it didn't work anymore and I never did figure it out.  I'm very 
grateful for some working instructions. :)


On 11/13/11 1:20 PM, Philippe Monnet wrote:
> Here is my recipe:
>
> 1. Setup up up your Gems prerequisites: create a .gems file in the 
> root folder and list each gem version on a separate line. E.g.:
>
>     rack --version '>= 1.2.1'
>     markaby --version '= 0.5'
>     camping --version '>= 2.1'
>
> 2. Create a RackUp script:  create a config.ru file (still in the root 
> folder) for Rack's configuration. In this example myapp.rb has a main 
> module named MyApp:
>
>     # config.ru
>
>     %w(rack activerecord camping camping/session camping/reloader 
> ).each { | r | require r}
>     require 'myapp.rb'
>     run MyApp
>
> 3. Configure routes for your static assets: if you need to serve 
> static files from specific directories, add the following statements 
> to config.ru:
>
>     use Rack::Reloader
>     use Rack::Static,
>     :urls => [ '/css',
>                    '/js',
>                    '/images' ],
>     :root => File.expand_path(File.dirname(__FILE__))
>
> Note: If you need additional Rack modules insert the corresponding 
> statements there too.
>
> 4. Setup your application configuration: I'd recommend that the 
> various configuration files you need get grouped together into a 
> ./config folder. Example:
>
>     ./config
>         database.yml
>         some.yml
>         ...
>
> Important: Do not add the database.yml file to Git so that it does NOT 
> get pushed to Heroku. When you first deploy to Heroku, the 
> database.yml file will automatically be generated to reflect the 
> internal name that Heroku will assign. So your main module should 
> connect to the database like so:
>
>     dbconfig = YAML.load(File.read('config/database.yml'))
>     environment = ENV['DATABASE_URL'] ? 'production' : 'development'
>     Camping::Models::Base.establish_connection  dbconfig[environment]
>
> This allows you to use your local (git-unaware) database.yml when 
> developing and the official Heroku version when hosted.
>
> 5. Tweak your code for PostgreSQL when migrating your SQLite database 
> to PostgreSQL: take into account a stricter GROUP BY clause. 
> PostgreSQL requires all resulting columns from a SELECT ... GROUP BY 
> to be explicitly defined.
> In other words if you have the following SQLite query:
>     SELECT *
>     FROM widgets
>     GROUP BY category
> You will need to rewrite like so:
>     SELECT id, category, description
>     FROM widgets
>     GROUP BY category, category, description
>
> Hope that helps.
>
> Philippe
>
> On 11/13/2011 10:27 AM, Piotr S wrote:
>> Well yeah. I know about the gems and configu.ru <http://configu.ru>.
>> It's the magic part of switching between databases that really gives 
>> me the mental workout.
>> I'm looking for some working solutions to a problem that I'd imagine 
>> most of the Camping hackers face because where else could we possibly 
>> deploy our apps if not on heroku?
>>
>>     You just need a .gems file (containing list of gems you use, one per
>>     line) and a config.ru <http://config.ru> file like this:
>>
>>     require './my_app.rb'
>>     run MyApp
>>
>>     (both in the root of the repo).
>>
>>     Create them both, commit and it should start working. (You'll
>>     obviously also have to do some magic to switch to postgres, as you
>>     noticed.)
>>
>>      -- Matma Rex
>>
>>
>>
>>
>> _______________________________________________
>> Camping-list mailing list
>> Camping-list at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/camping-list
>
>
>
> This body part will be downloaded on demand.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111113/66cf64d8/attachment-0001.html>

From judofyr at gmail.com  Sun Nov 13 12:48:44 2011
From: judofyr at gmail.com (Magnus Holm)
Date: Sun, 13 Nov 2011 18:48:44 +0100
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
	<CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
Message-ID: <CAJ367femFgvWwEOwJXF6R2_zcP0SSueh5CPYVwoWB3ycW6LNgQ@mail.gmail.com>

On Sun, Nov 13, 2011 at 18:27, Piotr S <thisredoned at gmail.com> wrote:
> Well yeah. I know about the gems and configu.ru.
> It's the magic part of switching between databases that really gives me the
> mental workout.

See http://devcenter.heroku.com/articles/rack#database_access for how
to connect ActiveRecord to the database.

Just remember that the free version of Heroku doesn't include database support.

From thisredoned at gmail.com  Sun Nov 13 15:46:58 2011
From: thisredoned at gmail.com (Piotr S)
Date: Sun, 13 Nov 2011 21:46:58 +0100
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <4EC00A7E.5020008@monnet-usa.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
	<CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
	<4EC00A7E.5020008@monnet-usa.com>
Message-ID: <CAFUc-cRoHPqOF05bt6dWTXvK4DRa_sUgN296hwwL1xKi4i8F1g@mail.gmail.com>

Thanks for your answer. I still can't get it to work. I had to change
activerecord to active_record in config.ru so it doesn't give me 'no such
file to load' error.
Still there is a error that I also had before from postgresql_adapter.rb
saying:
PGError: ERROR: invalid value for parameter "client_min_messages" : ""
(ActiveRecord::StatementInvalid)

2011/11/13 Philippe Monnet <ruby at monnet-usa.com>

>  Here is my recipe:
>
> 1. Setup up up your Gems prerequisites: create a .gems file in the root
> folder and list each gem version on a separate line. E.g.:
>
>     rack --version '>= 1.2.1'
>     markaby --version '= 0.5'
>     camping --version '>= 2.1'
>
> 2. Create a RackUp script:  create a config.ru file (still in the root
> folder) for Rack's configuration. In this example myapp.rb has a main
> module named MyApp:
>
>     # config.ru
>
>     %w(rack activerecord camping camping/session camping/reloader ).each {
> | r | require r}
>     require 'myapp.rb'
>     run MyApp
>
> 3. Configure routes for your static assets: if you need to serve static
> files from specific directories, add the following statements to config.ru
> :
>
>     use Rack::Reloader
>     use Rack::Static,
>     :urls => [ '/css',
>                    '/js',
>                    '/images' ],
>     :root => File.expand_path(File.dirname(__FILE__))
>
> Note: If you need additional Rack modules insert the corresponding
> statements there too.
>
> 4. Setup your application configuration: I'd recommend that the various
> configuration files you need get grouped together into a ./config folder.
> Example:
>
>     ./config
>         database.yml
>         some.yml
>         ...
>
> Important: Do not add the database.yml file to Git so that it does NOT get
> pushed to Heroku. When you first deploy to Heroku, the database.yml file
> will automatically be generated to reflect the internal name that Heroku
> will assign. So your main module should connect to the database like so:
>
>     dbconfig = YAML.load(File.read('config/database.yml'))
>     environment = ENV['DATABASE_URL'] ? 'production' : 'development'
>     Camping::Models::Base.establish_connection  dbconfig[environment]
>
> This allows you to use your local (git-unaware) database.yml when
> developing and the official Heroku version when hosted.
>
> 5. Tweak your code for PostgreSQL when migrating your SQLite database to
> PostgreSQL: take into account a stricter GROUP BY clause. PostgreSQL
> requires all resulting columns from a SELECT ... GROUP BY to be explicitly
> defined.
> In other words if you have the following SQLite query:
>     SELECT *
>     FROM widgets
>     GROUP BY category
> You will need to rewrite like so:
>     SELECT id, category, description
>     FROM widgets
>     GROUP BY category, category, description
>
> Hope that helps.
>
>   Philippe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111113/dd1e9d32/attachment.html>

From steve at steveklabnik.com  Mon Nov 14 13:44:51 2011
From: steve at steveklabnik.com (Steve Klabnik)
Date: Mon, 14 Nov 2011 13:44:51 -0500
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <CAJ367femFgvWwEOwJXF6R2_zcP0SSueh5CPYVwoWB3ycW6LNgQ@mail.gmail.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
	<CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
	<CAJ367femFgvWwEOwJXF6R2_zcP0SSueh5CPYVwoWB3ycW6LNgQ@mail.gmail.com>
Message-ID: <CABL+ZB6=6DCQH8PO+ETKJU++RnhH5Z2RitfmVWoH8oh3z9TQCw@mail.gmail.com>

> Just remember that the free version of Heroku doesn't include database support.

Whaaa? Since when? http://www.heroku.com/pricing#0-0 says you get 5MB for $0.

Also, I'm pretty sure .gems is deprecated, and you have to use Bundler soon.

From judofyr at gmail.com  Mon Nov 14 14:04:32 2011
From: judofyr at gmail.com (Magnus Holm)
Date: Mon, 14 Nov 2011 20:04:32 +0100
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <CABL+ZB6=6DCQH8PO+ETKJU++RnhH5Z2RitfmVWoH8oh3z9TQCw@mail.gmail.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
	<CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
	<CAJ367femFgvWwEOwJXF6R2_zcP0SSueh5CPYVwoWB3ycW6LNgQ@mail.gmail.com>
	<CABL+ZB6=6DCQH8PO+ETKJU++RnhH5Z2RitfmVWoH8oh3z9TQCw@mail.gmail.com>
Message-ID: <CAJ367ffLj7QCHRJKTU=px5mpO_+vbJ8kwfdUHWvWJ8YF=tkX6w@mail.gmail.com>

On Mon, Nov 14, 2011 at 19:44, Steve Klabnik <steve at steveklabnik.com> wrote:
>> Just remember that the free version of Heroku doesn't include database support.
>
> Whaaa? Since when? http://www.heroku.com/pricing#0-0 says you get 5MB for $0.

Hm? Really? It seems I got the wrong impression after their price change?

Oh well, there's still that ugly client_min_messages-bug which I
haven't been able to solve :/

From gravious at jollyrotten.org  Fri Nov 18 08:09:00 2011
From: gravious at jollyrotten.org (Anthony Durity)
Date: Fri, 18 Nov 2011 13:09:00 +0000
Subject: Markaby + HTML5
In-Reply-To: <CFA1B517-E1D1-4F6A-B0FD-81B815A1A7BF@innotts.co.uk>
References: <CABmj=E78OJ+Fne2YkyZ5ZzGFJKyvZ3fuTgdqGnSY8ZXOtNVhuA@mail.gmail.com>
	<CAOxF-FYdxD0r5Cv7_1g8Gkuyhsd0Czy-if4ELPLsh_6jJenXmw@mail.gmail.com>
	<CFA1B517-E1D1-4F6A-B0FD-81B815A1A7BF@innotts.co.uk>
Message-ID: <CAOxF-FbwPs=avP2CGxfiq5jYYCT6O_Z+75PjpNWh4-eQhXSSqw@mail.gmail.com>

No, I guess not. The changes need tests and some more love. They work for
me.

On Sat, Nov 12, 2011 at 10:36 AM, Dave Everitt <deveritt at innotts.co.uk>wrote:

> Anthony - that's great. I think I mentioned your fork in an earlier
> response - have those changes been been pulled into
> https://github.com/markaby/markaby/<https://github.com/markaby/markaby/issues/18>or - if not - are they likely to be? - Dave
>
> Hi there,
>
> I have a Markaby fork that does HTML5
>
> https://github.com/igravious/markaby
>
> Use it like this:
>
> html_five do
>
> .
> .
> .
>
> end
>
> It recognizes header and footer and all the rest and sets the right
> incantations in DOCTYPE and the html and head tags. Patches welcome for
> bits I have missed out on. I've even removed tags that are deprecated, and
> added attributes that have been added. I've included URLs to a diff file
> between the HTML4 and 5 spec so it should be easy to build on what I have
> done. Hop you find it useful and hope it does what you need.
>
> Regards,
> Anthony
>
> On Sat, Nov 5, 2011 at 2:22 PM, Nokan Emiro <uzleepito at gmail.com> wrote:
>
>> Hi,
>>
>> this is not really a Camping question, but a Markaby one, so please don't
>> be angry, please!  :)
>>
>> How can I use HTML5 tags (for example <footer>) and HTML5 compliant
>> attributes (for example data-content="xxx") in Markaby?
>> It throws an error when I try this.  I've workarounded it with text
>> "<footer>"   and  text "<div data-content=\"xxx\">"  but this isn't the
>> nicest solution.  How would you do these?
>>
>> u.
>>
>> Camping-list mailing list
>> Camping-list at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/camping-list
>>
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111118/51b5e737/attachment.html>

From gravious at jollyrotten.org  Fri Nov 18 08:20:12 2011
From: gravious at jollyrotten.org (Anthony Durity)
Date: Fri, 18 Nov 2011 13:20:12 +0000
Subject: Camping goes heroku. Hopefully.
In-Reply-To: <4EC00A7E.5020008@monnet-usa.com>
References: <CAFUc-cRzAdSMWKT5K=6OAv7=ZuJFe+ZW+aEwhs=qbDh7TQs7BQ@mail.gmail.com>
	<CAA-yUx15DiTDvKKHTWHngAtM0JLMCgApZSs-X2qAOYbgGTSqPQ@mail.gmail.com>
	<CAFUc-cT7sh7FFvBpWORthxGYj0B__T+iSoS3vwMk8b4zhpKUTg@mail.gmail.com>
	<4EC00A7E.5020008@monnet-usa.com>
Message-ID: <CAOxF-FZjt4=qJoM+z4KqxCsDUeCvsbtGB+2TGyqtUGPT8+M3eQ@mail.gmail.com>

Thanks for the great instructions Phillippe. Are you French? Or perhaps
Canadian?

On Sun, Nov 13, 2011 at 6:20 PM, Philippe Monnet <ruby at monnet-usa.com>wrote:

>  Here is my recipe:
>
> 1. Setup up up your Gems prerequisites: create a .gems file in the root
> folder and list each gem version on a separate line. E.g.:
>
>     rack --version '>= 1.2.1'
>     markaby --version '= 0.5'
>     camping --version '>= 2.1'
>
> 2. Create a RackUp script:  create a config.ru file (still in the root
> folder) for Rack's configuration. In this example myapp.rb has a main
> module named MyApp:
>
>     # config.ru
>
>     %w(rack activerecord camping camping/session camping/reloader ).each {
> | r | require r}
>     require 'myapp.rb'
>     run MyApp
>
> 3. Configure routes for your static assets: if you need to serve static
> files from specific directories, add the following statements to config.ru
> :
>
>     use Rack::Reloader
>     use Rack::Static,
>     :urls => [ '/css',
>                    '/js',
>                    '/images' ],
>     :root => File.expand_path(File.dirname(__FILE__))
>
> Note: If you need additional Rack modules insert the corresponding
> statements there too.
>
> 4. Setup your application configuration: I'd recommend that the various
> configuration files you need get grouped together into a ./config folder.
> Example:
>
>     ./config
>         database.yml
>         some.yml
>         ...
>
> Important: Do not add the database.yml file to Git so that it does NOT get
> pushed to Heroku. When you first deploy to Heroku, the database.yml file
> will automatically be generated to reflect the internal name that Heroku
> will assign. So your main module should connect to the database like so:
>
>     dbconfig = YAML.load(File.read('config/database.yml'))
>     environment = ENV['DATABASE_URL'] ? 'production' : 'development'
>     Camping::Models::Base.establish_connection  dbconfig[environment]
>
> This allows you to use your local (git-unaware) database.yml when
> developing and the official Heroku version when hosted.
>
> 5. Tweak your code for PostgreSQL when migrating your SQLite database to
> PostgreSQL: take into account a stricter GROUP BY clause. PostgreSQL
> requires all resulting columns from a SELECT ... GROUP BY to be explicitly
> defined.
> In other words if you have the following SQLite query:
>     SELECT *
>     FROM widgets
>     GROUP BY category
> You will need to rewrite like so:
>     SELECT id, category, description
>     FROM widgets
>     GROUP BY category, category, description
>
> Hope that helps.
>
> Philippe
>
>
> On 11/13/2011 10:27 AM, Piotr S wrote:
>
> Well yeah. I know about the gems and configu.ru.
>  It's the magic part of switching between databases that really gives me
> the mental workout.
> I'm looking for some working solutions to a problem that I'd imagine most
> of the Camping hackers face because where else could we possibly deploy our
> apps if not on heroku?
>
>  You just need a .gems file (containing list of gems you use, one per
>> line) and a config.ru file like this:
>>
>> require './my_app.rb'
>> run MyApp
>>
>> (both in the root of the repo).
>>
>> Create them both, commit and it should start working. (You'll
>> obviously also have to do some magic to switch to postgres, as you
>> noticed.)
>>
>>  -- Matma Rex
>>
>
>
>
> _______________________________________________
> Camping-list mailing listCamping-list at rubyforge.orghttp://rubyforge.org/mailman/listinfo/camping-list
>
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111118/d28a78c1/attachment-0001.html>