We ended with sessions on security and performance and built a project that brought together everything we covered in the course. ![]() We learned how to perform end to end deployment automation using Docker, Ansible and Bitnami tools. We explored the AWS, Azure and Google clouds, learning how to servers in each one of them both through the management console and their APIs/command line tools. We invited guest speakers that covered in-depth a variety of topics, including Tomcat, OpenStack and configuration management tools. We continued with the ins and outs of automating the deployment of apps written in a variety of languages and frameworks: PHP, Python, Java, Rails and Node.js. We started out learning about system internals, Git, bash scripting, networking and Unix build toolchains. Each student managed their cloud servers using Bitnami Cloud Hosting (of course!) and we tracked and reviewed all assignments using a Bitnami-hosted Phabricator server. You can report any bugs or feature request in KDE bugzilla.Before reporting, please make sure your issue isn’t already reported (open issues). Code review is done on Phabricator.When sending patches, add Falkon project (Falkon) as a reviewer.Reporting bugs. For everything else you’ll want to change LocalSettings.php directly. Want to contribute Great KDE Community Wiki. ![]() Other ENV vars exist and are documented by the image README file. The mornings covered mostly theory (albeit with small interactive examples) while the afternoons were devoted to practical exercises. For a few configuration settings the ENV vars provided as part of the image can be used, although these generally only cover connecting services together such as DBSERVER, DBUSER, DBPASS and DBNAME. Over a four week period that just wrapped up last week, we geeked out on Linux and the cloud.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |