Download as PDF, PPTX
![export PPH_OUTPUT=JSON
PHYSICALSERVER_ID=`flow physicalServer:create
'{"serialNumber" : "0815-2",
"nodeName": "shared1.live.codecoon.com",
"externalNodeName": "shared1.codecoon.com",
"isAvailable" : true,
"interfaces" : {
"Management Interface" : {
"macAddress" : "bla:bla:bla",
"ipAddresses" : ["a.b.c.d","a.b.c.d"]
}
}
}'
| jq -r .uuid`
http://stedolan.github.io/jq/
{"uuid" : "89259562398239",
...
}](https://image.slidesharecdn.com/inspiring2015fabian-150328043743-conversion-gate01/75/Codecoon-A-technical-Case-Study-15-2048.jpg)
![webrick_options = {
:Port => 4567,
:AccessLog => [],
:Logger => WEBrick::Log::new($stderr, WEBrick::Log::DEBUG),
:DocumentRoot => DOCUMENT_ROOT,
:SSLEnable => true,
:SSLVerifyClient => OpenSSL::SSL::VERIFY_NONE,
:SSLCertificate => OpenSSL::X509::Certificate.new( File.open(File.join(CERT_PATH, "vbox33.box.codecoon.com.crt")).read),
:SSLPrivateKey => OpenSSL::PKey::RSA.new( File.open(File.join(CERT_PATH, "vbox33.box.codecoon.com.key")).read),
:SSLCertName => [ [ "CN",WEBrick::Utils::getservername ] ],
:app => BoxManagementApi
}
Rack::Server.start webrick_options
Gesamte Webserver -
Konfiguration mit Sinatra.
Das ist alles, was man
braucht, um
* einen eigenen Webservice
* mit eigenem Webserver
* mit SSL Verschlüsselung
* mit eigenem Logging
* auf einem eigenen HTTP
Port
laufen zu lassen.](https://image.slidesharecdn.com/inspiring2015fabian-150328043743-conversion-gate01/75/Codecoon-A-technical-Case-Study-28-2048.jpg)
Uploaded byMichael Lihs
Codecoon - A technical Case Study
The document is a technical case study detailing Codecoon's continuous integration workflow and vision, covering the setup and management of development, staging, and production environments, including the use of TYPO3 Flow and third-party applications. It discusses the distribution of developer activities, highlights the advantages and disadvantages of using TYPO3 Flow, and outlines future plans for integration with services like Jenkins and GitLab. The authors aim to demonstrate best practices while enabling effective collaboration and communication within software development projects.
More Related Content
Similar to Codecoon - A technical Case Study
Codecoon - A technical Case Study
- 1.
- 2.
- 3.
- 4. Outline → Continuous IntegrationWorkflow → The Codecoon Vision → Codecoon Components → Usage of TYPO3 Flow → Integration of 3rd-party Applications → Outlook & Résumé
- 5.
- 6. How does your Project Lifecycle look like?
- 7. 1. Setup Dev Environment 2. Setup Versioning 3. Setup CI Stages 4. Setup Staging Server 5. Setup Production Server 6. Setup Deployment 7. Write Code Fix/ Repair Dev Environment Fix CI Server Update Production Server 9. Deploy to Production 8. Deploy to Staging Update Git Server Fix Deployment
- 8. Developer’s „Daily ActivityDistribution“ *) 45% Development 30% Infrastructure Setup 25% Infrastructure Maintenance *) numbers might differ slightly
- 9. „Infrastructure as aService“ ~99% Development
- 10. The Codecoon Vision ProvideCI as a service → focus on your project again → avoid all the orange activities → avoid as much light-blue activities as possible
- 11. Codecoon Management Portal ContinuousIntegrationCodecoon Developer Box Staging ProductionERP Developer
- 12. Staging Production Continuous Integration CodecoonManagement Portal Codecoon Developer Box ERP Developer
- 13. NOC Command Line Test-Harness NOC Web Service NOCServices ERP Services Deployment Services NOC Domain Models TYPO3 Flow NOC UI
- 14.
- 15. export PPH_OUTPUT=JSON PHYSICALSERVER_ID=`flow physicalServer:create '{"serialNumber": "0815-2", "nodeName": "shared1.live.codecoon.com", "externalNodeName": "shared1.codecoon.com", "isAvailable" : true, "interfaces" : { "Management Interface" : { "macAddress" : "bla:bla:bla", "ipAddresses" : ["a.b.c.d","a.b.c.d"] } } }' | jq -r .uuid` http://stedolan.github.io/jq/ {"uuid" : "89259562398239", ... }
- 16. Webspace Version 4 WebspaceVersion 4 Webspace Version 1 Abstract Webspace Webspace Version 3 Webspace Version 2
- 17. /* * * @Annotation *@Target("CLASS") */ final class Artifact {} Wir wollen zeigen, * dass es mit wenig Code möglich ist, die Persistierung in Flow zu beeinflussen * wie wir dies genutzt haben und ein Domain-Objekt in unterschiedlichen Implementierungsversionen in der Datenbank zu persistieren
- 18. /** * @FlowEntity * @PPHArtifact *@ORMTable(name="pphv2_a_webspace") */ abstract class Webspace extends AbstractArtifact { //... } Wir wollen zeigen, * wie die Annotation für ein „abstraktes Produkt“ aussieht * dass wir hier für jedes Produkt eine Tabelle angeben können, in der das jeweilige Objekt persistiert wird
- 19. Codecoon Management Portal CodecoonDeveloper Box Developer ERP Continuous Integration Chef Server Staging Production GIT
- 20. Motivation for amobile Development Environment • Work wherever you are • Development = Production • Don’t touch your system • Distribute environments & cooperate with others http://www.die-mobile-gesellschaft.de/presse/fotos/themen/03_Mobil_arbeiten/10_Mobil_arbeiten_2.jpg
- 21.
- 22.
- 23.
- 24.
- 25.
- 26. gem 'sinatra' gem 'sinatra-contrib' gem'sinatra-cross-origin' gem 'sintra-base', '~>1.4.0' gem 'webrick', '~>1.3.1' Das ist das Äquivalent zur composer.json in Ruby. Statt json/yaml wird bei Ruby oft auch für solche Dateien Ruby Code benutzt. Vorteil: Es sind sehr einfach eigene Methoden möglich, die sehr mächtige Manipulation erlauben.
- 27. get '/status' do { :response=> 'status', :box_initialized => is_initialized(), :project_type => settings.project_type, :environment => settings.environment }.to_json() end
- 28. webrick_options = { :Port=> 4567, :AccessLog => [], :Logger => WEBrick::Log::new($stderr, WEBrick::Log::DEBUG), :DocumentRoot => DOCUMENT_ROOT, :SSLEnable => true, :SSLVerifyClient => OpenSSL::SSL::VERIFY_NONE, :SSLCertificate => OpenSSL::X509::Certificate.new( File.open(File.join(CERT_PATH, "vbox33.box.codecoon.com.crt")).read), :SSLPrivateKey => OpenSSL::PKey::RSA.new( File.open(File.join(CERT_PATH, "vbox33.box.codecoon.com.key")).read), :SSLCertName => [ [ "CN",WEBrick::Utils::getservername ] ], :app => BoxManagementApi } Rack::Server.start webrick_options Gesamte Webserver - Konfiguration mit Sinatra. Das ist alles, was man braucht, um * einen eigenen Webservice * mit eigenem Webserver * mit SSL Verschlüsselung * mit eigenem Logging * auf einem eigenen HTTP Port laufen zu lassen.
- 29.
- 30. . ├── Gemfile ├── application.rb ├──certificates │ ├── ca-bundle.crt │ ├── vbox33.box.codecoon.com.crt │ └── vbox33.box.codecoon.com.key ├── config │ ├── boot.rb │ ├── config_development.yaml │ └── config_production.yaml ├── config.ru ├── controllers │ ├── management_controller.rb │ └── status_controller.rb ├── lib │ └── helpers.rb ├── log └── readme.md
- 31.
- 32. 4. Shared Host •Acts as Chef Node • Deployed with Surf using rsync over ssh • Holds git repository for each project
- 33. Codecoon Management Portal DataBags ChefCookbooks Vagrant Box Chef solo creates uploads pull mount info upload
- 34. Surf package build locally Cache onProduction Stage Release Directory more task on prod. f.e. flush cahces tranfere with rsync cp release
- 35. 5. ERP • OurERP has crappy „Web Service“ • No user management / queue in the Web Service • Used MessageQueue (RabbitMQ) • Made ERP Multi-User ready Was wollen wir mit dieser Folie zeigen? * Anbindung des ERP Systems an die Hosting-Oberfläche * Verwaltung von Kunden, Rechnungs- und Vertragsdaten * Anbindung über einen „Webservice“ * ** eine Art SOAP Codecoon Management Portal ERP
- 37. Outlook • Implement themissing parts of our vision • Jenkins and Gitlab as integrated services • Production Stage • User driven development • 10 Early Adopters
- 38. Flow - thegood things * Fluid is a great Template Engine * Functional testing with Flow is pure fun * Business (Domain) Logic can be implemented with very little Framework overhead * Command Controllers are great FLOW
- 39. Flow - thenot so nice things * Flow Packages are not modular * „Everything or nothing“ * Code-Rewrite makes feedback cycles during development slow * Remote Debugging in proxy classes can be annoying * All the „magic things in the background“ and declarative stuff makes understanding hard * Code-Completion and IDE tools not very helpful * Webservices (REST) are not easy to implement * There is no ready-to-use Controller à la Sinatra * Not much „Best-Practices“ on Google… FLOW
- 40. Resume • Flow isa powerful Framework • Integrates well with 3rd party components • Don’t use it „unreflected“ • Best detail solution vs. smoothes integration • Duplicated configuration • Duplicated functionality
- 42. We will goout and try it with you!
- 43. Thank you! We hopeyou had fun! If you want to stay in contact: Michael Lihs: @kaktusmimi Fabian Stein: @docmac @codceoon Or outside at our booth