Dontyoudarenottobeaware

Two weeks ago a colleague was showing me a diagnosis software which is for free. And as a teacher those things are good to know. Anyway I already was looking for a little project I could use to get acquainted with rails 4 and evaluating checkboxes, so I picked this one up: to do diagnoses. The project is hosted on GitHub and if others want to contribute I will have to get myself into git branches and how to merge them without harming the app. And I will deploy the app as it is to my server: app in production stage . What does it do? There are categories (has_many and belongs_to rails associations) and questions belonging to them. So far the index page will show links to the categories and clicking them will create a page with a random choice questions. These questions are displayed with checkboxes and you can evaluate them by posting you choices and get a result page. It is nothing fancy but still something I can already work with my pupils and on the way I have learned ...

When progaming its nice to have several repositories in case you want to try a real life production test AND a github site for others to see and try. Especially the production test site gave me a lot of input or better: things to deal with which were good to have been dealt with, e.g. did I have to downgrade one gem. Anyway, this is what I found: your .git/config [remote "origin"]         url = git@github.com:xxxxx         fetch = +refs/heads/*:refs/remotes/origin/* [remote "hosted"]         url = ssh://xxxxx         fetch = +refs/heads/*:refs/remotes/hosted/*  Your .git/config should look like this: [remote "Origin"]         url = git@github.com:xxxxx         url = ssh://xxxxx And a simple "git push Origin" uploads to two repos.

Hello geeks! When programming rails I was very releaved having git at my site. And lately I was forced to deal with git sooner than expected Normaly I end deploying with this command, and of course before that I checked my local installation: cap deploy This time I had some trouble with my asset pipeline in production mode. Mainly because of the integration of russfrisch's html5 boilerplate. It took me a while to realize my mistake with rescuing my remote installation, because I was fixing my local system with this command: git log # look for hash git reset --hard *hash* # insert you hash where to go back to cap deploy # new deployment of old version Well, this did not work.......................... I forgot the fact my remote git system is used by capistrano to deploy, so I had to set that bare repository back too: git push --force origin *hash*:master # insert the same hash, see 'git log' ...