731 Service creation script #808
No reviewers
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!808
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "731-Service-creation-script"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Script that generates a new service according to #731's template.
Needs to be tested and reviewed on both a Windows system and an Unix system.
There is an issue with upper case and lower case. I informed the developer. He will inform back and I can test.
There is an issue with upper case and lower case. I informed the developer. He will inform back and I can test.
There is still an issue in redirect.
Noticed something when I was fixing my own service that uses this script, on line 163 (Unix) and 168 (Windows) where the connectionString is written as
"Host=PostgreSQL;Port=5432;Database=users;UsercapitalName={DbUser};Password={DbPassword}". All services are not using the users database, and honestly, there isn't a good way of selecting this since the script can't know if the service is for a sensor or something else.The best solution is one that we are already planning; each service has its own database. Then the name of the service could be used. Until then, the script will assign it to the sensors database.
The scripts seems to be working.
I just want to add it needs to be documented somewhere that we need to add into README or somewhere that for Linux it needs to be running without
sh SCRIPT_NAME@a24julot @a22erigr@a24timsv wrote in #808 (comment):
as improvement it could be that the second input you give the information whether it is a sensor or api. As the structure of the api differs from sensor. This could be an imporvement but does not need to be fixed in this issue.
Very useful. I create an improvement issue for the api.
@a24julot you can merge this one.