initial commit

did an oopsie

spaces -> tabs + ipv6

cgi :D


missed key name


minio creds
Hazel 2023-03-15 21:48:49 +00:00
parent 06d6030c96
commit d714600691
Signed by: h4
GPG Key ID: DD44A9C83259DAEB
12 changed files with 158 additions and 91 deletions

View File

@ -1,92 +1,4 @@
# setup
# AS200242 setup scripts
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create]( or [upload]( files
- [ ] [Add files using the command line]( or push an existing Git repository with the following command:
cd existing_repo
git remote add origin
git branch -M main
git push -uf origin main
## Integrate with your tools
- [ ] [Set up project integrations](
## Collaborate with your team
- [ ] [Invite team members and collaborators](
- [ ] [Create a new merge request](
- [ ] [Automatically close issues from merge requests](
- [ ] [Enable merge request approvals](
- [ ] [Automatically merge when pipeline succeeds](
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](
- [ ] [Use pull-based deployments for improved Kubernetes management](
- [ ] [Set up protected environments](
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to []( for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
Stuff we use to automate to get a POP up and running.
These are built mainly for Debian 11.

certbot/cf.ini Normal file
View File

@ -0,0 +1,2 @@
dns_cloudflare_email =
dns_cloudflare_api_key =

12 Executable file
View File

@ -0,0 +1,12 @@
sudo apt update
sudo apt install snapd
sudo snap install certbot --classic
sudo snap set certbot trust-plugin-with-root=ok
sudo snap install certbot-dns-cloudflare
# refresh env
eval "$(exec /usr/bin/env -i "${SHELL}" -l -c "export")"
# init certbot dir
certbot &2>/dev/null

9 Executable file
View File

@ -0,0 +1,9 @@
wget -O minio.deb
sudo dpkg -i minio.deb
sudo cp ./systemd/minio.service /etc/systemd/system/minio.service
sudo vim /etc/systemd/system/minio.service
sudo systemctl daemon-reload
sudo systemctl enable minio --now

3 Executable file
View File

@ -0,0 +1,3 @@
sudo apt update -y
sudo apt install -y nginx

nginx/ Normal file
View File

@ -0,0 +1,26 @@
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
ssl_certificate /etc/letsencrypt/live/ravy/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/ravy/privkey.pem;
ssl_trusted_certificate /etc/letsencrypt/live/ravy/chain.pem;
client_max_body_size 0;
location / {
proxy_pass http://localhost:9000/;
proxy_set_header Host $host;
proxy_buffering off;
location /anycast-cgi {
default_type text/plain;
location /anycast-cgi/trace {
return 200 'loc=$hostname\ncf=$remote_addr\nip=$http_cf_connecting_ip';

nginx/nginx.conf Normal file
View File

@ -0,0 +1,48 @@
user www-data;
pid /run/;
worker_processes auto;
worker_rlimit_nofile 65535;
events {
worker_connections 1024;
http {
charset utf-8;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
server_tokens off;
log_not_found off;
types_hash_max_size 2048;
client_max_body_size 16M;
server_names_hash_max_size 1024;
server_names_hash_bucket_size 128;
include /etc/nginx/mime.types;
default_type application/octet-stream;
# logging
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log warn;
ssl_session_timeout 1d;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
# OWASP A (Advanced) configuration
ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ecdh_curve secp384r1;
# OCSP Stapling
ssl_stapling on;
ssl_stapling_verify on;
resolver valid=60s;
resolver_timeout 2s;
# load configs
include /etc/nginx/sites-enabled/*;

7 Executable file
View File

@ -0,0 +1,7 @@

3 Executable file
View File

@ -0,0 +1,3 @@
cp ./certbot/cf.ini /etc/letsencrypt/cf.ini
sudo chmod u=rw,g=,o= /etc/letsencrypt/cf.ini
vim /etc/letsencrypt/cf.ini

5 Executable file
View File

@ -0,0 +1,5 @@
certbot certonly \
--agree-tos \
--dns-cloudflare --dns-cloudflare-credentials /etc/letsencrypt/cf.ini \
--cert-name ravy \
-d -d *

5 Executable file
View File

@ -0,0 +1,5 @@
sudo cp ./nginx/nginx.conf /etc/nginx/nginx.conf
sudo cp ./nginx/ /etc/nginx/sites-available/
sudo ln -s /etc/nginx/sites-available/ /etc/nginx/sites-enabled/
sudo rm /etc/nginx/sites-enabled/default
nginx -t && sudo systemctl restart nginx

systemd/minio.service Normal file
View File

@ -0,0 +1,35 @@
ExecStart=/usr/local/bin/minio server --address=:9000 --console-address=:9001 /data/minio
# Let systemd restart this service always
# Specifies the maximum file descriptor number that can be opened by this process
# Specifies the maximum number of threads this process can create
# Disable timeout logic and wait until process is stopped
# Built for ${}-${project.version} (${})