Skip to content
Snippets Groups Projects
Commit 9039e990 authored by nimrod's avatar nimrod
Browse files

Corrected spelling and grammar errors.

parent a5d9b692
No related branches found
No related tags found
No related merge requests found
...@@ -5,9 +5,9 @@ bundle_certs ...@@ -5,9 +5,9 @@ bundle_certs
:summary: Announce a new tool, bundle_certs :summary: Announce a new tool, bundle_certs
Like I said in a previous blog post, I rarely blog but I run :code:`git init Like I said in a previous blog post, I rarely blog but I run :code:`git init
project-name` like crazy. So here's a new such repo, `bundle_certs project-name` pretty regularly. So here's a new such repo, `bundle_certs
<https://www.shore.co.il/cgit/bundle_certs/>`_. A simple shell script for <https://www.shore.co.il/cgit/bundle_certs/>`_. A simple shell script for
bundling (in correct order) SSL certificates. bundling (in the correct order) SSL certificates.
How I start new projects How I start new projects
------------------------ ------------------------
...@@ -17,9 +17,9 @@ and `ssh-ca <https://www.shore.co.il/cgit/ssh-ca/>`_ have some commonality in ...@@ -17,9 +17,9 @@ and `ssh-ca <https://www.shore.co.il/cgit/ssh-ca/>`_ have some commonality in
how I use them and this seems like a good opportunity to share. First of all I how I use them and this seems like a good opportunity to share. First of all I
keep my rc files (like :code:`.vimrc`) in the keep my rc files (like :code:`.vimrc`) in the
`rcfiles <https://www.shore.co.il/cgit/rcfiles/`>_ repo. However I don't install `rcfiles <https://www.shore.co.il/cgit/rcfiles/`>_ repo. However I don't install
as mentioned in the documentation. Instead I add as Git submodules and now I them as mentioned in the documentation. Instead I add them as Git submodules
can be reasonably sure that when I clone the rcfiles repository, the aliases and and now I can be reasonably sure that when I clone the rcfiles repository, the
sourced files mentioned in :code:`.bashrc` are present. Here's how: aliases and sourced files mentioned in :code:`.bashrc` are present. Here's how:
.. code:: shell .. code:: shell
...@@ -44,10 +44,11 @@ repositories are the same (different license, programming language, pre-commit ...@@ -44,10 +44,11 @@ repositories are the same (different license, programming language, pre-commit
and git hooks). and git hooks).
Another option I know of are tools that manage a specific aspect of the repo, Another option I know of are tools that manage a specific aspect of the repo,
for example the license, or :code:`.gitignore`. A third option is using a for example the license, or :code:`.gitignore`.
project management tool like `Cargo <http://doc.crates.io/>`_ for Rust or
`Leiningen <http://leiningen.org/>`_ for Clojure. But not all aspects or A third option is using a project management tool like `Cargo
languages have such tools. <http://doc.crates.io/>`_ for Rust or `Leiningen <http://leiningen.org/>`_
for Clojure. But not all aspects or languages have such tools.
The fourth option I'm thinking of is using a scaffloding tool, mainly `Yeoman The fourth option I'm thinking of is using a scaffloding tool, mainly `Yeoman
<http://yeoman.io/>`_ as it seems to the most popular one but its focus is on <http://yeoman.io/>`_ as it seems to the most popular one but its focus is on
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment