Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
daveplsno 482a2612f0
Merge pull request #3 from daveplsno/devel
il y a 2 mois
grafana updates il y a 2 mois
pinger_backend updates il y a 2 mois
pinger_client updates il y a 3 mois
pinger_frontend updates il y a 2 mois
.gitignore updates il y a 2 mois
LICENSE Create LICENSE il y a 3 mois
README.md readme chgs il y a 3 mois

README.md

pinger

it pings, it records, it doens’t do anything else, eventually it might also graph.

thinken basic steps to get dev env setup is (to be tested lmao):

1) clone repo 2) create .env file in pinger_server (example provided) 3) create .env file in pinger_server/data/pinger_server (example provided) 5) navigate back to project root and compose up 3) enter container

docker exec -it pinger_server bash

5) migrate db

python manage.py migrate

5) create superuser

python manage.py createsuperuser

6) log into admin page, generate token for admin 7) create .env file in pinger_client (example provided) 8) probably good idea to take ownership of all the newly created files by root user (thx docker). from the project root run

sudo chown -R $USER:$USER .

unfortunately the api url for targets and db posts is currently hardcoded in the pinger_client container, so yeah not much can be done here until i change it, i’ll eventually pass this as a container env the same as the token so ppl can use their own local server. much work to be done.