How to track outsider quirks projects

It is possible that the answer to this question may be standard error tracking software like jira or fogbugz, but I kind of hope someone out there knows a better system for what I am describing.

My most recent project requires a lot of setup difficulties to get into a position where I can really start the coding section. For instance:

  • A series of intricate internal company teams before I can enable SSH.
  • Make sure that the third-party classes that make external calls have the company’s proxy settings configured and make sure that these settings are not set when installed in the production environment.
  • Make sure the proxy is installed before installing the pear packages.
  • Other similar things, mainly related to internal IT security and working with modules and packages.

Individually, none of these things is a huge deal, and I wrote extensive notes for myself regarding the exact commands and announcements I made, but they are currently in a common text document, and it will be difficult to remember exactly where I need to , far from the line. We also have several new employees who will begin in the near future, and I will rather give them an easier time to create their software environments.

As I said, they are definitely not “programming quirks,” but simply a constant game that occurs before programming begins in earnest. Any thoughts on how to best document these things for common sense and for future generations?

+5
4

wiki . , - .

, , , , , - .

+7

script - (bash, python, applescript, autohotkey, ).

- . . "Set_up_everything.bash".

: , , , script/, , .

, ( ).

Edit:

, : ! (- ..), - , .

+6

. , , - , .

"bin" . , . SSH . , capistrano -, . , - , - .

. . ( , .) , AWS, , , github . ! !

+2

A: , , . , moker SOAP- (SoapUI Mockservices) .. , , mock/dummy/stub services, (, .ini).
, "" , , zip , , .. , .

, ! , , .

B: , , , "" . .. , , , , . , , , , , . , , , . , HR. , , , , , " ". . , ( , , , , , ..). // . , 3 , nothign .

Update: and whatever you do, check it for version control so you can come back, compare, etc.

+1
source

All Articles