- post content on multiple plateform
- gather data around your content
- gather sociales at one place to prevent waste of time
- manage your scraped data localy
- alerts you when someone is talking about your content
- add fermet to hash json inside database
- Get source code
- Setup:
- have python3 and pip installed on your computer/serve 🐍
- go to
requirements.txt
in source code and setup your dev environement for the server (recommend via VScode after installing python3)- to launch the python dev environement to folder in terminal and use following cmd:
- Windows:
.\env\Scripts\activate.ps1
- Linux/macOS:
source env/bin/activate
- Windows:
- to launch the python dev environement to folder in terminal and use following cmd:
- go to
- or launch dockerfile
- have python3 and pip installed on your computer/serve 🐍
- Run
flask run
in terminal(.env) inside your app folder - Go to http://127.0.0.1:5000
- Register/Login a user account
- Setup API
- go to ressource API of your choice
- them input your credentials http://127.0.0.1:5000/api
- Use the current app as you please and add features if you think you can make it better
- Access API page
- add your differents keys inside of it
If you want to keep the vigie.db
file in your repository but prevent it from being updated, you can use git update-index --assume-unchanged vigie.db
. This will tell Git to temporarily ignore changes to the vigie.db
file. The file will remain in the repository and will not be updated until you run git update-index --no-assume-unchanged vigie.db
to start tracking changes again.
Please note that this is a local setting and will only apply to your local repository. Other users who clone the repository will still see changes to the vigie.db
file unless they also run the git update-index --assume-unchanged
command.
I dont like to go to all different sociales to check my private msg or check if i got tag somewhere. My objective was to make a free solution to gather my social at one place. I got stuck firstly by twitter api paywall to access mp even my own via there api (twitter is my main social activity service), so i had to change my approach to make my research on API not turn to waste so i made, the actual implementation that you have (post and read only).