-
-
Notifications
You must be signed in to change notification settings - Fork 388
The major release 2.0.0 is backwards incompatible with existing installations, since the migration scripts are manually altered (See commit) and the checksums in the metadata table of Flyway (our DB migration tool) need to be corrected. This can be done executing the following command:
mvn initialize flyway:repair
You can easily run SteVe behind a reverse proxy by forwarding /steve/
to the respective host. The following configuration would work for NGINX:
location /steve/ {
proxy_pass http://192.168.1.100:8080/steve/;
}
Keep in mind that OCPP-J using WebSockets might require additional configuration or depending on your proxy software, wont work at all. For NGINX the configuration could look like this:
location /steve/websocket/CentralSystemService {
proxy_pass http://192.168.1.100:8080/steve/websocket/CentralSystemService;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_connect_timeout 1d;
proxy_send_timeout 1d;
proxy_read_timeout 1d;
}
To backup the SteVe database you can use the standard MySQL tools, like e.g. mysqldump
just keep in mind that SteVe uses stored procedures which are, by default, not dumped by mysqldump
. For that you can use the following command:
# mysqldump --opt --routines -usteve -p stevedb >steve-dump.sql
This will dump the complete SteVe database into the file steve-dump.sql
. To restore it on a different machine, create the steve user and database as in the installation manual and restore the dump using:
# mysql -usteve -p stevedb <steve-dump.sql
Missing stored procedures will result in Jooq not generating the jooq.steve.db.routines
package which results in a maven build error.