| Run in command line: | |
| RAILS_ENV=production rake db:create db:schema:load |
| Rails scaffolding types | |
| These types are valid since Rails version 2: | |
| string | |
| text (long text, up to 64k, often used for text areas) | |
| datetime | |
| date | |
| integer | |
| binary | |
| boolean |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
| git branch -m old_branch new_branch # Rename branch locally | |
| git push origin :old_branch # Delete the old branch | |
| git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
| #!/usr/bin/env bash | |
| sudo locale-gen en_US.UTF-8 | |
| sudo update-locale LANG=en_US.UTF-8 | |
| sudo update-locale LC_ALL=en_US.UTF-8 | |
| sudo apt-get update | |
| sudo apt-get install -y build-essential git curl libxslt1-dev libxml2-dev libssl-dev | |
| # postgres |
| ### Nginx ### | |
| check process nginx with pidfile /opt/nginx/logs/nginx.pid | |
| start program = "/etc/init.d/nginx start" | |
| stop program = "/etc/init.d/nginx stop" | |
| if cpu > 60% for 2 cycles then alert | |
| if cpu > 80% for 5 cycles then restart | |
| if memory usage > 80% for 5 cycles then restart | |
| if failed host 127.0.0.1 port 80 protocol http | |
| then restart | |
| if 3 restarts within 5 cycles then timeout |
| # paths | |
| app_path = "/home/deployer/qna" | |
| working_directory "#{app_path}/current" | |
| pid "#{app_path}/current/tmp/pids/unicorn.pid" | |
| # listen | |
| listen "#{app_path}/shared/tmp/sockets/unicorn.qna.sock", backlog: 64 | |
| # logging | |
| stderr_path "log/unicorn.stderr.log" |
A class should have only a single responsibility.
Every class should have a single responsibility, and that responsibility should be entirely encapsulated. All its services should be narrowly aligned with that responsibility, this embrace the high cohesion.
Software entities should be open for extension, but closed for modification.
