karaolidis/admina
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add admina base

Browse Source 
Signed-off-by: Nikolaos Karaolidis <nick@karaolidis.com>
This commit is contained in:
Nick Karaolidis
2023-03-28 20:42:53 +03:00
parent 53e48f6012
commit aef5a27d02
13 changed files with 404 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

161
.gitignore vendored Normal file
View File

@@ -0,0 +1,161 @@
# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
*$py.class
# C extensions
*.so
# Distribution / packaging
.Python
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST
session.json
# PyInstaller
# Usually these files are written by a python script from a template
# before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec
# Installer logs
pip-log.txt
pip-delete-this-directory.txt
# Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py,cover
.hypothesis/
.pytest_cache/
cover/
# Translations
*.mo
*.pot
# Django stuff:
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal
# Flask stuff:
instance/
.webassets-cache
# Scrapy stuff:
.scrapy
# Sphinx documentation
docs/_build/
# PyBuilder
.pybuilder/
target/
# Jupyter Notebook
.ipynb_checkpoints
# IPython
profile_default/
ipython_config.py
# pyenv
# For a library or package, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in:
# .python-version
# pipenv
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
#Pipfile.lock
# poetry
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
# This is especially recommended for binary packages to ensure reproducibility, and is more
# commonly ignored for libraries.
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
#poetry.lock
# pdm
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
#pdm.lock
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
# in version control.
# https://pdm.fming.dev/#use-with-ide
.pdm.toml
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
__pypackages__/
# Celery stuff
celerybeat-schedule
celerybeat.pid
# SageMath parsed files
*.sage.py
# Environments
.env
.venv
env/
venv/
ENV/
env.bak/
venv.bak/
# Spyder project settings
.spyderproject
.spyproject
# Rope project settings
.ropeproject
# mkdocs documentation
/site
# mypy
.mypy_cache/
.dmypy.json
dmypy.json
# Pyre type checker
.pyre/
# pytype static type analyzer
.pytype/
# Cython debug symbols
cython_debug/
# PyCharm
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
# and can be added to the global gitignore or merged into this file. For a more nuclear
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
#.idea/

30
.gitlab-ci.yml Normal file
View File

@@ -0,0 +1,30 @@
# Build a Docker image with CI/CD and push to the GitLab registry.
# Docker-in-Docker documentation: https://docs.gitlab.com/ee/ci/docker/using_docker_build.html
#
# This template uses one generic job with conditional builds
# for the default branch and all other (MR) branches.
docker-build:
# Use the official docker image.
image: docker:latest
stage: build
before_script:
- docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
# Default branch leaves tag empty (= latest tag)
# All other branches are tagged with the escaped branch name (commit ref slug)
script:
- |
if [[ "$CI_COMMIT_BRANCH" == "$CI_DEFAULT_BRANCH" ]]; then
tag=""
echo "Running on default branch '$CI_DEFAULT_BRANCH': tag = 'latest'"
else
tag=":$CI_COMMIT_REF_SLUG"
echo "Running on branch '$CI_COMMIT_BRANCH': tag = $tag"
fi
- docker build --pull -t "$CI_REGISTRY_IMAGE${tag}" .
- docker push "$CI_REGISTRY_IMAGE${tag}"
# Run this job in a branch where a Dockerfile exists
rules:
- if: $CI_COMMIT_BRANCH
exists:
- Dockerfile

3
.vscode/settings.json vendored Normal file
View File

@@ -0,0 +1,3 @@
{
"python.formatting.provider": "autopep8"
}

10
Dockerfile Normal file
View File

@@ -0,0 +1,10 @@
FROM python
WORKDIR /app
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY ./src .
CMD ["python", "main.py"]

90
README.md
View File

@@ -1,92 +1,4 @@
# admina
A Facebook messenger bot powered by OpenAI and Stable Diffusion.
## 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 README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://git.karaolidis.com/Nikas36/admina.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://git.karaolidis.com/Nikas36/admina/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# 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 [makeareadme.com](https://www.makeareadme.com/) 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.

19
docker-compose.yml Normal file
View File

@@ -0,0 +1,19 @@
version: '3.9'
services:
admina:
image: registry.karaolidis.com/nikas36/admina:latest
build: .
restart: unless-stopped
depends_on:
- db
env_file:
- .env
db:
image: mongo:latest
restart: unless-stopped
environment:
MONGO_INITDB_DATABASE: admina
volumes:
- ./mongo-init.js:/docker-entrypoint-initdb.d/mongo-init.js

12
mongo-init.js Normal file
View File

@@ -0,0 +1,12 @@
db.createUser(
{
user: "admina",
pwd: "admina",
roles: [
{
role: "readWrite",
db: "admina"
}
]
}
);

24
requirements.txt Normal file
View File

@@ -0,0 +1,24 @@
aiohttp==3.8.4
aiosignal==1.3.1
async-timeout==4.0.2
attrs==22.2.0
autopep8==2.0.2
beautifulsoup4==4.12.0
blinker==1.5
certifi==2022.12.7
charset-normalizer==3.1.0
dnspython==2.3.0
fbchat @ git+https://git.karaolidis.com/Nikas36/fbchat.git@2fa1b58336731a5de923018bcb9ec4488eeeb923
frozenlist==1.3.3
idna==3.4
multidict==6.0.4
openai==0.27.2
paho-mqtt==1.6.1
pycodestyle==2.10.0
pymongo==4.3.3
requests==2.28.2
soupsieve==2.4
tomli==2.0.1
tqdm==4.65.0
urllib3==1.26.15
yarl==1.8.2

59
src/main.py Normal file
View File

@@ -0,0 +1,59 @@
import fbchat
from message import handle_message
from util.logger import logger
import atexit
from blinker import Signal
from threading import Thread
from os import environ
def on_event(sender, session, event):
match sender:
case fbchat.MessageEvent:
Thread(target=handle_message, args=(
sender, session, event)).start()
case _:
logger.debug("Ignoring event: %s", event)
def main():
email = environ.get("FB_EMAIL")
password = environ.get("FB_PASSWORD")
cookie_path = environ.get("FB_COOKIE_PATH") or "session.json"
if not email or not password:
raise ValueError("FB_EMAIL and FB_PASSWORD must be set")
try:
logger.info("Loading cookies from %s", cookie_path)
session = fbchat.Session.from_file(cookie_path)
except (FileNotFoundError, fbchat.FacebookError):
logger.warning("Failed to load cookies from %s", cookie_path)
logger.info("Logging in with email and password")
session = fbchat.Session.login(
email, password, on_2fa_callback=lambda: input("Input 2FA code: ")
)
session.to_file(cookie_path)
logger.info("Saved cookies to %s", cookie_path)
finally:
if session.is_logged_in():
logger.info("Logged in as %s", session.user.id)
else:
raise ValueError("Failed to log in")
atexit.register(lambda: session.to_file(cookie_path))
listener = fbchat.Listener(
session=session, chat_on=False, foreground=False)
events = Signal()
events.connect(on_event)
for event in listener.listen():
events.send(type(event), session=session, event=event)
if __name__ == "__main__":
main()

8
src/message.py Normal file
View File

@@ -0,0 +1,8 @@
import fbchat
from util.logger import logger
from util.database import database
from util.session import session
def handle_message(_, event: fbchat.MessageEvent):
logger.info("Received message from %s: %s", event.author.id, event.text)

15
src/util/database.py Normal file
View File

@@ -0,0 +1,15 @@
import pymongo
from os import environ
MONGO_HOST = environ.get("MONGO_HOST")
MONGO_PORT = environ.get("MONGO_PORT")
MONGO_USERNAME = environ.get("MONGO_USERNAME")
MONGO_PASSWORD = environ.get("MONGO_PASSWORD")
MONGO_DATABASE = environ.get("MONGO_DATABASE")
if not MONGO_HOST or not MONGO_PORT or not MONGO_USERNAME or not MONGO_PASSWORD or not MONGO_DATABASE:
raise ValueError(
"MONGO_HOST, MONGO_PORT, MONGO_USERNAME, MONGO_PASSWORD and MONGO_DATABASE must be set")
database = pymongo.MongoClient(MONGO_HOST, int(
MONGO_PORT), username=MONGO_USERNAME, password=MONGO_PASSWORD, authSource=MONGO_DATABASE)[MONGO_DATABASE].client

29
src/util/logger.py Normal file
View File

@@ -0,0 +1,29 @@
import sys
import logging.config
import logging.handlers
def handle_exception(exception_type, exception, traceback):
logger.error(
"Uncaught exception",
exc_info=(exception_type, exception, traceback),
)
sys.excepthook = handle_exception
logger = logging.getLogger()
logger.setLevel(logging.DEBUG)
formatter = logging.Formatter(
'%(asctime)s:%(levelname)s:%(name)s:%(module)s:%(funcName)s:%(lineno)s:%(message)s')
stream_handler = logging.StreamHandler(sys.stdout)
stream_handler.setLevel(logging.INFO)
stream_handler.setFormatter(formatter)
logger.addHandler(stream_handler)
file_handler = logging.FileHandler('output.log')
file_handler.setLevel(logging.INFO)
file_handler.setFormatter(formatter)
logger.addHandler(file_handler)

33
src/util/session.py Normal file
View File

@@ -0,0 +1,33 @@
import fbchat
from util.logger import logger
import atexit
from os import environ
FB_EMAIL = environ.get("FB_EMAIL")
FB_PASSWORD = environ.get("FB_PASSWORD")
FB_COOKIE_PATH = environ.get("FB_COOKIE_PATH") or "session.json"
if not FB_EMAIL or not FB_PASSWORD:
raise ValueError("FB_EMAIL and FB_PASSWORD must be set")
try:
logger.info("Loading cookies from %s", FB_COOKIE_PATH)
session = fbchat.Session.from_file(FB_COOKIE_PATH)
except (FileNotFoundError, fbchat.FacebookError):
logger.warning("Failed to load cookies from %s", FB_COOKIE_PATH)
logger.info("Logging in with email and password")
session = fbchat.Session.login(
FB_EMAIL, FB_PASSWORD, on_2fa_callback=lambda: input(
"Input 2FA code: ")
)
session.session.to_file(FB_COOKIE_PATH)
logger.info("Saved cookies to %s", FB_COOKIE_PATH)
finally:
if session.is_logged_in():
logger.info("Logged in as %s", session.user.id)
else:
raise ValueError("Failed to log in")
atexit.register(lambda: session.to_file(FB_COOKIE_PATH))