This is the Support Page for the C2NET developers

This sub-project of the development portal was created to host documentation, software, and tools that are meant to support the development itself. It includes tutorials and tips for Configuration Management, development, support tools, etc. Its purpose is not to create documents or software that are actually deliverables of the C2NET project, although parts of it can be used to enrich the official deliverables.

This page will keep being updated with new documentation and tools.

Documentation and tools for support of the C2NET development:

• GIT - Configuration Management: This states the policies defined for the uniform use of GIT throughout the project development;
• C2NET Development Management: This page is a tutorial for all partners developing in C2NET to report that status and provide management a brief overview of the development evolution;
• Last updates about PaaS4SLA: This blog collects the last updates about PaaS4SLA platform.
• Component versioning: This page explains how to use git tags for versioning your code in order to allow other people using it.
• SDK for development with PaaS4SLA: These are the resources and development tools needed to deploy on the PaaS4SLA platform;
• Training examples for development with PaaS4SLA: Here you will find examples of configurations that were used with the PaaS4SLA platform;
• C2NET Code Conventions: This should be read by all developers when starting to code for C2NET;
• Aggregation of Repositories: While most will want to clone only the GIT repositories of the modules they are working on, some may want to clone all GIT repositories of C2NET or only of some sub-project of C2NET;
• OpenSourceProjects.eu: Documentation: Documentation for working with the Open Source Projects code hosting platform.
• Runtime Images: Information about the different images to be used in the C2NET project: both base ones and customized ones (e.g. UCP, MariaDBWrapper...)
• Service Application and Deployment Manifest repositories: Information about how to use the repositories for storing the C2NET service application and deployment manifest, Demo service application and deployment manifests and Test service application and deployment manifest.
• Component-bundles repository: A new folder has been created in the FTP server called component-bundles (at the same level of integration-test folder) in order to be used as a component bundle repository. This new folder is meant to hold bundles of components that are ready to be deployed. The main idea is that the partner responsible of each component uploads there any component version it generates ready to be deployed, in order other partners can use it for their tests. Each file containing the bundle in the folder should follow the next naming convention: ComponentAcronym-version-partner.zip, i.e. PSMQ-1_1_3-ATOS.zip