npm i -g @nestjs/cli
nest new tasks-api
npm run start:devnest g mo tasks| // I'm tired of extensions that automatically: | |
| // - show welcome pages / walkthroughs | |
| // - show release notes | |
| // - send telemetry | |
| // - recommend things | |
| // | |
| // This disables all of that stuff. | |
| // If you have more config, leave a comment so I can add it!! | |
| { |
| #!/bin/bash | |
| # Project | |
| oc new-project workshop | |
| # Parksmap | |
| oc new-app quay.io/openshiftroadshow/parksmap:1.3.0 --name=parksmap -l 'app=workshop,component=parksmap,role=frontend,app.kubernetes.io/part-of=workshop' | |
| oc create route edge parksmap --service=parksmap | |
| oc policy add-role-to-user view -z default | |
| oc rollout restart deploy/parksmap | |
| # Nationalparks | |
| oc new-app java~https://github.com/openshift-roadshow/nationalparks.git --name nationalparks -l 'app=workshop,component=nationalparks,role=backend,app.kubernetes.io/part-of=workshop,app.kubernetes.io/name=java' |
I set up my linters for use with VS Code, so I only use the linting tools that can be integrated into the Problems tab, but these can be used from the command line. I have attempted to avoid having different tools give duplicate warnings, but this is a work in progress. The VS code settings.json is at https://gist.github.com/jlmelville/74d8fe778b0d89574e82ffe47c1e49ae.
Create a linting-requirements.txt file:
# this also installs pylint and pycodestyle
bandit
prospector[with_pyroma]
flake8
blackFrom time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
| # install haproxy | |
| yum install -y haproxy | |
| # config haproxy for rabbitmq | |
| cat > /etc/haproxy/haproxy.cfg << "EOF" | |
| global | |
| log 127.0.0.1 local0 notice | |
| maxconn 10000 | |
| user haproxy |