Re: Ruby

Is solidus compatible with rails 5.0.0 any advice on a ecommerce  start up
Ive heard spree is not safe to use and Im a Jr so sorry if my questions
arent as clear
when i run
 bundle exec rails g spree:install
[image: Inline image 1]
 I am following the instructions on this get started page @(
https://github.com/solidusio/solidus)  and I am also
following a video tutorial on youtube  (
https://www.youtube.com/watch?v=0mxGzk1Lfwg)
So far i havent been able to get past this step.

On Mon, Aug 1, 2016 at 4:18 PM, Matthew Kerwin <[email protected]>
wrote:

> Good advice, I'll just add some things:
>
> On 2 August 2016 at 08:38, Leam Hall <[email protected]> wrote:
>
>> Jeff,
>>
>> Like IRC, "just ask". There are a lot of smart people here and I've
>> gotten a world of help from them. Some things to consider as you post:
>>
>> 1. Specify platform and Ruby versions. Also, other tools or gems being
>> used.
>>
>
> ​This is really important, but subtle. Ruby 1.8.7 is long dead, but still
> gets a lot of use. A lot of things changed between 1.8 and 1.9 (which is
> also long dead, but still gets a lot of use.) And there are differences
> (both in detail and in conformance) between different implementations
> (MRI/CRuby, JRuby, Ruboto, Rubinius, ​etc.) Knowing your environment can
> help us help you a lot better.
>
>
>
>>
>> 2. Specify the question. The more specific, the better.
>>
>
> ​"Specific" is not the same as "short." If everyone asked this sort of
> question, I'd be such a happy camper:
>
> *I want to do <*this general​ thing*>. As a part of it I'm doing <*this
> specific thing*>. I am trying <*this approach*>, which I though would <*have this
> effect*>, however it seems to <*do this other thing*> instead. Can you
> help?  Here is a short snippet copied-and-pasted from my codebase/link to a
> gist that demonstrates my attempt.*
>
>
>
>>
>> 3. Show some code. That does three things; it often points out the error
>> as you type, it shows people you're put some effort into it, and it gives
>> an explicit demonstration of your code.
>>
>>
> ​It also gives us an idea of where you're at as a programmer. People
> who've spent 25 years writing C code tend to produce drastically different
> code from those who've done 10 years of java, or 5 years of
> ECMAScript/javascript, etc. and of course they're all different from
> someone who's never really done coding before.
>
> What you already know will change how we approach both: understanding your
> problem, and explaining a solution in a way you'll understand.​
>
>
>
>> 4. Be patient and thoughtful. Like I said, there are a lot of smart folks
>> here. Most of they have day jobs and families, not sure if anyone is paid
>> to just sit on the e-mail list and answer questions.
>>
>>
> ​I'm certainly not.
>
> Paid, that is; I'd like to think I'm patient and thoughtful. In the Ruby
> community we have a saying, centred on the man who created the language: *Matz
> is nice, so we are nice*.
>
> Cheers​
> --
>   Matthew Kerwin
>   http://matthew.kerwin.net.au/
>
>
> Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
>
>


Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>