Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Configuration of deployment installation #250

Closed
physikerwelt opened this issue Nov 28, 2016 · 12 comments · May be fixed by #352
Closed

Configuration of deployment installation #250

physikerwelt opened this issue Nov 28, 2016 · 12 comments · May be fixed by #352

Comments

@physikerwelt
Copy link
Contributor

I only discovered a few minor issues (#244, #246, #247, #248) while testing the developer setup.
However, I got completely stuck with deployment setup.
Configure Praktomat in Praktomat/src/settings/local.py, to set data base names and paths.
turns out to be much harder than it seems.
After two days of trail and error I'm still not able to log into the web UI due to a

    CSRF cookie not set.

exception even though there is a cookie called csrftoken.
Is there somewhere a more detailed guide on setting up a deployment environment.
@nomeata
Copy link
Contributor

nomeata commented Nov 28, 2016

No, there is unfortunately no better guide. Is the cookie maybe old and not actually update in the browser? Was a secret key file properly generated by the code in defaults (I guess a cookie generated with the wrong secret key might be ignored)?

@physikerwelt
Copy link
Contributor Author

@nomeata How can I check the secret key file?

What would really help for the configuration is the directory structure on the kit server and the corresponding web services. Especially this section
https://github.com/KITPraktomatTeam/Praktomat/blob/master/src/settings/local.py#L15-L53
suggests that there is a certain best practice naming convention that should be applied.

@nomeata
Copy link
Contributor

nomeata commented Nov 28, 2016

That part is pretty KIT-specific. If you just have one instance, just scrap the whole code and set SITE_NAME directly. Similarly with other conditional statements further down.

@nomeata
Copy link
Contributor

nomeata commented Nov 28, 2016

@nomeata How can I check the secret key file?

Praktomat should automatically create a file SECRET_KEY in the UPLOAD_ROOT directory. If that is not the case, maybe some permissions are wrong?

@ifrh
Copy link
Contributor

ifrh commented Dec 8, 2016

Hi, here I hat to fix a bug inside class D for getting an automated SECRET_KEY see pull request #238 and there commit 35ab8e9

@mhecker
Copy link
Contributor

mhecker commented Dec 8, 2016

I picked that particular commit now into our master: 6d8fdd2 Thanks @ifrh.

@physikerwelt does this work for you now!?!?

@physikerwelt
Copy link
Contributor Author

@mhecker I started with the test config. There the default values

SECRET_KEY = "not-so-secret"
# Private key used to sign uploded solution files in submission confirmation email
PRIVATE_KEY = join(dirname(dirname(dirname(__file__))), 'examples', 'certificates', 'privkey.pem')

work ok.
I think I'll have to look for a slightly bigger machine to test USESAFEDOCKER and the mail features which we currently do not use at all.

@ifrh ifrh mentioned this issue Mar 1, 2017
Merged
@ifrh
Copy link
Contributor

ifrh commented Mar 1, 2017

Just now I saw, that there was a small typo in class D left.
Fixed in my pull request #268

ifrh pushed a commit to ifrh/Praktomat that referenced this issue Nov 27, 2021
reinserted fix in src/settings/defaults.py: using d.SECRET_KEY and no…
80fde4b 
…t SECRET_KEY.

(see KITPraktomatTeam#250 (comment) )
this fix had been overwritten between October 2018 and July 2019
by merging KITmaster into this branch https://github.com/ifrh/Praktomat/tree/bugfix_small_typos .

remove trailing whitespaces
(as requested in May 2017 KITPraktomatTeam#268 (comment)
and November 2021 KITPraktomatTeam#268 (comment) )
@ifrh
Copy link
Contributor

ifrh commented Mar 7, 2022

I only discovered a few minor issues (#244, #246, #247, #248) while testing the developer setup. However, I got completely stuck with deployment setup. Configure Praktomat in Praktomat/src/settings/local.py, to set data base names and paths. turns out to be much harder than it seems.
[...]
Is there somewhere a more detailed guide on setting up a deployment environment.

Are information in README (update on 19. February 2022) now better?

@ifrh
Copy link
Contributor

ifrh commented May 6, 2022

@physikerwelt : perhaps this issue could be closed? How do you think about closing it?

@physikerwelt
Copy link
Contributor Author

Sure close it...too old

@ifrh
Copy link
Contributor

ifrh commented Jul 29, 2022

@ratefuchs , @KITPraktomatTeam : this issue should be closed. (Sadly I cannot do it.)

@nomeata nomeata closed this as completed Jul 29, 2022
ifrh pushed a commit to ifrh/Praktomat that referenced this issue Aug 19, 2022
Update README.md: Insert information about new dependencies introduce…
13f2d44 
…d by merging "feature boxplot-taskstatistic" ( KITPraktomatTeam#345 )  .

Update README.md to give more information about installation steps : Fixes KITPraktomatTeam#250 .

Include change sets from KITPraktomatTeam#351 , KITPraktomatTeam#349 , KITPraktomatTeam#348
@ifrh ifrh mentioned this issue Aug 19, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
4 participants
@nomeata @mhecker @physikerwelt @ifrh