Skip to content

Instantly share code, notes, and snippets.

View aguerrave's full-sized avatar

Alejandro Guerra aguerrave

  • Alge Consultores Gerenciales
  • Venezuela
  • 07:20 (UTC -04:00)
View GitHub Profile
@aguerrave
aguerrave / Analysis.py
Created July 24, 2022 01:56 — forked from ShambhaviPataskar/Analysis.py
A sales analysis using jupyter notebook
#!/usr/bin/env python
# coding: utf-8
# # Sales Analysis
# ### import necessary libraries
# In[1]:
@aguerrave
aguerrave / dbeaver.ini
Created December 6, 2021 21:45 — forked from souhaiebtar/dbeaver.ini
[dbeaver config file] .ini file for dbeaver #dbeaver #linux
# path on linux /usr/share/dbeaver/dbeaver.ini
# path on macos /Applications/DBeaverEE.app/Contents/Eclipse/dbeaver.ini
-vm
/usr/bin/java
-startup
plugins/org.eclipse.equinox.launcher_1.5.600.v20191014-2022.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.1100.v20190907-0426
-vmargs
-XX:+IgnoreUnrecognizedVMOptions
@aguerrave
aguerrave / postgres_fdw.sql
Created November 23, 2020 20:08 — forked from sathed/postgres_fdw.sql
postgres_fdw example
/***** "Remote" server first *****/
-- Note: Unless the object you are trying to gain access to is in the same DATABASE, it's a remote datebase. Even if it's
-- on the same node!
-- 1. create the role and assign it a password. Note: CREATE USER is an alias for CREATE ROLE. Either one is fine
CREATE ROLE new_user WITH PASSWORD 'somepassword';
-- 2. Grant the required permissions. This grants select, insert, update, and delete on all tables in the public schema.
-- I also gave execute to all functions in the public schema as well.
GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO new_user;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA public TO new_user;
@aguerrave
aguerrave / xclip_ssh_rsa.sh
Created August 16, 2020 20:07 — forked from orendon/xclip_ssh_rsa.sh
linux copy ssh rsa key, xclip xsel pbcopy
xclip -sel clip < ~/.ssh/id_rsa.pub
# in case you get a display null error
DISPLAY=:0 xclip -sel clip < ~/.ssh/id_rsa.pub
# osx
pbcopy < ~/.ssh/id_rsa.pub
secured:
chain:
middlewares:
- default-whitelist
- default-headers
@aguerrave
aguerrave / proxmox-proxy
Created September 4, 2019 16:26 — forked from basoro/proxmox-proxy
Running Proxmox behind a single IP address
I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables.
What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding.
Network configuration
Here’s how it’s done:
Create a virtual interface that serves as the gateway for your VMs:
@aguerrave
aguerrave / docker-compose.yml
Created September 2, 2019 00:42 — forked from analogic/docker-compose.yml
Poste.io (with Lets Encrypt) + Nginx reverse proxy + Nginx Lets encrypt companion
version: '3'
services:
nginx-proxy:
image: jwilder/nginx-proxy
labels:
com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
container_name: nginx-proxy
restart: unless-stopped
ports: