-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MRG] Ovh logo #286
[MRG] Ovh logo #286
Conversation
Codecov Report
@@ Coverage Diff @@
## master #286 +/- ##
==========================================
+ Coverage 92.23% 92.24% +<.01%
==========================================
Files 94 94
Lines 6904 6908 +4
==========================================
+ Hits 6368 6372 +4
Misses 536 536
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok for you @kegl for the new server?
We need to find a way to customize some of the web pages (landing, sign up). Logos is one thing, but for example we needed to add terms and conditions to the sign up page. I included it in the template for now as plain html, but I will not commit it in the master. Since these may come up later, what is important is to find a way to do this seamlessly. For example, have placeholders and defaults for those committed in the master, and a config template folder in the deployment where customizable elements can be changed. Then we can copy those into the template directory (ignored by github) when for example the frontend is launched. See also this comment: #276 (comment) |
@kegl @agramfort
|
I would do this with the config file of ram-board. It could contain the
paths to logos to use for acknowledgements.
medium priority I would say.
…On Fri, Nov 22, 2019 at 9:59 AM maikia ***@***.***> wrote:
@maikia <https://github.com/maikia> can you see if it's possible to make
it a configurable thing?
… <#m_-574576313381494335_>
@kegl <https://github.com/kegl> @agramfort <https://github.com/agramfort>
Sure, I do my best. Just to be clear as I never worked with placeholders
and defaults (or html for that matter ;) )
1. you want the frontpage to be easily customizable (logos, pictures,
terms and conditions, sections, etc) before the launch?
2. How about after the launch? If like now we need to change logo(s)
(or people, or other info) on the running RAMP... Is there a way and if yes
is it of interest to have possibility of making some changes like that to
already launched RAMP?
3. finally, how much of a priority is it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#286?email_source=notifications&email_token=AABHKHD2PBFSWUSPMF3G6TTQU6NQRA5CNFSM4JPUYXG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE5ADQA#issuecomment-557449664>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHKHGVZYDEXXSOZLH56TDQU6NQRANCNFSM4JPUYXGQ>
.
|
Ideally we should be able to change it after the launch. I simply edited the sign up template https://github.com/paris-saclay-cds/ramp-board/blob/master/ramp-frontend/ramp_frontend/templates/sign_up.html adding pure html to it. You can do the same thing temporarily at your end to add logos. The problem is that sign_up.html is in the repo and I don't want to commit Huawei T&C. The same way, I don't think OVH logo should be committed in the repo. I would set up a deploy_templates folder in the deployment folder in which some default customizable templates can be placed. These could be copied into ramp-frontend/ramp_frontend/templates at deployment (or somewhere else where flask can read from) and re-copied any time we change them. These could be then sent to index or sign_up through the flask code. I think we don't even have to restart the frontent since the flask could read these files dynamically. @maikia if you set this up for the logo section of index.html, I can take care of the T&C on the sign_up page. |
@kegl @agramfort |
nice, simple and very elegant ! +1 for MRG feel free to MRG @kegl |
Nice! Maybe add the folder to .gitignore and add documentation. |
…but not the directory itself
I think it's better to .gitignore the contents of the powered_by directory and not of the directory itself |
good to go form my end |
Great job @maikia, +1 for MRG |
Great, thanks @agramfort @kegl |
return render_template('index.html') | ||
img_ext = ('.png', '.jpg', '.jpeg', '.gif', '.svg') | ||
images = [f for f in os.listdir( | ||
'ramp-frontend/ramp_frontend/static/img/powered_by/') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This path should be with respect to __file__
, otherwise it does not exist #300
images = [f for f in os.listdir( | ||
'ramp-frontend/ramp_frontend/static/img/powered_by/') | ||
if f.endswith(img_ext)] | ||
print(images) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also maybe remove the print?
Reference Issue
What does this implement/fix? Explain your changes.
Added Ovh logo to the front webpage and removed other powered-by logos
Any other comments?