932 |
932 |
Configuration
|
933 |
933 |
~~~~~~~~~~~~~
|
934 |
934 |
|
935 |
|
The settings for the snf-branding application are found in the configuration
|
936 |
|
file <path_to_conf_file> 15-snf-branding.conf
|
|
935 |
The settings for the snf-branding application can be found in the configuration
|
|
936 |
file <path_to_conf_file>/15-snf-branding.conf
|
937 |
937 |
|
938 |
|
By default, the service name is Synnefo and the Company name is GRNET.
|
|
938 |
By default, the service name is Synnefo and the company name is GRNET.
|
939 |
939 |
These name and their respective logos and urls are used throughout Astakos,
|
940 |
940 |
Pithos and Cyclades UI.
|
941 |
941 |
|
942 |
942 |
**Name and logos:**
|
943 |
943 |
|
944 |
|
The first group of branding customization regards Company and Service info.
|
|
944 |
The first group of branding customization regards company and service info.
|
945 |
945 |
|
946 |
946 |
You can overwrite the company and the service name and url respectively by
|
947 |
947 |
uncommenting and setting the following:
|
... | ... | |
954 |
954 |
#BRANDING_COMPANY_URL = 'https://www.grnet.gr/en/'
|
955 |
955 |
|
956 |
956 |
|
957 |
|
BRANDING_COMPANY_NAME and BRANDING_COMPANY_URL appear in Astakos and Cyclades
|
958 |
|
footer.
|
959 |
|
BRANDING_COMPANY_NAME appears also in Astakos project tab.
|
|
957 |
BRANDING_COMPANY_NAME and BRANDING_COMPANY_URL appear in Astakos, Cyclades and
|
|
958 |
Pithos footer.
|
|
959 |
In addition to that, BRANDING_COMPANY_NAME appears in Astakos project tab.
|
960 |
960 |
|
961 |
961 |
**Copyright options:**
|
962 |
962 |
|
963 |
963 |
By default, no copyright message is shown in the UI. If you want to make it
|
964 |
|
visible to to footer of Astakos and Cyclades, you can uncomment and set True
|
965 |
|
the setting:
|
|
964 |
visible to the footer of Astakos, Cyclades and Pithos UI, you can uncomment and
|
|
965 |
set True the setting:
|
966 |
966 |
|
967 |
967 |
.. code-block:: console
|
968 |
968 |
|
... | ... | |
989 |
989 |
Storage logo storage_logo.png Visible in Pithos UI pages
|
990 |
990 |
=============== ============================ =========
|
991 |
991 |
|
992 |
|
The methods available for replacing all or individual branding-related images
|
993 |
|
are :
|
|
992 |
There are two methods available for replacing all or individual
|
|
993 |
branding-related images:
|
994 |
994 |
|
995 |
995 |
1. Create a new directory and place there some or all of your images.
|
996 |
996 |
|
997 |
997 |
If you want to replace all images, keep the name/extension conventions as
|
998 |
|
indicated above and set
|
|
998 |
indicated in the above table and set:
|
999 |
999 |
|
1000 |
1000 |
.. code-block:: console
|
1001 |
1001 |
|
... | ... | |
1008 |
1008 |
pointing to the file inside your directory for each BRANDING_<image>_URL that
|
1009 |
1009 |
will be replaced.
|
1010 |
1010 |
|
1011 |
|
2. Upload some or all of your images to a server and replace
|
|
1011 |
2. Upload some or all of your images to a server and replace each
|
1012 |
1012 |
BRANDING_<image>_URL with the absolute url of the image ( i.e.
|
1013 |
1013 |
BRANDING_DASHBOARD_URL=’https://www.example.com/images/my_dashboard.jpg’ ).
|
1014 |
1014 |
|
1015 |
1015 |
Note that the alternative text for each image tag inside html documents is
|
1016 |
|
alt=“BRANDING_SERVICE_NAME {Dashboad, Console, Compute}” respectively.
|
|
1016 |
alt=“BRANDING_SERVICE_NAME {Dashboad, Compute. Console, Storage}” respectively.
|
1017 |
1017 |
|
1018 |
1018 |
|
1019 |
1019 |
.. note:: Retina optimised images:
|
1020 |
1020 |
|
1021 |
|
Synnefo UI is optimised for Retina displays. As far as images are concerned,
|
1022 |
|
retina.js (http://retinajs.com/ ) is used.
|
|
1021 |
Synnefo UI is optimised for Retina displays. As far as images are concerned,
|
|
1022 |
`retina.js <http://retinajs.com/>`_ is used.
|
1023 |
1023 |
|
1024 |
1024 |
Retina.js checks each image on a page to see if there is a high-resolution
|
1025 |
1025 |
version of that image on your server. If a high-resolution variant exists,
|
1026 |
1026 |
the script will swap in that image in-place.
|
1027 |
1027 |
|
1028 |
|
The script assumes you use Apple's prescribed high-resolution modifier (@2x)
|
1029 |
|
to denote high-resolution image variants on your server.
|
|
1028 |
The script assumes you use `Apple's prescribed high-resolution modifier (@2x)
|
|
1029 |
<http://developer.apple.com/library/ios/#documentation/2DDrawing/Conceptual/
|
|
1030 |
DrawingPrintingiOS/SupportingHiResScreensInViews/SupportingHiResScreensInViews
|
|
1031 |
.html#//apple_ref/doc/uid/TP40010156-CH15-SW1>`_ to denote high-resolution
|
|
1032 |
image variants on your server.
|
1030 |
1033 |
|
1031 |
1034 |
For each of the images that you wish the script to replace you must have a
|
1032 |
1035 |
high-resolution variant in the same folder named correctly and it will be
|
1033 |
1036 |
detected automatically. For example if your image is in <my_directory> and is
|
1034 |
|
named “my_image.jpg” the script will look in the same directory for an image
|
1035 |
|
named “my_image@2x.jpg”.
|
|
1037 |
named "my_image.jpg" the script will look in the same directory for an image
|
|
1038 |
named "my_image@2x.jpg".
|
1036 |
1039 |
|
1037 |
1040 |
In case that you don’t want to use a high-resolution image, the
|
1038 |
1041 |
normal-resolution image will be visible.
|
... | ... | |
1045 |
1048 |
|
1046 |
1049 |
**EMAILS**
|
1047 |
1050 |
|
1048 |
|
All the email *.txt files are already customized to contain your Company and
|
1049 |
|
Service names but you can further alter their content if you feel it best fits
|
1050 |
|
your needs using django’s TEMPLATE_DIRS setting.
|
|
1051 |
The output of all email *.txt files will be already customized to contain your
|
|
1052 |
company and service names but you can further alter their content if you feel
|
|
1053 |
it best fits your needs using django’s TEMPLATE_DIRS setting.
|
1051 |
1054 |
|
1052 |
1055 |
In order to overwrite a template you need to create a new one with the same
|
1053 |
1056 |
name, place it to a folder of your choice and provide its path to the
|
... | ... | |
1061 |
1064 |
description and a link to their content:
|
1062 |
1065 |
|
1063 |
1066 |
|
1064 |
|
* ``snf-astakos-app/astakos/im/templates/im/email.txt`` Base email template. Contains a contact email and a “ thank you” message.
|
|
1067 |
* ``snf-astakos-app/astakos/im/templates/im/email.txt`` Base email template.
|
|
1068 |
Contains a contact email and a “ thank you” message.
|
1065 |
1069 |
(Link: https://code.grnet.gr/projects/synnefo/repository/revisions/master/changes/snf-astakos-app/astakos/im/templates/im/email.txt )
|
1066 |
1070 |
|
1067 |
1071 |
|
1068 |
1072 |
* ``snf-astakos-app/astakos/im/templates/im/activation_email.txt`` Email sent to user that prompts him/her to click on a link provided to activate the account.
|
1069 |
|
Extends “email.txt”
|
|
1073 |
Extends “email.txt”
|
1070 |
1074 |
(Link: https://code.grnet.gr/projects/synnefo/repository/revisions/master/changes/snf-astakos-app/astakos/im/templates/im/activation_email.txt )
|
1071 |
1075 |
|
1072 |
1076 |
* ``snf-astakos-app/astakos/im/templates/im/invitation.txt:`` Email sent to invited user. He/she has to click on a link provided to activate the account.
|
... | ... | |
1115 |
1119 |
.. warning:: Django templates language:
|
1116 |
1120 |
|
1117 |
1121 |
If you choose to overwrite these email templates, be mindful of the necessary
|
1118 |
|
information contained in django template variables that must not be omitted ,
|
1119 |
|
such as the activation link for activating one’s account etc.These variables
|
1120 |
|
are contained into {{}} inside the templates.
|
|
1122 |
information contained in django template variables that must not be omitted,
|
|
1123 |
such as the activation link for activating one’s account and many more.
|
|
1124 |
These variables are contained into {{}} inside the templates.
|
1121 |
1125 |
|
1122 |
1126 |
|
1123 |
1127 |
|