Starting with a new organisation, the first thing that you will need to do is create some spaces.
Spaces are used to create separate working environments, with their own specific user permissions and access depending on your needs.
You can add spaces from the main page of the Web Console.
Invite Users to Your Spaces
Open the Members menu of your Org and you should see a drop-down menu that includes your organisation and all its spaces.
You can invite collaborators to your org, using the following roles:
- ORG MANAGER - can invite users and manage user roles in the org and all spaces
- ORG AUDITOR - have read-only access to org information and reports
Or you can invite them to specific spaces:
- SPACE MANAGER - can invite users and manage user roles in a given space
- SPACE DEVELOPER - can create, delete, and manage applications and services, and has full access to app logs and reports
- SPACE AUDITOR - has read-only access to space information, app logs, and reports
Each user can have different permissions for each space allowing flexible access management.
Invited users will be notified of their invitation via email.
Login from the Command Line Interface
You will need the command line interface to push your apps, so the last thing you need to do before being are ready to push your first app is to install that client.
To do this you can click on the tools menu on the Web Console which will give you several download options suitable for your operating system as well as information on how to get started using the command line.
To login from the command line, use the command “cf login”. You will be asked for an API endpoint, user name, password and optionally a space.
- API endpoint: find it in the GETTING STARTED section of the tools menu on the Web Console
- User name: your user name
- Password: your password
- Space: Initially your organisation will have no spaces and you can skip this step. Spaces are created and managed by you and you can target a space either by logging in through “cf login”, or directly targeting using “cf target –s space-name”
Atos Cloud Foundry supports a variety of common programming languages. You can push applications written in these languages using the “cf push” command and the name that you want to give to your app.
To push applications written in other languages you can make use of custom buildpacks.
Once you have logged in and targeted a space, navigate to the directory containing your application.
Using default buildpacks
cf push app-name
Using custom buildpacks
cf push name-of-your-app –b buildpack-name
Once the process is complete simply visit your apps url location to confirm that it has been deployed successfully.
Manage Your App From the Web Console
To manage your application, go to the web console and navigate to its designated page in the space that you used.
From this page you can:
- rename, stop and restart the application
- view status updates and logs
- scale your apps:
- memory limit
- disk limit
The page also presents additional menus for:
- environment variables
The routes are the URLs that you can use to access your application. To manage them, simply go the Routes menu of your app configuration page on the Web Console. Having the option of adding and removing routes in a matter of seconds can allow you to have your application accessible from all your desired web addresses.
Watch the video below for a demonstration of the main functionality of Atos Cloud Foundry.