{"push_id":976161330,"size":3,"distinct_size":3,"ref":"refs/heads/consolidate-db-scripts","head":"2c91bf3e50debd9634b3fde0ac68b55ce7b47d98","before":"5dd706ae4c336a98a2cf52c84639d4c263a9f5d7","commits":[{"sha":"4770faf635abf4c280fae63480e7d67beee34155","author":{"email":"cb4940bc805094928ff859a6a56b574f1526c42a@tarent.de","name":"Thomas Krille"},"message":"Extract assets and configuration on startup\n\nAssets and configuration will copied from the classpath to the home\ndirectory, when starting OSIAM.\n\nThe contents of the home directory have been put on the classpath,\nbecause it's the only place that is working under the different runtime\nenvironments, e.g. Maven (with Spring Boot plugin), Tomcat (or other\nServlet containers) and standalone usage with `java -jar osiam.war`.\n\nInitialization will not be done, if the home directory already contains\nfiles or folders, to prevent accidentally overwriting a customized\nsetup.\n\nAlso load the default configuration that's contained in the classpath,\nto work around a chicken-and-egg problem:\nIf OSIAM starts without a configuration in place, it will not reach the\npoint, where it initializes the home directory, because property\nreplacements will fail beforehand.\nAlways loading the default config, which is the same config that will be\ncopied to the home directory anyway, makes sure all properties are set\nto working defaults.\nOn the next start the values from the config file in the home directory\nwill override the ones defined in the default config.\n\nRemove the distribution creation and make the `.war` file the single\nartifact to distribute.\nThe `.war.` file contains all needed assets now, so a separate\ndistribution artifact is not needed anymore.\nAlso add the changelog and readme to the `.war.` file from now on, as\nthey have been in included in the distribution artifact before.\nAssets and default configuration can still be extracted from the `.war.`\nfile, as it's just a ZIP file, but from a different path.","distinct":true,"url":"https://api.github.com/repos/tkrille/osiam-osiam/commits/4770faf635abf4c280fae63480e7d67beee34155"},{"sha":"6f3ec7020b666bc5b883f3c9ae563d2bf1703282","author":{"email":"78caba27373d027fd471271aa386b2261eabfb92@gmail.com","name":"David Crome"},"message":"Merge pull request #130 from tkrille/extract-assets\n\nExtract assets and configuration on startup","distinct":true,"url":"https://api.github.com/repos/tkrille/osiam-osiam/commits/6f3ec7020b666bc5b883f3c9ae563d2bf1703282"},{"sha":"2c91bf3e50debd9634b3fde0ac68b55ce7b47d98","author":{"email":"cb4940bc805094928ff859a6a56b574f1526c42a@tarent.de","name":"Thomas Krille"},"message":"Squash Flyway migrations\n\nThis unifies the first 3 database versions, that reflect the way the\ndatabase schema looks like in the latest 2.x version.\nThe idea is that version 1 will be the new baseline, so that on an\nupgrade from 2.x to 3.0, Flyway will mark this schema as applied\n(baselined) and won't run it.\nAfter that, version 2 will be applied, that is currently just changing\nthe scopes of the well-known clients.\nVersion 2 should be used for all upcoming automatic changes, that deal\nwith old data, not updated schemas, like removing the auth-server\nclient, renaming the auth-server extension, etc.\n\nThe PostgreSQL scripts have been re-generated by Hibernate's auto DDL\nfeature and exported with IntelliJ.\nIt had one unique constraint missing: `osiam_client.id`.\nThe MySQL scripts are the same as before, but combined.","distinct":true,"url":"https://api.github.com/repos/tkrille/osiam-osiam/commits/2c91bf3e50debd9634b3fde0ac68b55ce7b47d98"}]}