Data management and scheduler backend for the Cookiebot and Bombot Telegram bots
This project aims to manage a NoSQL (MongoDB) database with https.
Using: Java 17 + Spring Boot + Spring Web + Spring Data MongoDB + Spring Security
It's necessary to create a file called "application.properties" inside src/main/resources folder.
spring.data.mongodb.uri=YourUriHere
spring.security.user.name=username
spring.security.user.password=password
spring.security.user.roles=ADMIN
By default, unprivileged users on Linux are blocked from hosting on ports under 1024.
In order to allow any port to any user, insert this line into the file /etc/sysctl.d/99-sysctl.conf with a text editor:
net.ipv4.ip_unprivileged_port_start=0
This new configuration will be effective after a reboot. You can also apply it immediately:
sudo sysctl -p /etc/sysctl.d/99-sysctl.conf
After that, use keytool to generate a certificate (for a self-signed https):
keytool -genkey -alias bootsecurity -storetype PKCS12 -keyalg RSA -keysize 2048 -keystore bootsecurity.p12 -validity 36500
Copy the bootsecurity.p12 file to the root folder of the project and finally add these settings to your application.properties:
server.port=443
server.ssl.key-store=bootsecurity.p12
server.ssl.key-store-password=YourCertificatePasswordHere
server.ssl.key-store-type=PKCS12
server.ssl.key-alias=bootsecurity
And you're done!
After compiling to a jar file, the software will look for a bootsecurity.p12 file on the same directory as the .jar file itself.
https://host/configs [GET]
https://host/configs/{id} [GET, POST, PUT, DELETE]
Json attributes:
id : string (used in place of {id} as explained above)
furbots : boolean
stickerSpamLimit : integer
timeWithoutSendingImages : integer
timeCaptcha : integer
functionsFun : boolean
functionsUtility : boolean
sfw : boolean
language : string
publisherPost : boolean
publisherAsk : boolean
threadPosts : string
maxPosts : integer
https://host/registers [GET]
https://host/registers/{id} [GET, POST, DELETE]
https://host/registers/{id}/users [GET, POST, PUT, DELETE]
Json attributes:
id : string (used in place of {id} as explained above)
At /users:
user : string
date : string
accountId : string
https://host/rules [GET]
https://host/rules/{id} [GET, POST, PUT, DELETE]
Json attributes:
id : string (used in place of {id} as explained above)
rules : string
https://host/welcomes [GET]
https://host/welcomes/{id} [GET, POST, PUT, DELETE]
Json attributes:
id : string (used in place of {id} as explained above)
message : string
https://host/blacklist [GET]
https://host/blacklist/{id} [GET, POST, DELETE]
Json attributes:
id : string (used in place of {id} as explained above)
https://host/stickers [GET]
https://host/stickers/{id} [GET, POST, PUT, DELETE]
Json attributes:
id : string (used in place of {id} as explained above)
lastUsed : string
https://host/randomdatabase [GET/POST]
Json attributes:
id : string
idMessage : string
idMedia : string
https://host/stickerdatabase [GET/POST]
Json attributes:
id : string
https://host/raffles [GET]
https://host/raffles/{name} [GET, POST, DELETE]
https://host/raffles/{name}/participants [GET, POST, PUT, DELETE]
Json attributes:
name : string (used in place of {name} as explained above)
award : string
deadline: string
At /participants:
user : string