Automated build and test running on WebDevOps CI (GitLab.com CI custom AWS runner) sponsored by Onedrop GmbH & Co. KG. Or write an issue in our GitHub repository.
docker apache-httpd nginx liquibase typo3 vsftpd varnish dockerfiles docker-testing ubuntu centos alpine debian dockerfile docker-imageGeneric migration tool for RDBMS and other resources based on Liquibase
database migration liquibaseRuns Liquibase migrations on Play application startup. Current version is built against Scala 2.10, 2.11 and 2.12 and works with Play 2.4 and higher.
play-framework liquibaseDemo project for Spring Boot with Liquibase
spring-boot java8 liquibaseExample application for storing books.
liquibase travis-ci gatling spring-boot angularjsPyquibase is a Python wrapper for liquibase. There are other liquibase wrapper for python but they all require change log files to be in YAML format. Since I want to use xml file for liquibase, I built my own liquibase wrapper for python. Athough I use Pyquibase with xml files only, it should also work with other file types.
liquibase migrationLibrary that provides a JUnit rule for setting up unit test using an embedded in-memory database (H2)
jdbc junit sql liquibase testing junit-rule hsqldb flyway h2-databaseThe primary motivation behind this tool is to provide a simple and quick Go (instead of Java) based database migration tool that allows loading migrations from anywhere, including from inside your code so you can distribute single binary applications. You write the migration and rollback SQL, Rove will apply it for you properly. Database migrations are necessary when you make changes to your applications. You may need a new table or a new column so you have to write the SQL commands to make the changes. The tricky piece is when you perform an upgrade, how do you manage which SQL queries will run? Do you run all of them again and then the new ones after? Or is there an easy way to track which queries have been run so you only run new ones? What if you have to rollback your database because of a feature that was released too early and is causing problem? How do you manage those queries? You can definitely write your own code to manage the migration process, but Rove makes the process much easier for you. You also don't have to convert your SQL code to a another format like JSON or XML, you can just add a few comments around it and Rove will handle the rest.
database-migrations liquibaseSample Spring Boot 2.0.x OAuth2 JWT Authorization Server (JWT, JPA, Hibernate, PostgreSQL, Dockerize). You can use this project to boostraping Authorization your own Application.
spring-boot postgresql oauth2-server liquibase oauth2-resource-server client-credentials lombok-gradle odenktoolsCollection of Gradle plugin by JetBrains.
docker terraform gradle-plugin liquibase
We have large collection of open source products. Follow the tags from
Tag Cloud >>
Open source products are scattered around the web. Please provide information
about the open source projects you own / you use.
Add Projects.