Chris Rose offbyone

## amazon.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                offbyone
                / amazon.md
            
            
              Created
              August 23, 2020 17:33
                — forked from terabyte/amazon.md
            
              
                Amazon's Build System
              
          
    Prologue

I wrote this answer on stackexchange, here:
https://stackoverflow.com/posts/12597919/
It was wrongly deleted for containing "proprietary information" years later.  I think that's bullshit so I am posting it here.  Come at me.
The Question

Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?

  
## key.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                offbyone
                / key.md
            
            
              Last active
              May 13, 2020 22:13
            
              
                Twitter (un)official Consumer Key
              
          
    Twitter Official Consumer Key

Test
Twitter for Android

type:            PIN
Consumer key:    3nVuSoBZnx6U4vzUxf5w
Consumer secret: Bcs59EFbbsdF6Sl9Ng71smgStWEGwXXKSjYvPVt7qys

Twitter for iPhone

type: PIN

  
## postactivate.sh
#!/bin/zsh -w
# This hook is run after this virtualenv is activated.

# If the virtualenv has a .project file in it then check to see the
# path contained within it exists, and if so collect etags for .py
# files in that path.  Also includes etags generated for the
# virtualenv itself—if it finds them.  Virtualenv tags are generated
# with the `venvtags` function defined in .zshrc: which should be run
# manually after, for example, installing new requirements.  The
# resulting TAGS file is then hooked into the virtualenv by a
	#!/bin/zsh -w
	# This hook is run after this virtualenv is activated.

	# If the virtualenv has a .project file in it then check to see the
	# path contained within it exists, and if so collect etags for .py
	# files in that path. Also includes etags generated for the
	# virtualenv itself—if it finds them. Virtualenv tags are generated
	# with the `venvtags` function defined in .zshrc: which should be run
	# manually after, for example, installing new requirements. The
	# resulting TAGS file is then hooked into the virtualenv by a