Prints a folder in a JSON format
python main.py <path> > <output_file.json>
# -*- coding: utf-8 -*- | |
#!/usr/bin/env python3 | |
import sys | |
# Print iterations progress | |
def printProgressBar(iteration, total, prefix='Progress', suffix='complete', decimals=1, length=30, fill='█'): | |
""" | |
Call in a loop to create terminal progress bar | |
@params: | |
iteration - Required : current iteration (Int) |
import argparse | |
if __name__ == '__main__': | |
# construct the argument parser and parse the arguments | |
ap = argparse.ArgumentParser() | |
ap.add_argument("-i", "--image", required=False, | |
help="Path to the image to be scanned") | |
args = vars(ap.parse_args()) | |
if args["image"] == None: |
#!/usr/bin/python | |
# -*- coding: utf-8 -*- | |
import logging | |
import os | |
from logging.handlers import RotatingFileHandler | |
class LogManager: | |
def __init__(self, log_name, |
#!/usr/bin/env python3 | |
# encoding: utf-8 | |
"""Use instead of `python3 -m http.server` when you need CORS""" | |
from http.server import HTTPServer, SimpleHTTPRequestHandler | |
import sys | |
class CORSRequestHandler(SimpleHTTPRequestHandler): | |
def end_headers(self): |
[MASTER] | |
# A comma-separated list of package or module names from where C extensions may | |
# be loaded. Extensions are loading into the active Python interpreter and may | |
# run arbitrary code. | |
extension-pkg-whitelist= | |
# Add files or directories to the blacklist. They should be base names, not | |
# paths. | |
ignore=CVS |
import numpy as np | |
# Variável onde seu índice representa a posíção no labirinto | |
# E seu valor representa os possíveis lugares para se mover | |
# em outras palavras, a tabela de adjacencia | |
NOS = [ | |
[1],#nó 0 | |
[0, 2, 4, 3],#nó 1 | |
[1],#nó 2 | |
[1, 5],#nó 3 |
That is it! You read right. If you are building small applications and don't need to prepare a super complex environment to deploy it and just want to keep the code on an updated server, you can set up a bare repository on your remote machine and "listen" changes on the master. So, with a push, you can always update the code on the remote machine.
Step 1: Create the repository that will listen to the pushes on GIT and the folder where the files will be stored
That is it! You read right. If you are building small applications and don't need to prepare a super complex environment to deploy it and just want to keep the code on an updated server, you can set up a bare repository on your remote machine and "listen" changes on the master. So, with a push, you can always update the code on the remote machine.
Step 1: Create the repository that will listen to the pushes on GIT and the folder where the files will be stored